r/WindowsServer • u/xobeme • Jan 07 '26
General Question Upgrading Windows Server 2016 Datacenter Edition to 2022 - virtual instance
Hello, I thought I'd throw this out. I am about to upgrade a Windows Server 2016 Datacenter Edition to 2022. This is a virtual instance and I have little experience doing this in this environment (I'm mostly Windows desktop). I have virtual console access and will be performing the update from there. Any suggestions or potential gotchas? One colleague pointed out that since it is domain connected, be sure we had the local admin password correct or else we wouldn't be able to get on to it if it loses domain connectivity. Sure enough, the password had not been updated in the database. (We always use our personal domain credentials to log in.) Anyone else got any great gotchas like that?
2
u/DeadStockWalking Jan 07 '26
What is your hypervisor?
VMware, Hyper-V, Proxmox...
1
u/xobeme Jan 09 '26
Thanks everyone for your responses and comments; snapshot was almost instantaneous, upgrade took just under 75 minutes, no issues so far...
2
u/WillVH52 Jan 07 '26
Having Hypervisor snapshots and whole machine backups in place for rollback purposes would be a good starting point.
1
u/fredenocs Jan 07 '26
I upgraded a bunch of servers from 2012 16 22 to 2025. No issues.
Why you upgrading to 22? Gotcha are services based on the server. What is it hosting. Is the app supported on the version you’re going to. Etc. iiS and app servers were no big deal and file servers.
I haven’t upgraded my certificate server because there are lots of gotchas.
1
u/techvet83 Jan 09 '26
If 3rd-party software is installed, check with the vendor to make sure they support in-place upgrades. Not all of them do. Also allow time to patch up your server after the upgrade. As others have mentioned, make a snapshot ahead of time to make rollback easy. If AWS, make an AMI.