• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 149
  • Last Modified:

Windows 2000 Server to Windows 2003 Server

Ok i am trying to migrate windows 2000 server to windows 2003 server.This is not an upgrade but a migration to a different computer.I only have 16 computers on my network along with 2 users who remote in and we use pcanywhere to connect to other computers in different states as well. I want to see if i have this correct on how to do this migration.

1.First go to windows 2000 server and use the adprep /forestprep  adprep /domainprep
2.Go to 2003 server and run DCPROMO and join it in a exsiting domain
3.After completed go to 2000 server and to active directory domains and trust and go to operations manager and transfer role.
4.Then on the 2003 server go to active directory sites and services and make this a global catalog.
5. Wait until replication is done...NO IDEA HOW LONG TO WAIT AT THIS POINT
6.Remove global catalog from 2000 server.
7.THIS IS WHERE I AM STUCK NOW...What about DNS? When you make the 2003 an exsiting domain controller it doesnt install DNS automatically. Im not sure how to set up and configure it. We have DSL here at work through earthlink.All the users computers have the DNS ip address of the 2000 server. Wouldnt you put in the DNS of Earthlink the ISP Provider?? I am lost at this point.

Any help would be awesome..I am simulating this at home first before i do the real thing
1 Solution
Hello jjatsk,

Sounds like a good plan.  Just a few minor adjustments I would recommend.  

1.  The steps you are taking classify as an upgrade instead of a migration.  In a migration, you would use the ADMT to move users, groups, computers to the new AD.  You would also be changing the domain name.

2.1. I would make the new DC a GC before transferring the roles.  Also, as a minor detail, you would go to the 2003 server to transfer the roles.  Usually the GC takes about 30min to 1.5 hours to replicate, depending on how large your AD is.  You will see a replication event in the replication event log telling you that it is now a GC.  Do not transfer roles until you see that event.

3.  As for DNS, make sure that your zones are AD integrated.  Then install DNS on the 2003 server to make it a writable DNS.  I would make the new DC the primary DNS for the clients without making the old DC the secondary.  That will allow you to test resolving before taking down the old DC.

I know you will probably need more info than this, so please ask.


Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now