Jun 27 2022 06:18 AM - edited Jun 27 2022 06:24 AM
Hi,
I have a DC running on 2012r2 (where FSMO resides) and also on 2016 as a backup (2012 schema of course). I’m planning on demoting the 2012r2 DC and promoting a 2022 DC in its place. The new server is already spun up and has been added as a third DC, I just need to turn the old one off. When I’m done I’d like the new 2022 DC to have the same IP as the old one so I don’t have to run around my (admittedly small) network repointing any confused machines to it.
Here’s my game plan:
(We’re fewer than 100 users and I’ll be doing this on a weekend … already warned people things may be down temporarily.)
Move FSMO from DC2012r2 to DC2016
Demote DC2012 and turn it off.
Change the IP of DC2022 to match what DC2012 was.
Move FSMO to DC2022.
Upgrade the schema to 2016.
Any steps you people, with way more knowledge of DCs than I, see that I’m missing?
Thanks,
Jeff
Jun 27 2022 11:52 AM
Demote DC2012 and turn it off.
At this step I'd check the health is 100% (dcdiag, repamin tools) and perform cleanup if needed.
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-contr...
also clean up DNS records of demoted server.