Merge pull request #17654 from ManikaDhiman/md-upgrade-changes

prmerger-automator[bot] · web-flow · commit 19207a1ba714 · 2025-04-15T20:14:34.000Z
Changes to the registry key section of Upgrade articles
diff --git a/azure-local/update/about-updates-23h2.md b/azure-local/update/about-updates-23h2.md
@@ -82,7 +82,7 @@ Solution updates managed by this feature contain new versions of the Azure Stack
 This solution is the recommended way to update your Azure Local.
 
 > [!NOTE]
-
+>
 > - Azure Local update includes updates for all components, including Azure CLI, PowerShell, and any extensions. Microsoft does not support out of band updates for individual components. The out of band updates could lead to incompatibility with Application Control for Windows.
 > - Customer workloads aren't covered by this update solution.
 
diff --git a/azure-local/upgrade/upgrade-22h2-to-23h2-other-methods.md b/azure-local/upgrade/upgrade-22h2-to-23h2-other-methods.md
@@ -3,7 +3,7 @@ title: Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via other method
 description: Learn how to upgrade from Azure Stack HCI OS, version 22H2 to version 23H2 using other manual methods on Azure Local.
 author: alkohli
 ms.topic: how-to
-ms.date: 03/14/2025
+ms.date: 04/14/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -45,26 +45,34 @@ Before you begin, make sure that:
 
 - You have access to an Azure Local running version 22H2.
 - The system is registered in Azure.
-- Make sure that all the machines in your Azure Local are healthy and show as **Online**.
+- All the machines in your Azure Local are healthy and show as **Online**.
+- You shut down virtual machines (VMs). We recommend shutting down VMs before performing the OS upgrade to prevent unexpected outages and damages to databases.
 - 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).
 - You have access to a client that can connect to your Azure Local. This client should be running PowerShell 5.0 or later.
 
 ## Step 0: Update registry keys
 
-To avoid issues with Resilient File System (ReFS) during OS upgrade, run the following commands on each machine in the system to update registry keys:
+To ensure Resilient File System (ReFS) and live migrations function properly during and after OS upgrade, follow these steps on each machine in the system to update registry keys. Reboot each machine for the changes to take effect.
 
-```powershell
-# Set RefsEnableMetadataValidation to 0
-Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord  -ErrorAction Stop
-```
+1. Set `RefsEnableMetadataValidation` to `0`:
 
-```powershell
-# Create the parameters key if it does not exist. If it does already exist, the command may fail with an error, which is expected.
-New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters
+   ```powershell
+   Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord  -ErrorAction Stop
+   ```
+
+1. Create the parameters key if it doesn't exist. If it already exists, the command may fail with an error, which is expected.
+
+   ```powershell
+   New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters
+   ```
+
+1. Set `SkipSmallLocalAllocations` to `0`:
+
+   ```powershell
+   New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters -Name SkipSmallLocalAllocations -Value 0 -PropertyType DWord
+   ```
 
-# Set the SkipSmallLocalAllocations value to 0
-New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters -Name SkipSmallLocalAllocations -Value 0 -PropertyType DWord
-```
+1. Restart the machine for the changes to take effect. On machine restart, if the `RefsEnableMetadataValidation` key gets overridden and ReFS volumes fail to come online, toggle the key by first setting `RefsEnableMetadataValidation` to `1` and then back to `0` again.
 
 ## Step 1: Connect to your system
 
diff --git a/azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md b/azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md
@@ -3,7 +3,7 @@ title: Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via PowerShell
 description: Learn how to use PowerShell to upgrade Azure Stack HCI OS, version 22H2 to version 23H2.
 author: alkohli
 ms.topic: how-to
-ms.date: 03/14/2025
+ms.date: 04/14/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -44,32 +44,38 @@ Before you begin, make sure that:
 
 - You have access to an Azure Local running version 22H2.
 - The system is registered in Azure.
