You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md
+6-20Lines changed: 6 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,16 +23,17 @@ To keep your Azure Local service in a supported state, you have up to six months
23
23
24
24
::: zone-end
25
25
26
-
27
-
28
26
::: zone pivot="os-24h2"
29
27
28
+
This article describes how to upgrade the operating system (OS) for Azure Local from version 20349.xxxx (22H2) to version 26100.xxxx (24H2), via PowerShell.
30
29
31
-
This article describes how to upgrade the Azure Stack HCI operating system (OS) via PowerShell. Supported upgrade paths include:
30
+
With the 2505 release, a direct upgrade path from version 20349.xxxx (22H2) to version 26100.xxxx (24H2) is available. Skipping the upgrade to the version 26100.xxxx is one less upgrade hop and helps reduce reboots and maintenance planning prior to the solution upgrade.
32
31
33
-
- From OS version 20349.xxxx to 26100.xxxx.
32
+
- Make sure to consult with your hardware vendor to determine if version 26100.xxxx OS is supported before performing the upgrade.
33
+
- After the OS upgrade, you can wait for the solution upgrade and the drivers to become available. This option is currently in preview and is not recommended for production workloads.
34
+
- There is an exception to the preceding recommendation if you are using stretch clusters. Stretch clusters should directly move to version 26100.xxxx (24H2) in 2508. This version contains critical bug fixes.
34
35
35
-
- From OS version 20349.xxxx to 25398.xxxx.
36
+
For more information about the various upgrade paths, see the blog post on [Upgrade Azure Local to new OS version](https://techcommunity.microsoft.com/blog/azurearcblog/upgrade-azure-local-operating-system-to-new-version/4423827).
36
37
37
38
> [!IMPORTANT]
38
39
> - This article covers OS upgrades only. Do not proceed if the solution upgrade is complete or Azure Local 2311.2 or later is deployed. To check if your system is already running the solution, run the `Get-StampInformation` cmdlet. If it returns output, your system is already running the solution, and you should skip these steps.
@@ -76,21 +77,6 @@ To upgrade the OS on your system, follow these high-level steps:
76
77
77
78
::: zone-end
78
79
79
-
## Choose an upgrade path
80
-
81
-
To upgrade your OS from version 20349.xxxx (22H2), choose one of the following upgrade paths
82
-
83
-
-**Upgrade to OS version 25398.xxxx**: You can upgrade your OS version to 25398.xxxx (23H2) and apply solution upgrade. This is our *recommended* option.
84
-
85
-
-**Upgrade OS version 26100.xxxx** (Preview): With the 2505 release, a direct upgrade path from version 20349.xxxx (23H2) to version 26100.xxxx (24H2) is available. Skipping the upgrade to the version 26100.xxxx is one less upgrade hop and helps reduce reboots and maintenance planning prior to the solution upgrade.
86
-
87
-
After the OS upgrade, you can wait for the solution upgrade and the drivers to become available. This option is currently in preview and is not recommended for production workloads.
88
-
89
-
- There is an exception to the preceding recommendation if you are using stretch clusters. Stretch clusters should directly move to version 26100.xxxx (24H2) in 2508. This version contains critical bug fixes.
90
-
- Make sure to consult with your hardware vendor to determine if version 26100.xxxx OS is supported before performing the upgrade.
91
-
92
-
For more information about the various upgrade paths, see the blog post on [Upgrade Azure Local to new OS version](https://techcommunity.microsoft.com/blog/azurearcblog/upgrade-azure-local-operating-system-to-new-version/4423827).
0 commit comments