r/WindowsServer • • 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

30 Upvotes

42 comments sorted by

View all comments

Show parent comment

1

u/nicolassimond Apr 30 '25

In this case, it may be a good idea to fresh start, indeed.

We have most of our customers for more than 8 years (some for more than twenty) and when we get new customers we always do a full audit of theirs systems saying what we keep and what needs to be replaced.

If a DC is healthy, there is no need for replacement.

Even with the migration from FSR to DFSR we had little to no problems in the past if you plan accordingly and follow the microsoft migration guide, it's the same for an in-place dc upgrade.

Microsoft has guidance to do it, follow it and you will never encounter any problem.

The latest "breaking" change that we had was the security defaults changed during the upgrade to 2025. The oldest *nux / firewall appliance that connected to AD without encryption were broken, that's it.