Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migrating to Windows 2000

Status
Not open for further replies.

Mecurio

MIS
Oct 23, 2000
18
GB
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
 
Because you are going on a different domain, Exchange will get really antsy.

Why are you changing domains? How many mailboxes?

Suggest you build Exchange properly onto new domain, exmerge mailboxes off A, upload to B and scrap domain A.
 
We're changing domains as we need to remove NT4 from the network to comply with an audit. There's 400 mailboxes on the server and it's part of a wider exhange organisation, hence wanting to preserve the machine name. I'd like to avoid exmerging if possible as the priv db is 27Gb.

Cheers

Rowan
 
OK, I've done a lot of things with Exchange but never that...

Here's some thoughts.

1. Install a new Exchange server in domain A, migrate everything over to that and remove Exchange from the PDC (never a good plan anyway). Then rendom.
2. If you don't have domainB yet anyway, stick with domainA and upgrade the boxes. You can upgrade NT4 to Windows 2000 in situ including with Exchange on it (well, it worked for me anyway). You can upgrade 5.5 to 2000 in situ too (ditto).
3. Third party tools.

Is domainB running?
Can you not upgrade the NT4 box as it stands?
 
Domain B is running. Permissions wise I couldn't see any problems with bringing up the services. I'd created a new service account in Domain B and added it as a full admin on the NT4 PDC + at Org, Site & Config levels within Exchange.

Have you upgraded NT4 to 2000 when it was a PDC?

Cheers

Rowan
 
Erm, I can't recall - I moved off 5.5 about 7 years ago!!

Can you not virtualise it and give it a go in virtual?
 
We're still waiting for the corporate rollout of 2003, hence having 5.5 running.

I'm building a test enviroment now with a copy of the 2k3 DC and the 2000 server. Hopefully that'll prove out whether restoring exchange breaks the connectivity.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top