Migrating Exchange from NT domain to Active Dir.

[itecs]

Thanks in advance.

I have a NT 4.0 Server with Exchange 5.5 installed. The NT server is also the PDC for the NT Domain.

I will be installing a new server this weekend, which will be Windows 2003 Server, creating a new domain (for a 2003 / 2000 mixed environment).

I know that my NT server cannot join a Active Directory Domain, however, I want to be able to still use the current user mailboxes in the Exchange 5.5 for the new accounts that will be created in the 2003 server. Any suggestions on how I can get the Win NT server to join the newly created Active Directory (as a client, not a BDC) and allow the users in the Active Directory to use the mail boxes on the Exchange side?

Brian

 

[liorz66]

Well, try this method
Take a simple PC, install Winnt BDC and promote it to PDC (relax, it’s only temporary).
Make sure the PC is strong enough for Win2003 server though.

Now, perform an upgrade to 2003 server ON the temp PDC!!!
Then you can add the actual 2003 servers and remove the temp.

All accounts from the NT will be migrated and active and also you’ll have NT DC’s as ROLE servers, especially the Exchange. Should you decide to abort, you can simply remove the 2003 and use the old NT domain.

Good luck

LZ

 

[itecs]

Thanks for your reply. I've never had any good experiences upgrading server from one old OS to another (escpecially with something like upgrading from ME to 2000 or XP).

You feel pretty confident that Microsoft's updgrade utility works well from NT to 2003? I could create a ghost image of the old NT and perform the upgrade, and always go back, as you stated.

Thanks again,
Brian

 

[liorz66]

I wouldn't use an upgraded machine for production either.
but it's just a temporary machine.
just perform the upgrade and then add a new 2003 DC. then you can safely turn off the temp machine.

 

[itecs]

So the NT server that is the current PDC and also is the exchange server should not be upgraded?

If I was to upgrade the NT server with exchange, do you think that Exchange 5.5 will run normally with the new active directory, in respects to the user accounts that were migrated from NT domain to AD?

I could blow away the current PDC and start a whole new domain without issues. As a matter of fact, I plan using a totally sperate server to do the initial server 2003 installation. Creating a new AD domain seperate from the current NT domain. I was then going to upgrade the NT server (with Exchange) to 2003 and hope that the Exchange side of that upgraded server works within the newly created AD domain, retaining the ability for the users to authenticate with Exchagne to access mails and so forth.

 

[liorz66]

If it's not broken - don't fix it.
don't touch the exchange at all. it's better to have it running on NT than to drown in 2003 with Ex 5.5.
Besides, it will run with a role of PDC, made exactly for these situations.

About a new domain - have you considered all actions?
You'll have to migrate all users, passwords etc. Then you'll have to change or add the domain name in each machine manully and create an account for every single machine.and what about a trust with the old domain?
Don't - I wouldn't

LZ.

 

[AlexIT]

If all you are doing with the temp machine is moving user accounts you can just export them to a disc (Active Directory Migration Tool ADMT) and import them on a freshly-installed Win2k...I would never upgrade a PDC in real world since it never worked correctly in the lab...0/3 tries.

Plus since your NT probably doesn't have a FQDN your going to have to start with a "new" domain as Esandman said anyway...better off to backup the shared files, exmerge the mailboxes to tape/CDR, save the users with ADMT, wipe the server and install Win2k from scratch the right way, then install Exchange5.5 from scratch (or upgrade to 2000/2003), ADMT the users to Win2k AD, then exmerge the mailboxes back into the new Exchange, reload the shares and reassign permissions and you are done.

Takes less or about same time as installing NT on temp server, upgrading, finding and fixing the domain errors, dcpromo the old PDC, installing Win2k, dcpromo the new install, dcpromo the temp server...but doesn't have any legacy info tucked into your AD to bite you in 6 mos.

Alex

 

[itecs]

Alex that was a great explanation of exactly what our team has decided to do. I greatly appreciate your great step-by-step advice.

Brian

 

[Marcs41]

See also: faq858-3483
and

http://www.microsoft.com/technet/tr...nge/exchange2003/proddocs/library/default.asp

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}