How to replace a domain controller and keep the computer name and IP the same?

I had this question after viewing how to replace a domain controller and keep the computer name and IP the same.

From that question's accepted solution:

Here is a step by step.
http://blog.zwiegnet.com/windows-server/migrate-server-2003-to-2008r2-active-directory-and-fsmo-roles/

I would create the DC as another name then once you have removed the old DC from the Forest or demoted to a member server you can then do the rename and re-ip.


Since you indicate this is a software requirement, you should indicate there will be a minimal amount on downtime with the rehome and rename but that should be pretty straightforward since it is a single DC environment.

Rename DC
http://technet.microsoft.com/en-us/library/cc794951%28v=ws.10%29.aspx

Is there a step by step guide since that initial link is not working now?
LVL 19
Kyle SantosQuality AssuranceAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Cliff GaliherCommented:
The safest way to of this is to follow "normal" guides and just do it twice.

Add a new temp DC using normal guides.

Demote and remove old DC.

Add new DC with the same name and IP address you removed using normal guidance.

With that said, Active Directory is designed to be agnostic to names and IP addresses. The only reason to do this is if another LOB app has a requirement... In which case I'd ask why you are running LOB apps on a DC...or because it is a cosmetic request (my machine names are DC1, DC2, DC3, and it'd leave a gap!) in which case I'd ask if fixing a purely cosmetic preference is worth the extra man-hours, extra change management and potential risk.

So yes, it's doable. But I'd suggest that needing to do so USUALLY is a sign that something is bring done wrong anyways.
0
Shaun VermaakTechnical SpecialistCommented:
You can always double-bind the IP address and add the old computer name as an additional hostname with this command
netdom computername currentName /add:AdditionalName.domain.com

Open in new window

0
Ben Personick (Previously QCubed)Lead Network EngineerCommented:
if you are running new OSs (windows 2008R2 and forward) this process is exceedingly simple, but ALWAYS assumes you have two DCs to begin with...do you?

if not, then prior to following this build sequence, build a second DC.

(That new 2nd DC will preferably become permanent. --  I highly reccomend you always have two DCs so you don't get screwed if something happens to one. -- but could be removed at the end if you are willing to take the risks of having only one DC).


assuming you currently have two DCs:

step 1)  Make sure replication to DC2 is running well, '  repadmin /replsum. '


step 2) Move all fsmo roles to the secondary DC (assuming this one your replacing is your primary.)

step 3)  Move any function that are on the server, such as DHCP, etc. over to the secondary server ans make sure its functional (shut down function in existing DC and test)

step 4) Assuming this is all new to you, test all is well - turn off the old DC01 for a few days and make sure things are running smoothly.

step 5) Power on the old DC01, make sure it is replicating correctly again (repadmin /replsum )

step 6) Demote the old DC01, reboot the system

step 7) Unjoin DC01 from the domain, reboot the system

step 8) Log in, change tbe name of the sgstem and its IP (or just shut it down as preferred)

step 9) Make sure the object with the DCs name is femoved from AD, and DNS (delete by hand if not.)

step 10) Build a new system with the same name and IP as the old DC.

step 11) Promote the new system to a Domain Controller

step 12) Confirm replication

step 13) if preffered: move FSMO roles and any functions bacl to this DC.
0

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
Kyle SantosQuality AssuranceAuthor Commented:
Thank you.
0
Ben Personick (Previously QCubed)Lead Network EngineerCommented:
Glad to help :)
0
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
Microsoft Legacy OS

From novice to tech pro — start learning today.