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/post-upgrade-steps.md
+35-12Lines changed: 35 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Post-upgrade steps on Azure Local via PowerShell
3
3
description: Learn how to perform the post-upgrade tasks for Azure Local using PowerShell.
4
4
author: alkohli
5
5
ms.topic: how-to
6
-
ms.date: 10/22/2024
6
+
ms.date: 03/03/2025
7
7
ms.author: alkohli
8
8
ms.reviewer: alkohli
9
9
ms.service: azure-local
@@ -31,6 +31,20 @@ Before you begin, make sure that:
31
31
- Make sure that all the machines in your system are healthy and show as **Online**.
32
32
- You have access to a client that can connect to your system. This client should be running PowerShell 5.0 or later.
33
33
34
+
## Step 0: Update registry keys
35
+
36
+
Post-OS upgrade, update registry keys on each machine in the system to ensure that Resilient File System (ReFS) volume upgrade is enabled and metadata validation is turned on.
37
+
38
+
Run the following command on each machine in the system to update registry keys:
Once the new OS is installed, you need to upgrade the *cluster functional level* and upgrade the storage pool version using PowerShell in order to enable new features.
103
+
Once the new OS is installed, you need to upgrade the cluster functional level and the storage pool version using PowerShell to enable new features.
90
104
91
105
> [!IMPORTANT]
92
106
> - Post-OS upgrade steps are essential for the stability and performance of your system. Make sure to follow these steps after the OS upgrade.
93
107
94
-
95
108
1. Upgrade the cluster functional level.
96
109
97
110
> [!WARNING]
98
111
> After you upgrade the cluster functional level, you can't roll back to the previous operating system version.
99
112
100
113
We recommend that you upgrade the cluster functional level as soon as possible. Skip this step if you installed the feature upgrades with Windows Admin Center and checked the optional **Update the cluster functional level to enable new features** checkbox.
101
114
102
-
1. Run the following cmdlet on any machine in the system:
115
+
1. Run the following cmdlet on any machine in the system to check the current cluster functional level:
1. After the cluster functional level is upgraded, use the following cmdlet to identify the `FriendlyName` of the storage pool representing your system.
137
+
1. After upgrading the cluster functional level, use the following cmdlet to identify the `FriendlyName` of the storage pool representing your system.
1.[Connect to your system.](#step-1-connect-to-your-system)
35
36
1. Install new OS using one of the other methods:
36
37
1.[Manual upgrade of a Failover Cluster using SConfig.](#method-1-perform-a-manual-os-update-of-a-failover-cluster-using-sconfig)
37
38
1.[Offline manual upgrade of all machines in a system.](#method-2-perform-a-fast-offline-os-update-of-all-machines-in-a-system)
38
39
1. Check the status of the updates.
39
40
1.[Perform post-upgrade steps, after the OS is upgraded.](#next-steps)
40
41
41
-
42
42
## Complete prerequisites
43
43
44
44
Before you begin, make sure that:
@@ -49,6 +49,20 @@ Before you begin, make sure that:
49
49
- You have access to the Azure Stack HCI OS, version 23H2 software update. This update is available via Windows Update or as a downloadable media. The media is an ISO file that you can download from the [Azure portal](https://portal.azure.com/#view/Microsoft_Azure_HybridCompute/AzureArcCenterBlade/~/hciGetStarted).
50
50
- You have access to a client that can connect to your Azure Local. This client should be running PowerShell 5.0 or later.
51
51
52
+
## Step 0: Update registry keys
53
+
54
+
To avoid issues with Resilient File System (ReFS) during OS upgrade, update registry keys on each machine in the system to ensure ReFS volume upgrade is disabled and metadata validation is turned off.
55
+
56
+
Run the following command on each machine in the system to update registry keys:
Follow these steps on your client to connect to one of the machines on your system.
@@ -85,7 +99,7 @@ Depending upon your requirements, you can manually update the OS using SConfig o
85
99
86
100
To do a manual feature update of a failover cluster, use the **SConfig** tool and Failover Clustering PowerShell cmdlets. For more information about **SConfig**, see [Configure a Server Core installation of Windows Server and Azure Local with the Server Configuration tool (SConfig)](/windows-server/administration/server-core/server-core-sconfig).
87
101
88
-
For each node in the cluster, run these commands on the target node:
102
+
For each machine in the cluster, run these commands on the target node:
89
103
90
104
1.`Suspend-ClusterNode -Node <Node Name> -Drain`
91
105
@@ -131,7 +145,6 @@ If there's a critical security update <!--ASK-->that you need to apply quickly o
131
145
132
146
You're now ready to perform the post-upgrade steps for your system.
133
147
134
-
135
148
## Next steps
136
149
137
150
-[Learn how to perform the post-upgrade steps for your Azure Local.](./post-upgrade-steps.md)
1.[Connect to Azure Local, version 22H2.](#step-1-connect-to-azure-local)
35
36
1.[Check for the available updates using PowerShell.](#step-1-connect-to-azure-local)
36
37
1.[Install new OS using PowerShell.](#step-2-install-new-os-using-powershell)
@@ -53,6 +54,20 @@ Before you begin, make sure that:
53
54
54
55
Follow these steps to install the solution upgrade:
55
56
57
+
## Step 0: Update registry keys
58
+
59
+
To avoid issues with Resilient File System (ReFS) during OS upgrade, update registry keys on each machine in the system to ensure ReFS volume upgrade is disabled and metadata validation is turned off.
60
+
61
+
Run the following command on each machine in the system to update registry keys:
1.[Connect to the Azure Local, version 22H2](#step-1-connect-to-azure-local-via-windows-admin-center).
35
36
1.[Check for the available updates using Windows Admin Center.](#step-2-install-operating-system-and-hardware-updates-using-windows-admin-center)
36
37
1.[Install the new OS, hardware and extension updates using Windows Admin Center.](#step-2-install-operating-system-and-hardware-updates-using-windows-admin-center)
@@ -49,6 +50,20 @@ Before you begin, make sure that:
49
50
> [!NOTE]
50
51
> The offline ISO upgrade method is not available when using Windows Admin Center. For these steps, see [Upgrade the operating system on Azure Local via PowerShell](./upgrade-22h2-to-23h2-powershell.md)
51
52
53
+
## Step 0: Update registry keys
54
+
55
+
To avoid issues with Resilient File System (ReFS) during OS upgrade, update registry keys on each machine in the system to ensure ReFS volume upgrade is disabled and metadata validation is turned off.
56
+
57
+
Run the following command on each machine in the system to update registry keys:
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments