Replacing old 2003 DC with new one

[rswift]

Listed below are steps I plan to take to replace an old 2003 DC located in a remote site. It has no FSMO roles on it. All the FSMO roles are split between two DCs here at corporate. This is the first time I've done this so I hope everything works. If you see any major flaws please advise.


• Run NTBACKUP to save common and user directory to new server
• Export DHCP (MS Article ID 325473) and save on new server.
• Uninstall DHCP
• Remove DNS from old server.
• Run DCPROMO to demote old DC.
• Shut down old server.
• Remove computer account from domain.
• Wait 1 hour
• Rename new server to same name as old and change IP address
• Run DCPROMO on new server and make DC
• Install DNS
• Install DHCP and import database (MS Article ID 325473)
• Run NTBACKUP and restore saved common and user directory.
• View event log for errors
• Go have a beer


Thansk in advance

 

[nevets2001uk]

I've not done this myself yet either but it sounds like a reasonable approach to me. I'd consider making it at least 2 beers afterwards though!

Steve G (MCSE / MCSA:Messaging)

 

[pagy]

Why don't you just dcpromo the new box so it's a dc alongside the old box?? Install DNS on it, move DHCP database to it. Then when ready dcpromo the old box out.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[rswift]

Would there be a problem renaming the new DC to the original name and IP address?

 

[pagy]

Does the server have to be exactly the same name and IP address????

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[rswift]

Not really. It would be easy to point the local computers on that network to a different server for their files

 

[pagy]

Do the client machines use mapped drives to access files then?? Do you use a login script?? If so you can just change the login script. If they map the drives manually you could either change it on each machine or you could use this support doc which details how to alias a server name

http://support.microsoft.com/kb/281308

I just think your original proposal is a bit long winded, I'm not saying it would not work but adding a server and making sure everything works on the new server before dcpromoing out your old one is so much safer and very little or no downtime

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[karmic]

I've been blogging some of this stuff lately, it's all step by step. Work if anyone wants to verify...

http://newfierefugee.wordpress.com/

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[rswift]

Thanks all. I think I will keep the old DC in place until every thing looks good

 

[MarkDym]

I recently did this and dcpromo'd the new server while the old (single DC) one was still in place. This allows time for all the active directory data to replicate to the new machine - no need to export data. I'm glad I did as the old one went belly up two days later...

If you are also using the old DC as a file server then you may want to consider using DFS instead of straight share mapping. Once you have DFS setup, the clients map the DFS share once and that's it - any maintenance to shares (e.g. data moved to different file server) is done once at the DFS link. No need to change mappings on all the clients.

I would also make sure you check that VPN (IAS) server (etc), if present, is also moved to the new DC.

Good luck!