Replacing DC in Windows network

Posted on 2006-07-10
Medium Priority
Last Modified: 2010-03-18
Scenario:  I have two servers (one is a f/p DC running WinServ2003; the other is also a WinServ2003 acting as a terminal server).  I am replacing the f/p DC.  Aside from transferring FSMO roles and running dcpromo to make the new server a DC, are there any surprises I should look out for?  Ideally I would like to name the new server the same as the current DC.  Not sure what the best way to do that is.  

Question by:dwd4243
  • 2
LVL 23

Expert Comment

by:Erik Bjers
ID: 17078556
best if you can use the same name and IP address, this will prevent problems on the network.


Author Comment

ID: 17080952
Another question regarding this new server install:  Licensing???   I can look at either of the two servers (the DC and the Term Server) under Admin tools/licensing, and it shows 15 per device or per user licenses.  Am I going to need to purchase and install 15 more licenses for this new DC server?
LVL 23

Expert Comment

by:Erik Bjers
ID: 17082283
Your licenses should transfer, may want to call a reseler who sels Server licenses. CDW is a good one http://cdw.com

LVL 48

Accepted Solution

Jay_Jay70 earned 500 total points
ID: 17087910
will post my standard steps

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

**Note - If introducing a 2003 R2 Server into the network as a DC you will need to run the ADPREP tools from the second cd


you can also download here

this boosts the schema up to cope with R2 functionality

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
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, note if you have a fairly complex or Large DHCP scheme you may want to export and import the database
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

licences will transfer over

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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.

Join & Write a Comment

Have you ever set up your wireless router at home or in the office to find that you little pop-up bubble in the bottom right-hand corner of Windows read "IP Conflict - One of more computers on the network have been assigned the following IP address"…
Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
In the video, one can understand the process of resizing images in single or bulk. Kernel Bulk Image Resizer is an easy to use tool for resizing large number of images. One can add and resize multiple images with this tool in single go. The video sh…
Suggested Courses

622 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question