From d6fdb9f7a105058b858c9a468147b9a4f2131d0c Mon Sep 17 00:00:00 2001 From: jodeffen <153466573+jodeffen@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:58:18 -0600 Subject: [PATCH 1/2] Add note to clarify upgrade path. Note is needed to make it clear the Failover Clustering feature does not allow skipping a version of Windows when performing an OS upgrade. --- .../failover-clustering/Upgrade-Option-Same-Hardware.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md b/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md index b30246e35d..4f4cd54f0d 100644 --- a/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md +++ b/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md @@ -22,6 +22,9 @@ Upgrading the operating system on an existing failover cluster is only supported Before any upgrade of your failover cluster, please consult the [Windows Server upgrade content](../get-started/upgrade-overview.md). When you upgrade a Windows Server in-place, you move from an existing operating system release to a more recent release while staying on the same hardware. Windows Server can be upgraded in-place at least one, and sometimes two versions forward. For example, Windows Server 2012 R2 and Windows Server 2016 can be upgraded in-place to Windows Server 2019. Also keep in mind that the [Cluster Migration Wizard](https://blogs.msdn.microsoft.com/clustering/2012/06/25/how-to-move-highly-available-clustered-vms-to-windows-server-2012-with-the-cluster-migration-wizard/) can be used but is only supported up to two versions back. The following graphic shows the upgrade paths for Windows Server. Downward pointing arrows represent the supported upgrade path moving from earlier versions up to Windows Server 2019. +> [!NOTE] +> While Windows Server has the ability to upgrade two versions forward (ex: from 2012 R2 to 2019), the Failover Clustering feature only supports upgrading to one version higher (ex: from 2012 R2 to 2016). + ![In-place Upgrade Diagram](media/In-Place-Upgrade/In-Place-Upgrade-1.png) The following steps are an example of going from a Windows Server 2012 failover cluster server to Windows Server 2019 using the same hardware. From 90865492c05d9bded6c6d7be5ebbcd6fbc59ec02 Mon Sep 17 00:00:00 2001 From: jodeffen <153466573+jodeffen@users.noreply.github.com> Date: Wed, 13 Nov 2024 11:04:27 -0600 Subject: [PATCH 2/2] Add note for Failover clustering upgrade path. --- .../failover-clustering/Upgrade-Option-Same-Hardware.md | 1 + 1 file changed, 1 insertion(+) diff --git a/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md b/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md index 4f4cd54f0d..b5b8b3f77c 100644 --- a/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md +++ b/WindowsServerDocs/failover-clustering/Upgrade-Option-Same-Hardware.md @@ -24,6 +24,7 @@ Before any upgrade of your failover cluster, please consult the [Windows Server > [!NOTE] > While Windows Server has the ability to upgrade two versions forward (ex: from 2012 R2 to 2019), the Failover Clustering feature only supports upgrading to one version higher (ex: from 2012 R2 to 2016). +
![In-place Upgrade Diagram](media/In-Place-Upgrade/In-Place-Upgrade-1.png)