-- Make sure that all the machines  in your Azure Local, version 22H2 instance are healthy and show as **Online**.
+- All the machines  in your Azure Local, version 22H2 instance are healthy and show as **Online**.
+- You shut down virtual machines (VMs). We recommend shutting down VMs before performing the OS upgrade to prevent unexpected outages and damages to databases.
 - You have access to the Azure Stack HCI, version 23H2 OS software update for Azure Local. 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).
 - You have access to a client that can connect to your Azure Local instance. This client should be running PowerShell 5.0 or later.
 
 > [!NOTE]
 > The ISO file is only required if the machines do not have access to Windows Update to download the OS feature update. If using this method, after you [Connect to Azure Local, version 22H2](#step-1-connect-to-azure-local), skip to step 6 under [Step 2: Install new OS using PowerShell](#step-2-install-new-os-using-powershell) and perform the remaining steps.
 > Use of 3rd party tools to install upgrades is not supported.
 
-Follow these steps to install the solution upgrade:
-
 ## Step 0: Update registry keys
 
-To avoid issues with Resilient File System (ReFS) during OS upgrade, run the following commands on each machine in the system to update registry keys:
+To ensure Resilient File System (ReFS) and live migrations function properly during and after OS upgrade, follow these steps on each machine in the system to update registry keys. Reboot each machine for the changes to take effect.
 
-```powershell
-# Set RefsEnableMetadataValidation to 0
-Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord  -ErrorAction Stop
-```
+1. Set `RefsEnableMetadataValidation` to `0`:
 
-```powershell
-# Create the parameters key if it does not exist. If it does already exist, the command may fail with an error, which is expected.
-New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters
+   ```powershell
+   Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord  -ErrorAction Stop
+   ```
 
-# Set the SkipSmallLocalAllocations value to 0
-New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters -Name SkipSmallLocalAllocations -Value 0 -PropertyType DWord
-```
+1. Create the parameters key if it doesn't exist. If it already exists, the command may fail with an error, which is expected.
+
+   ```powershell
+   New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters
+   ```
+
+1. Set `SkipSmallLocalAllocations` to `0`:
+
+   ```powershell
+   New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters -Name SkipSmallLocalAllocations -Value 0 -PropertyType DWord
+   ```
+
+1. Restart the machine for the changes to take effect. On machine restart, if the `RefsEnableMetadataValidation` key gets overridden and ReFS volumes fail to come online, toggle the key by first setting `RefsEnableMetadataValidation` to `1` and then back to `0` again.
 
 ## Step 1: Connect to Azure Local
 
diff --git a/azure-local/upgrade/upgrade-22h2-to-23h2-windows-admin-center.md b/azure-local/upgrade/upgrade-22h2-to-23h2-windows-admin-center.md
@@ -3,7 +3,7 @@ title: Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via Windows Admi
 description: Learn how to upgrade Azure Stack HCI OS, version 22H2 to version 23H2 using Windows Admin Center.
 author: alkohli
 ms.topic: how-to
-ms.date: 03/14/2025
+ms.date: 04/14/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -43,7 +43,8 @@ Before you begin, make sure that:
 
 - You have access to version 23H2 OS software update.
 - The system is registered in Azure.
-- Make sure that all the machines in your Azure Local are healthy and show as **Online**.
+- All the machines in your Azure Local are healthy and show as **Online**.
+- You shut down virtual machines (VMs). We recommend shutting down VMs before performing the OS upgrade to prevent unexpected outages and damages to databases.
 - 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).
 - You have access to a client that can connect to your Azure Local instance. This client should have Windows Admin Center installed on it. For more information, see [Install Windows Admin Center](/windows-server/manage/windows-admin-center/deploy/install).
 
@@ -52,20 +53,27 @@ Before you begin, make sure that:
 
 ## Step 0: Update registry keys
 
-To avoid issues with Resilient File System (ReFS) during OS upgrade, run the following commands on each machine in the system to update registry keys:
+To ensure Resilient File System (ReFS) and live migrations function properly during and after OS upgrade, follow these steps on each machine in the system to update registry keys. Reboot each machine for the changes to take effect.
 
-```powershell
-# Set RefsEnableMetadataValidation to 0
-Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord  -ErrorAction Stop
-```
+1. Set `RefsEnableMetadataValidation` to `0`:
 
-```powershell
-# Create the parameters key if it does not exist. If it does already exist, the command may fail with an error, which is expected.
-New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters
+   ```powershell
+   Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord  -ErrorAction Stop
+   ```
 
-# Set the SkipSmallLocalAllocations value to 0
-New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters -Name SkipSmallLocalAllocations -Value 0 -PropertyType DWord
-```
+1. Create the parameters key if it doesn't exist. If it already exists, the command may fail with an error, which is expected.
+
+   ```powershell
+   New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters
+   ```
+
+1. Set `SkipSmallLocalAllocations` to `0`:
+
+   ```powershell
+   New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters -Name SkipSmallLocalAllocations -Value 0 -PropertyType DWord
+   ```
+
+1. Restart the machine for the changes to take effect. On machine restart, if the `RefsEnableMetadataValidation` key gets overridden and ReFS volumes fail to come online, toggle the key by first setting `RefsEnableMetadataValidation` to `1` and then back to `0` again.
 
 ## Step 1: Connect to Azure Local via Windows Admin Center
 
