Networks

Ask something
Discussion Locked

nt 4.0 Migration to win2k3 server

0 helpful
2 replies

by nicholasclayg 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok here is the deal, I have a migration coming up- Nt 4.0 domain to win 2003 server. There are currently 182 clients on xp pro, 40 win 95 machines and some macs (10 all running 10x) On top of that its using SecureID (pass changes every minute when you log into the VPN)Basically this one is new for me, ive performed many a win95 to win2k pro and nt 3.5 to 4.0 etc. But this one is tricky in the fact that ALL user profiles, settings, GP, and everything under the sun cannot be compromised at all. I am having a problem grasping the AD migration.
Heres my question: What is the general process for doing a non destructive domain transfer? I know that can generate a plethera of possible answers but I need a round about where to start so I can start work-

2 replies

by chrisdent

Testing. You can never have too much. Build a test network and test out possibly deployment scenarios on there.

The test network should mirror your live network as closely as possible in terms of complexity (include MACs, 9x computers, NT BDCs, as well as the XP machines).

Easiest way to do that is create a temporary BDC, split it off from the network and promote it to PDC for the domain giving you a production and a test version of your existing domain. Of course the test server should never re-appear on your live network.

The normal upgrade path for this is PDC first. The BDCs should be capable of acting as BDCs for Active Directory. But be aware that Windows 2003 uses a more advanced version of Active Directory than Windows 2000. Testing should reveal whether or not your upgrade path will work.

As you probably know DNS is vital for Active Directory, make sure all your client PCs have DHCP configuration unless you want to run around finding problems later. Make sure each works correctly with an internal DNS server.

Remember that direct upgrade isn't the only option, you could build an Active Directory domain. Create a trust between that and your NT domain and slowly shift servers and users across.
While this method is a lot slower it gives you plenty of time to resolve any issues that might pop up and isn't so risky.

This documentation from Microsoft should provide some additional information:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/ad/windows2000/plan/migntw2k.asp

by chrisdent

One more bit.

Remember that in the event of an emergency it would be possible to re-create the old domain from the BDC you created for the test network.

This discussion is closed to new replies.