Replacing Servers in an Existing Domain

Posted on 2006-04-08
Last Modified: 2010-05-18
We have a domain consisting of a Domain Controller, a Terminal Server, and an Exchange Server. OS is Win 2003 Server. The DC and Term. Server both need to be replaced however we are concerned that this will affect the Exchange Server. The computer names will not change nor will the IP addresses and the DNS settings will be the same when the two computers are replaced. What will be the result of this change when the Exchange Server is confronted with these new computers?
Question by:Generator
    LVL 95

    Expert Comment

    by:Lee W, MVP
    If you do things right, there will be no change.

    Keeping the same names will cause this to take longer than it should, but if need the names you need the names:

    1.  Add new server with a NEW NAME and a different IP (we'll change it later) and run DCPROMO on it to make it a domain controller.
    2.  Once the new server is a domain controller, transfer the FSMO roles, DNS, and global catalog to it.
    3.  Run DCPROMO on the existing DC.  This makes it a member server.
    4.  Rename the original DC to something else and change it's IP.
    5.  run DCPROMO on the original server and promote it to a DC again.
    6.  Transfer the FSMO roles, GC, and DNS back to the original server with the new name.
    7.  Run DCPROMO on the new server DEMOTING it so it is no longer a DC.
    8.  Rename the new server to the old server's name and change its IP to the old server's IP.
    9.  Run DCPROMO on the new server and make it a DC again.
    10.  Transfer the FSMO roles, DNS, and GC back to the new server using the old name and IP.
    11.  Demote the old server by running DCPROMO again.
    12.  Remove the old server from the network.

    BUT, how many DCs do you currently have?  If only one, then leave the original Domain Controller in place and just add another - this will give you redundancy and help ensure if a DC fails, your mail and network doesn't.

    Author Comment

    This is a case of too many hands in the pot. We came to this company after a number of different techs tried to peacemeal this system to keep it going and consequently we were called in to "fix" things. The Terminal Server was in need of replacement due to wear and tear and upon looking at the way the DC was setup (improperly) we felt it was best to also replace that unit due to numerous errors, lockups, AD errors and slow response time. The only good part of the system was the exchange server. We have 50 users that require access to the system (locally and remotely) and down time is not acceptable (weekend job).
    LVL 51

    Expert Comment

    by:Keith Alabaster
    I'd suggest that you will need two weekends for this.

    First weekend, get the new server in, dcpromo'ed and add the global catalog within the ntds settings. Add in the dns etc and move the FSMO roles to the new server (remember to create any forwarders etc in the dns as well for when you shutdown the first box.... Move any shares, printers etc

    Leave that for the rest of the week to ensure all your replication etc is functioning and as you would expect it to be. Then shutdown the original DC. Does everything continue to operate?
    Now do a full backup of the original DC including system state and dcpromo out.

    Done this so many times now its almost second nature. Lee has given you all the steps but this is a one way thing. Once its dcpromo'ed out your options are gone.

    Author Comment

    We are building the new DC and TS from scratch and were hoping to be able to connect to the existing Exchange server. Due to the multiple error situation on the original DC; we were worried that some of the system errors and security mistakes would propagate to the new units. So basically, we wanted to know if the Exchange server would crash upon being introduced to the new DC and TS. Yesterday we introduced the new terminal server to the existing DC and noted a large number of anomolies appearing in the TS after replication. Thanks to Lee and Keith for your expertise thus far.
    LVL 95

    Accepted Solution

    You can't create a new DC on the side and slam it into place in AD.  You either run DCPROMO on the new server while the new server is a member of your domain - which will essentially copy Active Directory to it - in its current condition - or you start from scratch.   If you want to clean up your AD problems by replacing the DC, you're going to have to create a new domain and new exchange server and export the email from the old one, probably using Exmerge.
    LVL 9

    Expert Comment

    hi, there

    If you are getting problems using the DCPROMO and it for some reason does not work here is a scenario you can try on.

    Use the Ntsdutil on the server type like this:

    connect to server "Servername"
    Seize domain naming master
    Seize infrastructure master
    Seize PDC
    Seize RID master
    Seize schema master

    you can find the full explanation here:

    It worked for me.....


    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
    If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

    732 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

    Need Help in Real-Time?

    Connect with top rated Experts

    20 Experts available now in Live!

    Get 1:1 Help Now