Hyper-V Failover Cluster 2016 Inplace Upgrade to 2019

SDS 216 Reputation points

Hello Community,

"Upgrading the operating system on an existing failover cluster is only supported when going from Windows Server 2016 to Windows 2019." as mentioned in https://learn.microsoft.com/en-us/windows-server/failover-clustering/upgrade-option-same-hardware

Does that mean I can Pause+Drain the node and perform an InPlace Upgrade from 2016 to 2019 without evicting the node from the cluster? Any additional steps needed?

Thank you!

A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,597 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
969 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Alex Bykovskyi 1,831 Reputation points


    You will still need to Pause+Draing roles on node1, evict it from the cluster rebuild it with Windows Server 2019, install all roles and features and then add it back to the cluster. Might help:


    Alex Bykovskyi

    StarWind Software

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose

  2. Raed M. Mary 51 Reputation points

    Delete the comment since it was placed in the wrong question.

    0 comments No comments

  3. Raed M. Mary 51 Reputation points

    One more thing I want to add to the discussion, Hyper-V server 2022 no longer support NIC Teaming. The new technology called "Switch Embedded Teaming (SET)"

    0 comments No comments