Moving primary W2K DC to a new machine

I have two W2K DC's in a child domain, one is primary - containing DHCP, DNS, GC and the other is GC / Active dir only.  The primary DC is aging and I want to purchase a new server.  Is it best to purchase a new server, name it something else, promote to DC with DNS and DHCP then demote the old primary server, or is it better to send the server roles (DNS, DHCP) to the current secondary machine, demote the current primary and then purchase the new server and promote it?  I don't think I can call it the same computer name but that should be ok.   Would Schema still work properly?
I would also like the new server to be Windows 2003 if possible.  Thanks for any suggestions
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi chitchcock,

can be done quite easily with a clean install of the new server

below are my standard install steps, however if this is your first win2k3 server in the network you are going to need to extend the schema prior to doing the following

An additional not, if you are adding a 2003 R2 DC, then you will need to run the adprep tools from the second disk in the package

1) Promote your new machine as an additional domain controller in an already existing domain - this will allow AD to replicate to the new server
2) Make sure DNS is AD integrated on your old DC to allow all DNS replications also
3) Transfer the FSMO roles to the new server;en-us;255690
4) Make the new DC a Global Catalog under Sites and Services
5) Deactivate DHCP on the old DC (if used) and recreate the scope on the new DC
6) Run DCDIAG to make sure all is well and replication is fine
7) Demote the old DC if you dont intend to keep it as a backup
8) Recreate Shares etc on the new server
9) Reinstall printers and share them etc....

this will allow you to have the complete AD directory on the new DC and clients will barely be aware of any changes

If you get stuck just post


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
chitchcockAuthor Commented:
Thanks for your help Jay Jay70.  
no worries :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.