This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello.
I have quite a few multi node SQL Always on MSCS clusters currently using Server 2016.
I've been reviewing the documentation on Cluster OS Rolling Update and it suggests that the in place upgrade of existing cluster nodes isn't supported and a strategy of evict, rebuild, join is recommended. https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade
My question is, Is an in-place upgrade of an existing node (without evicting the node) a Microsoft supported upgrade strategy? For example an in place upgrade of Server 2016 to Server 2022.
Many thanks.
Chris
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
Hi,
While in-place upgrades are generally supported for standalone servers, they are not recommended for cluster nodes due to potential compatibility and stability issues. Your failover cluster may need to be stopped or restarted. The recommended approach is indeed to use the evict, rebuild, and join strategy.
