Skip to content

Commit 98dff5e

Browse files
committed
Updated TOC and removed choose upgrade path
1 parent 42510d4 commit 98dff5e

File tree

2 files changed

+8
-32
lines changed

2 files changed

+8
-32
lines changed

azure-local/TOC.yml

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -279,18 +279,8 @@ items:
279279
items:
280280
- name: About Azure Local upgrades
281281
href: upgrade/about-upgrades-23h2.md
282-
- name: 1. Select upgrade path
283-
items:
284-
- name: Upgrade to 26100.xxxx
285-
href: upgrade/upgrade-to-24h2-powershell.md
286-
- name: Upgrade to 25398.xxxx
287-
items:
288-
- name: Via PowerShell (recommended)
289-
href: upgrade/upgrade-22h2-to-23h2-powershell.md
290-
- name: Via Windows Admin Center
291-
href: upgrade/upgrade-22h2-to-23h2-windows-admin-center.md
292-
- name: Via other methods
293-
href: upgrade/upgrade-22h2-to-23h2-other-methods.md
282+
- name: 1. Upgrade OS via PowerShell
283+
href: upgrade/upgrade-22h2-to-23h2-powershell.md
294284
- name: 2. Perform post-OS upgrade tasks
295285
href: upgrade/post-upgrade-steps.md
296286
- name: 3. Configure Network ATC

azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md

Lines changed: 6 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -23,16 +23,17 @@ To keep your Azure Local service in a supported state, you have up to six months
2323

2424
::: zone-end
2525

26-
27-
2826
::: zone pivot="os-24h2"
2927

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.
3029

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.
3231

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.
3435

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).
3637

3738
> [!IMPORTANT]
3839
> - 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:
7677

7778
::: zone-end
7879

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).
93-
9480

9581
## Complete prerequisites
9682

0 commit comments

Comments
 (0)