Upgrade from 2016 to 2022.

[rbjames]

Hi,

 

We have a Server 2016 Hyper-v server with 2 server 2016 VMs and a third 2016 server running papercut mf and paxton net2 v6 and Salamander. I have a second hyper-v 2016 host in a different building which the main one replicates to. I'd like to update everything to server 2022 and I'd just like some advice on the best order to do the upgrade. The hyper-v servers are joined to the domain. We are in a hybrid environment joined to AAD and nearly all of our data is in M365 Sharepoint/Onedrive/Exchange. All clients are Windows 11 domain joined with management from local group policy and intune.

 

Here's what I'm thinking:

 

1. Stop replication (the second host acts as the backup).

2. Upgrade both DC VMs in place

3. Upgrade 3rd server in place

4. Upgrade Server 2016 with Hyper-V to 2022

5. Test everything thoroughly

6. Turn on replication to pull through the upgraded servers

7. Finally upgrade the secondary server 2016 Hyper-V to 2022.

 

Does that sound like a sensible plan? I know I need to check the printer drivers for compatibility.

 

Thanks,

Richard

[simpsonj]

I've always been wary of upgrading DC Server versions, but that could just be me... Instead I tend to build new servers, add the DC roles, then demote the old servers.

 

The process of updating server OS has improved, but there is always something (a service or role) that needs some TLC after the upgrade in my experience.

 

Finally, ensure that the the Hyper-V configuration version of your VMs is compatible with the Hyper-V host. With that in mind, I would probably swap steps 6 and 7 around, as you may find that the VMs won't work on Server 2016 once/if they've been upgraded to work on Server 2022.

[CrootUK]

We have just been inplace upgrading all our servers across the trust from 2019 to 2022 everything and anything, with no real order unless its “clusters or services with multiple servers” we haven’t had any problems with 95% of them, have had 1 rds and 1 file server that failed to upgrade and were rebuilt.

 

Hope all goes smoothly for you!

[dapaulio]

I've always been wary of upgrading DC Server versions, but that could just be me... Instead I tend to build new servers, add the DC roles, then demote the old servers.

 

The process of updating server OS has improved, but there is always something (a service or role) that needs some TLC after the upgrade in my experience.

 

Finally, ensure that the the Hyper-V configuration version of your VMs is compatible with the Hyper-V host. With that in mind, I would probably swap steps 6 and 7 around, as you may find that the VMs won't work on Server 2016 once/if they've been upgraded to work on Server 2022.

 

I too always wary of in place upgrade of the dc’s. Been burnt once in my career by doing so. Likely a lot more reliable these days but also like that it’s a clean install.

So alway spun up a couple new vms, promoted and transferred the roles, demoted then decommissioned the server. Not rushed each stage may have a couple days/weeks before promo and decommissioning of old servers

 

Personally never done hyper v but would probably be more cautious and normally come inline with a server refresh

Edited August 21, 2024 by dapaulio