Mixing node operating systems in a cluster is only supported for a rolling cluster upgrade scenario. The maximum allowed distance between host operating systems is 1. So, if you've got 2012 R2, then nothing after 2016 is supported in the same cluster. In no case are mixed-level clusters supported long-term. This mode is specifically meant to allow you to upgrade or replace the members one at a time until the cluster is homogenous, then update the functional level. Mixing them will probably work, but if anything goes wrong, you're probably going to have trouble getting help. And by "anything", that could even include things that have nothing to do with the operating system levels. The operating system inside virtual machines does not matter. On paper, Microsoft supports any Windows or Windows Server operating system inside a virtual machine as long as it is no further than one version past its host. On paper, they support the same level and downward to the oldest Microsoft OS until it's end-of-life. In practice, they don't usually look that closely and things just work. But, if you have a cluster with mixed OS nodes, all bets are off. Your biggest practical concern is trying to migrate VMs. The host operating systems probably won't care, but migrating between different CPUs is risky on a good day. Going from hardware from the 2012 R2 era to hardware in the 2022 era will almost certainly not work even with compatibility mode on. You can shut the VMs down and migrate them across, but expect Live and Quick Migration to fail.
Joining Windows Server 2022 into a mixed OS Hyper-V cluster
Hi everyone,
I have a Hyper-V cluster consisting of three nodes running Windows Server 2012 R2 and Windows Server 2016. I want to replace one of the nodes running Windows Server 12 with a new, beefier one running Windows Server 2022. My question is, can I do this without causing compatibility issues and preventing the cluster from communicating properly, while maintaining a Cluster Functional Level of 8.0 (so the one 2012 R2 node still can be part of the cluster)?
Also I have multiple windows Server 2012 R2 VM instances running on the cluster of this 3 nodes, however I am concerned whether they remain functional during this procedure.
I was not able to find any relevant information regarding the topic, so I'd appreciate any advice or guidance on how to proceed with this replacement. (If it is possible at the first place.)
Thank you in advance for your help!
3 answers
Sort by: Most helpful
-
-
Limitless Technology 43,951 Reputation points
2023-03-30T10:23:30.9566667+00:00 Hello
Thank you for your question and reaching out. I can understand you are having query\issues related to Cluster update.
I would advise you to upgrade all nodes to same OS which is 2022. There are many new security measures included with Server 2022, particularly those related to TPM. While moving virtual machines between nodes, compatibility issues with CPUs will arise. It might not live migrate even if you enable the CPU compatibility options.
Moreover, failover cluster validation won't succeed without warning you.
Reference:
--If the reply is helpful, please Upvote and Accept as answer--
-
Ricky Saull 0 Reputation points
2023-09-05T17:24:13.1366667+00:00 On paper, they support the same level and downward to the oldest Microsoft OS until it's end-of-life.
@Eric Siron What are the chances that you would have a link?