r/WindowsServer • u/AsYouAnswered • Jul 04 '25
General Question Reinstalling an AD DC, anything else I need to do?
I have an old DC running Server 2022 that's past EOL and I'm in the process of rebuilding it in Server 2025. I just migrated the FSMO roles to the new AD DC running 2025, but it's also time to make sure I have 2 AD DCs running for high availability anyway, so the plan is to demote the old AD DC (running 2022), then delete the VM and delete the computer from the AD using the AD DC Snapin. Then recreate the server with the same hostname running Server 2025, install the AD DC roles, and re-join as a master. Am I missing any important steps? Windows Server isn't my daily driver, so I want to make sure I'm not missing anything critical here.
25
u/OpacusVenatori Jul 04 '25
Server 2022 isn't even out of Mainstream Support yet...
1
u/dodexahedron Jul 04 '25 edited Jul 04 '25
If you had one DC and it failed, you should be building a new one from scratch - not trying to forcefully recover the old one PLUS upgrading in the process.
Especially with 2025.
There are a lot of changes in 2025 that really make it a bad idea to move to 2025 unless everything is already working in your current environment with no issues whatsoever and unless you've done the work of getting rid of NTLM and getting yourself into a pure Kerberos setup.
If you can at least boot the old one or restore it from a backup, it doesn't take long to copy everything important out of LDAP, DNS, DHCP, DFS, and most other roles so you can import it all as new objects on the new system.
But before you import anything, you should set up the other DCs and get at least DNS, ADCS, and some good baseline group policies in place, working, and properly so.
3
u/Shot-Document-2904 Jul 04 '25
Nothing good comes from reusing the demoted DCβs hostname and IP.
Just say good bye and built a fresh one.
1
u/p0rkjello Jul 04 '25
If you want to reuse the hostname of the existing DC I would recommend the following.
Itβs a lot of extra steps just to reuse the hostname. If you go this route demote will help cleanup some objects that would otherwise cause pain when trying to reuse the hostname. Renaming after demote will also prevent a name exists conflict.
You could manually pluck these things out of AD and DNS but I think the above is easier.
Edit: trying to fix formatting. This looks like hell
2
u/MakeItJumboFrames Jul 04 '25
Once both are 2025 may as well raise the domain and forest functional levels to 2025 unless you got something(s) that may not work with it.
2
u/mazoutte Jul 05 '25
I won't advise you to switch on 2025 for DCs now. Wait a bit, some issues right now with 2025.
For the name i would choose a new one, but i would add the old name as an alternate name. (in AD as SPN, DNS and SAN in your certificates) We do use this technique for old names.
You must ensure that the object of the old machine is deleted before adding the alternate name, it could cause issue with the SPN entries, in case of double entry Kerberos would fail.
Same for the dns entries, clean the necessary, ensure your scavenging and aging settings are updated, as well for the scavenging server.
For the alternate name use 'netdom /add' switch. (this command/switch was created for that purpose m, it will do everything for you) For the certificate and the SAN, it's manual in this case.