Forum Discussion
Microsoft Recommendation on Upgrade Path from 2012R2 to 2022?
- Did a in-place upgrade from 2012 R2 to 2019 just last week for two servers, no issues.. It just depends on the installed software/drivers/anti-virus etc if it will work. But nobody thinks twice about upgrading Windows 7 tot 8 to 8.1 to 10 to 11 😉 Upgrading does work and having issues in the future because of it is something of the past in my experience. If you can migrate to a new server without a lot of work.. Please do so, but it is still an option (But keep your backup and snapshots close)
This is even more true when you try to fill a 10+ years gap.
Do yourself a favor and plan a side-by-side migration with a fresh install of Windows Server 2022.
"Avoid in-place upgrade whenever you can"
This is very difficult to do when the DC has hundreds of users and computers and other roles running, especially when you are a new sys admin with no connection to the prior sys admin of anything else the DC vm may be doing that is critical that you can't migrate by doing a fresh install.
Chrisntpsfor new domain controllers it's better just to spin up a new server 2022 and join it to the domain then make it a domain controller (DNS Server) I've removed all other roles from my domain controllers such as (DHCP, CERT, KMS, other roles) this way it's easier to upgrade domain controllers by adding a new DC already running the latest OS. if you haven't move the roles out of your DC I recommend you to first work on moving DHCP, KMS, Certificate of Authority or any roles you may be running on that DC aside from (DNS only) this role must stay in the DC imho.
Chrisntps If is a Domain Controller the recomendation is to create a new Windows server 2022, add the roll of Domain Controller and move all the DC rolls to this new one, then "demote" the old one.
