Current situation: 5.5 ENT SP4 on NT4 PDC, Domain A, only machine in domain. Windows 2003 AD single domain forest, Domain B, 2003 functional level.
I've built a 2000 server with the same name as the NT4 PDC, connected it to Domain B by just having it plugged into on of the 2k3 DCs. Installed 5.5 ENT, SP4 & reconfigured services. Restored the directory, priv, pub and associated logs from a stop service backup. Brought up SA & DS OK. Defragmented priv & pub, ran ISISNTEG -patch then brought up IS. Could connect locally to the mailboxes without any issue, however when tried to connect from a client it couldn't authenticate. Further investigation revealed the new server could no longer reach the DC. I tried removing it from the domain then re-adding but couldn't contact the domain to re-create the computer account. I'm thinking perhaps because the old box was a PDC it doesn't like restoring the directory to a member server? Before I start again with a clean build and a restore of the DC can anyone shed any light? Cheers Rowan
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Can you help the group understand why you didn't just install a 2000 box as a member in the NT4 domain and then DCPROMO it to be a DC? I'm struggling to understand why you did what you did. Once I/we understand that we can see about giving you a way forwards.
We're part of a larger exchange organsiation and want to remove the NT4 domain altogether. With the PDC being the exchange server I couldn't build the 2000 server with the same name - that's required to install Exchange / recover correctly? Here's a more detailed list of what my plan was:
Old Server
Make sure everyone has shutdown Outlook (net send)
Stop exchange services
Unplug from network
Full backup
New Server
Connect to direct DC
Join domain
Install Exchange 5.5 enterprise
Install SP4
Install Mbox Manager
Install ADS
Install Outlook 2003
Stop Exchange services
Restore databases
Start SA
Start DS
eseutil /d priv & pub
Isinteg -patch
Start IS
Install Trend
Change IP to .3
Connect to network and test IMS
Once exchange was up in the new domain happily I was planning to not put the NT4 box back on the network.
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
You've got your logic wrong and I explained something badly. What you should have done is to: Install NT4 on a (virtual would be ok) box somewhere. promote that to PDC. Upgrade that box to Windows 2000. Hey presto. AD done and dusted. Install Exchange 5.5 onto that 2000 Migrate all mail to it. Remove the old NT4 box. Install Windows 200x on that original box Install Exchange 5.5 on that original box Migrate all mail back to it.
However........ Why do you think you want the machine name the same? You know that if you install Exchange (any version) and do mailbox moves you will not have to go around to all the workstations and change anything. You just need to leave the old Exchange server on until everyone has logged onto their email Their mail profiles will be automatically updated. After a week or so you can remove Exchange from the old 5.5 server.
Don't try to bring a box in that's the same name as the DC and install anything on it, you're going to give yourself a complete nightmare.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 5.5] >> Installation >> 5.5 on Windows 2000 
5.5 on Windows 2000 - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
