Networks

Ask something
Question Locked

NT Migration to 2003

0 helpful
3 replies

by howithink

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

Hi,

We currently have a domain running NT4 as the PDC. Not too long ago a 2003 server was purchased and added in as a member server into the NT4 domain. Now we want to get rid of our NT4 PDC.

What would be the best way of doing this? Should we promote 2003 member server to AD and move the accounts or should I simply move all the data from NT4 onto the 2003 server, recreate the accounts (there are only 5), recreate the print queues and pull the plug on NT4? What would be your suggestions, thoughts, and concerns?

Thank you in advance

3 replies

by istream

If I'm reading this right, and you have five user accounts, scrap it and start over. Migrating may cause more headaches than its worth (and may bring baggage with it). You will need to pay close attention to user profiles on the workstations (changing from one domain to another will cause a new profile to be created). Free tools exist to point a new profile to an old one and are generally useful. Good luck!

by maniacman

I'd opt to use the ADMT tool and setup the new server in it's own pristine forest and domain, as you'll only need a single domain model based on the small size of your organization. When you install the new Windows 2003 server and promote it to a DC in it's own forest and domain, set the forest and domain functional level to Windows 2003 Interim in the meantime, which will allow for the migration of NT4 user, computers, and permissions over using the ADMT tool, which I believe is now at version 3. You're better off creating a new forest, as you'll have the pleasure in knowing that any issues or bugs in the NT4 domain won't get moved over to the new AD environment. Once your migration of users, computer, data, and permissions are complete, you can raise the forest and domain functional levels to Windows 2003 native on the new environment and proceed to setup additional domain controllers which you can then use to disperse your FSMO roles on so as n not to have all FSMO roles on a single DC, which is a disaster waiting to happen if that DC craps out. Regarding print queues, you'll have to recreate them given that you only have a few in your small environment, but I'm sure there a tool out there to migrate print queues as well.

This discussion is closed to new replies.