Migrating Windows Server 2016 to 2022: In-Place Upgrade vs Clean Install
With Windows Server 2016 losing support on January 12, 2027, the question stops being whether to move and becomes how. There are two honest answers, and the right one depends less on the operating system than on how much accumulated mess the current server is carrying.
The good news first: 2016 goes straight to 2022
Microsoft supports an in-place upgrade from Windows Server 2016 directly to 2022, using installation media. There is no intermediate hop through 2019. Nonclustered systems on 2022 and earlier can jump up to two versions at a time, and 2016 to 2022 is exactly two.
One nuance that catches people planning around Windows Update: the upgrade-through-Windows-Update path only exists for 2019 and 2022 moving to 2025. Coming from 2016 you are mounting an ISO and running setup, which means a planned maintenance window rather than an overnight patch cycle.
If you would rather skip a generation, 2016 to 2025 is also supported from media.
In place or clean install?
| In-place upgrade | Clean install | |
|---|---|---|
| Time per server | Hours | Days, including reconfiguration |
| What survives | Roles, features, settings, data | Nothing, you rebuild it |
| Hardware | Same box | Same or new |
| Inherited problems | Come with you | Left behind |
| Rollback | Restore from backup | Old server still there if new hardware |
| Best for | Clean, well documented servers | Servers nobody fully understands |
The table makes it look like a close call. In practice one question decides it: can you list, from memory or documentation, everything this server does? If yes, upgrade in place and save the days. If the honest answer is "mostly", a clean install on new hardware is the safer path, because it forces you to discover what is actually running before you cut over rather than afterwards.
The second decider is hardware age. A server bought for Windows Server 2016 is at least seven years old. If it is out of warranty, an in-place upgrade buys you a supported OS on unsupported hardware, which is only half a solution.
Prerequisites that stop an upgrade cold
Check these before you book the window, not during it.
- NIC teaming must be disabled before the upgrade, and re-enabled afterwards. This is the single most common reason an in-place upgrade fails partway.
- You cannot switch installation type. Server Core stays Server Core, Desktop Experience stays Desktop Experience. Changing that requires a clean install.
- You cannot downgrade edition. Standard can go to Datacenter during an upgrade, but Datacenter cannot come back to Standard.
- Language cannot change, and 32 bit to 64 bit is not a thing on any release since 2008 R2.
- Domain controllers need care. A licensed domain controller cannot be converted to a retail version during upgrade, and there is separate Microsoft guidance for upgrading DCs that is worth reading before you touch the first one.
- Servers booting from VHD cannot be upgraded in place at all.
- Every version upgrade needs its own licence. Unlike Windows on the desktop, there is no free hop between server versions.
The order that works
- Back up, and restore that backup somewhere. An untested backup is a hope, not a plan.
- Record what the server does: roles, features, scheduled tasks, certificates, shares, printer queues, firewall rules and anything hand-edited. Take screenshots of anything configured through a GUI.
- Check vendor support matrices for every application on the box against Windows Server 2022. This is where migrations stall.
- Disable NIC teaming.
- Mount the media and run setup, choosing to keep files, settings and applications.
- Reboot, then verify in this order: services started, roles present, shares reachable, application logs clean, activation valid.
- Re-enable NIC teaming and confirm the network is back to its intended configuration.
Allow half a day per server for the first one and rather less afterwards, once you know which surprises this particular estate produces.
The licensing you need
Windows Server 2022 is licensed per physical core with a minimum of 16 per server. A two socket box with eight cores per socket lands exactly on the minimum, which Windows Server 2022 Standard covers. Above 16 cores you top up in pairs with a 2 core licence.
Client access licences do not carry over from a version upgrade either. If you are moving to 2022, your CALs need to be 2022 CALs. Anyone using Remote Desktop needs an RDS CAL from our Windows Server CAL range on top of their regular one.
The full picture is in our Windows Server 2022 licensing guide.
One thing worth doing while you are in there
An in-place upgrade is the rare moment when everyone accepts that the server will be down. That makes it the cheapest opportunity you will get to also fix the backup you have been meaning to test, remove the roles nobody uses any more, and write down what this machine does.
Servers do not become undocumented overnight. They become undocumented one skipped maintenance window at a time.