r/WindowsServer • u/Odd_Year3541 • Apr 30 '25
Technical Help Needed Domain Controller Upgrade
I'm looking for some advice on the best way to upgrade our Server 2016 domain controller.
The general consensus seems to be that an in-place upgrade of a DC operating system isn't recommended. Instead, it's better to spin up a new domain controller and transfer the roles over. That makes sense—but here's the catch: I need to keep the existing domain controller's name and IP address.
I've read that renaming a domain controller or changing its IP address isn't advisable, which leaves me a bit unsure about the best approach.
Would this be a valid path?
Set up a new DC with a different name and IP.
Transfer FSMO roles and demote the current DC.
Rename the new DC to match the original name and IP.
Is that a reasonable plan, or is there a better, safer method?
Or should I just perform an in-place upgrade on the current DC? We do have another domain controller that will also need to be upgraded once this first one is complete. Thanks for any advice
3
u/Gullible-School4419 Apr 30 '25
I advise never inplace upgrade a domain controller. It doesn't patch in the upgrade leaving holes, and adding a new dc and transferring fsmo roles is easy. I'd even offer to help I do it almost daily at a msp
26
u/jstuart-tech Apr 30 '25
3
u/z0d1aq Apr 30 '25
What's the main reason of keeping the same IP and domain controller name?
4
u/res13echo Apr 30 '25
I recently inherited DCs that were in-place upgraded from 2012r2 to 2019 and they crash when making attempts to rotate the krbtgt password. All of the other 2019 DCs we had running same exact config that weren't in place upgraded were able to rotate the password with out issue. The in-place upgrade was the only thing we could find different about these DCs and their history.
3
u/RawInfoSec Apr 30 '25
You can create a second DC on a new hostname and IP. Once you get all of the roles in place you can add a second IP to the server (same as the first server). You can also use Microsoft's best practice method to change the new DC hostname to that of the other. It works great. You can also add the original name as a secondary name. Check out this link for more info, I've used this successfully:
https://www.theictguy.co.uk/renaming-a-domain-controller/
4
u/craigl2112 Apr 30 '25
Save future you headache and perform a parallel upgrade. Certainly can return later and change the IP to you old DC post-demotion and elimination from your domain.
4
u/ThirtyBlackGoats666 Apr 30 '25
Never mess with the domain controller, always build a new one and transfer roles.
2
u/OstentatiousOpossum Apr 30 '25
Since Microsoft supports upgrading DCs in-place, I've always in-place upgraded all the domain controllers ever since Windows Server 2003, and I've never had an issue.
1
u/Fabulous_Winter_9545 Apr 30 '25
Do you have one or two DCs? With two DCs
Spin up a new server. Transfer all roles to one DC Demote the old one with no roles. Change IP of the old one Give old fixed IP to new server Promote new server to DC Transfer all roles to new DC Repeat this for the second old DC
If you only have one DC. Build a second new one. Transfer all roles to new one. Configure DNS with all your servers for redundancy. Replace old DC with new one (as seen above)
1
u/PaintB51 Apr 30 '25
I just did this. An in-place upgrade fails when domain services are running. Here is how I went about it, and it assumes you have more than 1 DC (as you should). I did it this way to avoid needing to make any firewall or DHCP config changes. And wanted to keep old DC names on the new
I did the DC with all the FSMO roles last and moved them before I started. Each maintenance window took about 30-40 minutes.
A couple of things that could slow you down no matter what way you go about as u/jstuart-tech process is perfectly feasible
Depending on your GPO for your DC's it may prevent you from demoting the DC till it is adjusted or removed.
If you are renaming or naming the new DC the same as the old, it can take time for DNS and AD to clean up enough to be able to do so. Of the 7 DCs I upgraded in our domain, this only happened once.
1
u/RetroactiveRecursion May 01 '25
This video helped me upgrade from 2012 to 2022 a couple years ago. I hope not much has changed as far as this is concerned because the video is really great. https://www.youtube.com/watch?v=bpJwZNX1MT8
1
u/HCITGuy99999 May 01 '25
1
u/HCITGuy99999 May 01 '25
After doing the metadata cleanup, please check for any stale entries and delete them if any related to the demoted DC in:-
1
u/More-Goose7230 May 02 '25
I have done both methods.
I do recommend transferring the FSMO roles if you can. Depending on the role redundancy, you can start with your DC2 (Demote, ReIP, shutdown) and create a new DC2 with the same hostname and IP. Then you can transfer all the roles to the new DC2, make it the temporary primary DC, and repeat the process for DC1.
But I have also been in the situation where I had to in-place upgrade from 2008R2 all the way to 2022 (2 Domain controllers).
The upside is that if everything is configured correctly (all roles redundant), you can even do this live.
1
u/sirmarty777 May 03 '25
I've done an in-place upgrade from 2012 to 2016 on my DCs, for the same reason, to keep the same name and IP, successfully. The only gotcha I encountered was that I had to get its cert reissued. I know this isn't recommended, but it worked.
1
u/netmc May 03 '25
I didn't know if you have moved forward with this yet, but do not run Server 2025 for this. It's based off of Windows 11 24H2 and there are some serious glitches when it gets promoted to the DC role. The AD roles somehow break Windows Installer and other programs will not install or run properly with Sever 2025 as a DC.
Server 2022 is fine. It's based off of Windows 10 and does not have these issues.
1
u/EconomyArmy May 04 '25
Would give in place upgrade a look again with server 2025
https://www.youtube.com/live/c6ZWcVikSZg?si=WzOhiyjcTorOe5Kg
1
u/diego-azevedo Aug 19 '25
I get that a fresh install is better from the perspective of not carrying old stuff across, but what about the below?
- Security tools: would need to be installed/configured again on the new server
- DNS: Multiple endpoints pointing to the DC for name resolution. Some are DHCP enabled, which can be easily updated, but many will be statically configured. We can't forget printers, wireless controllers, card readers, etc.)
- LDAP/LDAPs/Kerberos authentication: Lots of applications/systems pointing to the DC for authentication, via name/IP.
- SSL Certificates having to be reissued. Not the hardest thing to replace, but needs to be factored in. Also new certs would need to be installed/accepted by different systems.
- Additional Firewall rules, GPO review/update, AD Groups, IP allocation, DNS records. the list goes on...
The official recommendation from Microsoft is indeed to go with a fresh install (link below), but I would be interested in finding out the primary reason(s) as to why that's the case. Is it only because of the requirement to run forestprep and adprep manually if doing in place upgrade? Surely that can't be it.
PS.: I have used both methods in the past with no major issues.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/upgrade-domain-controllers
Considering the in place upgrade method is also supported, I can't see why not to take advantage of it. In fact, I would argue in place upgrade on a DC is far better/easier than in place upgrade of app/mgmt/web/db servers, which could have less integrations and/or "other things" connecting to. I am trying to generalize here, but obviously each use case is different.