diff --git a/.openpublishing.redirection.azure-local.json b/.openpublishing.redirection.azure-local.json index dc69d76efa..54d6d12c15 100644 --- a/.openpublishing.redirection.azure-local.json +++ b/.openpublishing.redirection.azure-local.json @@ -1510,21 +1510,11 @@ "redirect_url": "/azure/azure-local/upgrade/troubleshoot-upgrade-to-23h2", "redirect_document_id": false }, - { - "source_path": "azure-stack/hci/upgrade/upgrade-22h2-to-23h2-other-methods.md", - "redirect_url": "/azure/azure-local/upgrade/upgrade-22h2-to-23h2-other-methods", - "redirect_document_id": false - }, { "source_path": "azure-stack/hci/upgrade/upgrade-22h2-to-23h2-powershell.md", "redirect_url": "/azure/azure-local/upgrade/upgrade-22h2-to-23h2-powershell", "redirect_document_id": false }, - { - "source_path": "azure-stack/hci/upgrade/upgrade-22h2-to-23h2-windows-admin-center.md", - "redirect_url": "/azure/azure-local/upgrade/upgrade-22h2-to-23h2-windows-admin-center", - "redirect_document_id": false - }, { "source_path": "azure-stack/hci/upgrade/validate-solution-upgrade-readiness.md", "redirect_url": "/azure/azure-local/upgrade/validate-solution-upgrade-readiness", @@ -1959,6 +1949,16 @@ "source_path": "azure-local/upgrade/upgrade-to-24h2-powershell.md", "redirect_url": "/azure/azure-local/upgrade/upgrade-22h2-to-23h2-powershell", "redirect_document_id": false + }, + { + "source_path": "azure-local/upgrade/upgrade-22h2-to-23h2-other-methods.md", + "redirect_url": "/azure/azure-local/upgrade/upgrade-22h2-to-23h2-powershell", + "redirect_document_id": false + }, + { + "source_path": "azure-local/upgrade/upgrade-22h2-to-23h2-windows-admin-center.md", + "redirect_url": "/azure/azure-local/upgrade/upgrade-22h2-to-23h2-powershell", + "redirect_document_id": false } ] } diff --git a/azure-local/upgrade/post-upgrade-steps.md b/azure-local/upgrade/post-upgrade-steps.md index 949bfa5ab5..bd7dbbe69d 100644 --- a/azure-local/upgrade/post-upgrade-steps.md +++ b/azure-local/upgrade/post-upgrade-steps.md @@ -3,7 +3,7 @@ title: Post-upgrade steps on Azure Local via PowerShell description: Learn how to perform the post-upgrade tasks for Azure Local using PowerShell. author: alkohli ms.topic: how-to -ms.date: 09/02/2025 +ms.date: 09/18/2025 ms.author: alkohli ms.reviewer: alkohli ms.service: azure-local @@ -21,12 +21,7 @@ Throughout this article, we refer to OS version 24H2 or 23H2 as the *new* versio Before you begin, make sure that: -- You successfully upgraded the OS to version 23H2 on Azure Local as per the instructions in one of the following docs: - - - [Upgrade to 23H2 OS via PowerShell](./upgrade-22h2-to-23h2-powershell.md). - - [Upgrade to 23H2 OS via Windows Admin Center](./upgrade-22h2-to-23h2-windows-admin-center.md). - - [Upgrade to 23H2 OS via other methods](./upgrade-22h2-to-23h2-other-methods.md). - +- You successfully upgraded the OS to version 23H2 on Azure Local as per the instructions in the [Upgrade to 23H2 OS via PowerShell](./upgrade-22h2-to-23h2-powershell.md) article. - Make sure that all the machines in your system are healthy and show as **Online**. - You have access to a client that can connect to your system. This client should be running PowerShell 5.0 or later. diff --git a/azure-local/upgrade/upgrade-22h2-to-23h2-other-methods.md b/azure-local/upgrade/upgrade-22h2-to-23h2-other-methods.md deleted file mode 100644 index 0017cfea63..0000000000 --- a/azure-local/upgrade/upgrade-22h2-to-23h2-other-methods.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via other methods on Azure Local -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: 09/02/2025 -ms.author: alkohli -ms.reviewer: alkohli -ms.service: azure-local ---- - -# Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via other methods - -[!INCLUDE [applies-to](../includes/hci-applies-to-23h2-22h2.md)] - -[!INCLUDE [end-of-service-22H2](../includes/end-of-service-22h2.md)] - -This article describes how to upgrade the operating system (OS) for Azure Local from version 22H2 to version 23H2 using manual methods, such as [SConfig](/windows-server/administration/server-core/server-core-sconfig) and performing an offline upgrade. This is the first step in the upgrade process, which upgrades only the OS. - -While you can use these other methods, PowerShell is the recommended method to upgrade the OS. For more information, see [Upgrade the Azure Stack HCI OS, version 22H2 to version 23H2 via PowerShell](./upgrade-22h2-to-23h2-powershell.md). - -Throughout this article, we refer to OS version 24H2 or 23H2 as the *new* version, and version 22H2 as the *old* version. - -> [!IMPORTANT] -> To keep your Azure Local service in a supported state, you have up to six months to install this new OS version. The update is applicable to all the Azure Local instances running version 22H2. We strongly recommend that you install this version as soon as it becomes available. - -## High-level workflow for the OS upgrade - -The Azure Stack HCI operating system update is available via the Windows Update and via the media that you can download from the Azure portal. - -To upgrade the OS on your system, follow these high-level steps: - -1. [Complete prerequisites.](#complete-prerequisites) -1. [Update registry keys.](#step-0-update-registry-keys) -1. [Connect to your system.](#step-1-connect-to-your-system) -1. Install new OS using one of the other methods: - 1. [Manual upgrade of a Failover Cluster using SConfig.](#method-1-perform-a-manual-os-update-of-a-failover-cluster-using-sconfig) - 1. [Offline manual upgrade of all machines in a system.](#method-2-perform-a-fast-offline-os-update-of-all-machines-in-a-system) -1. Check the status of the updates. -1. [Perform post-upgrade steps, after the OS is upgraded.](#next-steps) - -## Complete prerequisites - -Before you begin, make sure that: - -- You have access to an Azure Local running version 22H2. -- The system is registered in Azure. -- 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 must be version **2503** ISO 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. -- You run the `RepairRegistration` cmdlet only if both of the following conditions apply: - - - The *identity* property is either missing or doesn’t contain `type = "SystemAssigned"`. - - Check this in the Resource JSON in the Azure portal - - Or run the `Get-AzResource -Name ` PowerShell cmdlet - - The **Cloud Management** cluster group is not present. Check it by running the `Get-ClusterGroup` PowerShell cmdlet. - - If both these conditions are met, run the `RepairRegistration` cmdlet: - - ```powershell - Register-AzStackHCI -TenantId "" -SubscriptionId "" -ComputerName "" -RepairRegistration - ``` - -- (Recommended) You enable [Secure Boot](/windows-hardware/design/device-experiences/oem-secure-boot) on Azure Local machines before you upgrade the OS. - To enable Secure Boot, follow these steps: - 1. Drain the cluster node. - 1. Restart the OS. - 1. Enter the BIOS/UEFI menu. - 1. Review the **Boot** or **Security** section of the UEFI configuration options Locate the Secure Boot option. - 1. Set the option to **Enabled** or **On**. - 1. Save the changes and restart your computer. - - Consult with your hardware vendor for assistance if required. - -## Step 0: 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. - -1. Set `RefsEnableMetadataValidation` to `0`: - - ```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 - ``` - -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. - -1. Update and verify that the registry keys have been applied on each machine in the system before moving to the next step. - -## Step 1: Connect to your system - -Follow these steps on your client to connect to one of the machines on your system. - -> [!IMPORTANT] -> To perform a manual upgrade using SConfig, you must log in directly to the machines. You can use remote PowerShell to control system actions, or you can run the commands directly from each machine when performing the update. - -1. Run PowerShell as Administrator on the client that you're using to connect to your system. -2. Open a remote PowerShell session to a machine on your Azure Local. Run the following command and provide the credentials of your machine when prompted: - - ```powershell - $cred = Get-Credential - Enter-PSSession -ComputerName "" -Credential $cred - ``` - - Here's a sample output: - - ```Console - PS C:\Users\Administrator> $cred = Get-Credential - - cmdlet Get-Credential at command pipeline position 1 - Supply values for the following parameters: - Credential - PS C:\Users\Administrator> Enter-PSSession -ComputerName "100.100.100.10" -Credential $cred - [100.100.100.10]: PS C:\Users\Administrator\Documents> - ``` - -## Step 2: Install new OS using other methods - -Depending upon your requirements, you can manually update the OS using SConfig or update all the machines of the system at the same time. Each of these methods is discussed in the following sections. - - -## Method 1: Perform a manual OS update of a failover cluster using SCONFIG - -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). - -For each machine in the cluster, run these commands on the target node: - -1. `Suspend-ClusterNode -Node -Drain` - - 1. Check suspend using `Get-ClusterGroup`. Nothing should be running on the target node. - - 1. Run the **SCONFIG** option 6.3 on the target node. - - 1. After the target node has rebooted, wait for the storage repair jobs to complete by running `Get-Storage-Job` until there are no storage jobs or all storage jobs are completed. - -1. `Resume-ClusterNode -Node -Failback` - -When all the nodes are upgraded, you can perform the post-installation steps. - -## Method 2: Perform a fast, offline OS update of all machines in a system - -This method allows you to take all the machines in a system down at once and update the OS on all of them at the same time. This saves time during the update process, but the tradeoff is downtime for the hosted resources. - -If there's a critical security update that you need to apply quickly or you need to ensure that updates complete within your maintenance window, this method could be for you. This process brings down the Azure Local, updates the machines, and brings it all up again. - -1. Plan your maintenance window. -1. Take the virtual disks offline. -1. Stop the system to take the storage pool offline. Run the `Stop-Cluster` cmdlet or use Windows Admin Center to stop the system. -1. Set the cluster service to **Disabled** by running the PowerShell command below on each machine. This prevents the cluster service from starting up while being updated. - - ``` - Set-Service -Name clussvc -StartupType Disabled - ``` - -1. Apply the Windows Server Cumulative Update and any required Servicing Stack Updates to all machines. You can update all machines at the same time: there's no need to wait because the system is down. -1. Restart the machines and ensure everything looks good. -1. Set the cluster service back to **Automatic** by running the PowerShell command below on each machine. - - ``` - Set-Service -Name clussvc -StartupType Automatic - ``` - -1. Start the system. Run the `Start-Cluster` cmdlet or use Windows Admin Center. -1. Give it a few minutes. Make sure the storage pool is healthy. Run `Get-StorageJob` to ensure all jobs complete successfully. -1. Bring the virtual disks back online. -1. Monitor the status of the virtual disks by running the `Get-Volume` and `Get-VirtualDisk` cmdlets. - - - -## Step 3: Check the status of an update - -[!INCLUDE [verify-update](../includes/azure-local-verify-update.md)] - -## Next steps - -- [Learn how to perform the post-upgrade steps for your Azure Local.](./post-upgrade-steps.md) diff --git a/azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md b/azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md index 97d61d7644..6953f726c6 100644 --- 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: 09/03/2025 +ms.date: 09/18/2025 ms.author: alkohli ms.reviewer: alkohli ms.service: azure-local @@ -16,11 +16,6 @@ zone_pivot_groups: upgrade-os This article describes how to upgrade the Azure Stack HCI operating system (OS) from version 20349.xxxx (22H2) to version 25398.xxxx (23H2), via PowerShell. This is the first step in the upgrade process, which upgrades only the OS. - - - - ::: zone-end ::: zone pivot="os-24h2" 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 deleted file mode 100644 index f582b5358c..0000000000 --- a/azure-local/upgrade/upgrade-22h2-to-23h2-windows-admin-center.md +++ /dev/null @@ -1,176 +0,0 @@ ---- -title: Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via Windows Admin Center -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: 06/06/2025 -ms.author: alkohli -ms.reviewer: alkohli -ms.service: azure-local ---- - -# Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via Windows Admin Center - -[!INCLUDE [applies-to](../includes/hci-applies-to-23h2-22h2.md)] - -[!INCLUDE [end-of-service-22H2](../includes/end-of-service-22h2.md)] - -This article describes how to upgrade the operating system (OS) for Azure Local from version 22H2 to version 23H2 via the Windows Admin Center. This is the first step in the upgrade process, which upgrades only the OS. - -While the recommended method is to [Upgrade Azure Stack HCI OS, version 22H2 to version 23H2 via PowerShell](./upgrade-22h2-to-23h2-powershell.md), you can also upgrade via Windows Admin Center or other methods. - -Throughout this article, we refer to OS version 23H2 as the *new* version and version 22H2 as the *old* version. - -> [!IMPORTANT] -> To keep your Azure Local service in a supported state, you have up to six months to install this new OS version. The update applies to all Azure Local running version 22H2. We strongly recommend that you install this version as soon as it becomes available. - -## High-level workflow for the OS upgrade - -The Azure Stack HCI operating system update is available via Windows Update and via the media that you can download from the Azure portal. - -To upgrade the OS on your Azure Local, follow these high-level steps: - -1. [Complete the prerequisites](#complete-prerequisites). -1. [Update registry keys.](#step-0-update-registry-keys) -1. [Connect to the Azure Local, version 22H2](#step-1-connect-to-azure-local-via-windows-admin-center). -1. [Check for the available updates using Windows Admin Center.](#step-2-install-operating-system-and-hardware-updates-using-windows-admin-center) -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) -1. [Perform post-OS upgrade steps.](#next-steps) - -## Complete prerequisites - -Before you begin, make sure that: - -- You have access to version 23H2 OS software update. -- The system is registered in Azure. -- 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 must be version **2503** ISO 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). -- You run the `RepairRegistration` cmdlet only if both of the following conditions apply: - - - The *identity* property is either missing or doesn’t contain `type = "SystemAssigned"`. - - Check this in the Resource JSON in the Azure portal - - Or run the `Get-AzResource -Name ` PowerShell cmdlet - - The **Cloud Management** cluster group is not present. Check it by running the `Get-ClusterGroup` PowerShell cmdlet. - - If both these conditions are met, run the `RepairRegistration` cmdlet: - - ```powershell - Register-AzStackHCI -TenantId "" -SubscriptionId "" -ComputerName "" -RepairRegistration - ``` - -- (Recommended) You enable [Secure Boot](/windows-hardware/design/device-experiences/oem-secure-boot) on Azure Local machines before you upgrade the OS. - To enable Secure Boot, follow these steps: - 1. Drain the cluster node. - 1. Restart the OS. - 1. Enter the BIOS/UEFI menu. - 1. Review the **Boot** or **Security** section of the UEFI configuration options Locate the Secure Boot option. - 1. Set the option to **Enabled** or **On**. - 1. Save the changes and restart your computer. - - Consult with your hardware vendor for assistance if required. - -> [!NOTE] -> The offline **2503** 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) - -## Step 0: 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. - -1. Set `RefsEnableMetadataValidation` to `0`: - - ```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 - ``` - -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. - -1. Update and verify that the registry keys have been applied on each machine in the system before moving to the next step. - -## Step 1: Connect to Azure Local via Windows Admin Center - -Follow these steps to add and connect to an Azure Local machine via Windows Admin Center. - -1. Select **+ Add** under **All Connections**. -1. Scroll down to **Server clusters** and select **Add**. -1. Type the name of the system and, if prompted, the credentials to use. -1. Select **Add** to finish. -1. The system and machines are added to your connection list on the **Overview** page. Select the system to connect to it. - -## Step 2: Install operating system and hardware updates using Windows Admin Center - -Windows Admin Center makes it easy to update Azure Local and apply quality updates using a simple user interface. If you purchased an integrated system from a Microsoft hardware partner, it's easy to get the latest drivers, firmware, and other updates directly from Windows Admin Center by installing the appropriate partner update extensions. ​If your hardware wasn't purchased as an integrated system, firmware and driver updates would need to be performed separately, following the hardware vendor's recommendations. - - > [!WARNING] - > If you begin the update process using Windows Admin Center, continue using the wizard until updates complete. Don't attempt to use the Cluster-Aware Updating (CAU) tool or update a system with PowerShell after partially completing the update process in Windows Admin Center. If you wish to use PowerShell to perform the updates instead of Windows Admin Center, see [Upgrade via PowerShell](./upgrade-22h2-to-23h2-powershell.md). - -Follow these steps to install updates: - -> [!NOTE] -> The following steps use Windows Admin Center version 2311. If you are using a different version, your screens may vary slightly. - -1. When you connect to a system, the Windows Admin Center dashboard alerts you if one or more machines have updates ready to be installed and provide a link to update now. Alternatively, select **Updates** from the **Operations** menu at the left. - -1. If you're updating your system for the first time, Windows Admin Center checks if the system is properly configured to run CAU. If not, it prompts you to allow Windows Admin Center to configure CAU, which includes installing the CAU cluster role and enabling the required firewall rules. To begin the update process, select **Add Cluster-Aware-Updating role**. - - :::image type="content" source="media/upgrade-22h2-to-23h2-windows-admin-center/add-cau-role.png" alt-text="Screenshot of Windows Admin Center automatically configuring the system to run Cluster-Aware Updating." lightbox="media/upgrade-22h2-to-23h2-windows-admin-center/add-cau-role.png"::: - - > [!NOTE] - > To use the CAU tool in Windows Admin Center, you must enable Credential Security Service Provider (CredSSP) and provide explicit credentials. If you are asked if CredSSP should be enabled, select **Yes**. Specify your username and password, and select **Continue**. - -1. After the role is installed, Windows Admin Center automatically checks for updates applicable to your system. Ensure the radio button for **Feature update (Recommended)** is selected and the **Feature update for Azure Local, version 23H2** is **Available** for the machines. If the feature update isn't displayed, ensure your system is running the Azure Stack HCI OS and that the machines have direct access to Windows Update, then select **Check for updates**. - - :::image type="content" source="media/upgrade-22h2-to-23h2-windows-admin-center/check-for-updates.png" alt-text="Screenshot of the Updates page in Windows Admin Center showing the available updates." lightbox="media/upgrade-22h2-to-23h2-windows-admin-center/check-for-updates.png"::: - - > [!IMPORTANT] - > Feature updates aren't available in Windows Server Update Services (WSUS). - - If you navigate away from the Updates screen while an update is in progress, there could be unexpected behavior, such as the history section of the Updates page not populating correctly until the current run is finished. We recommend opening Windows Admin Center in a new browser tab or window if you wish to continue using the application while the updates are in progress. - -1. Select **Install**. Windows Admin Center automatically performs a series of readiness checks to identify issues that could prevent CAU from completing successfully. If any issues are found, select the **Details** link next to the issue, address the issue, and then select **Check again** to run the readiness checks again. - - :::image type="content" source="media/upgrade-22h2-to-23h2-windows-admin-center/readiness-checks.png" alt-text="Screenshot of the readiness check during the installation of updates." lightbox="media/upgrade-22h2-to-23h2-windows-admin-center/readiness-checks.png"::: - - > [!NOTE] - > If you're installing updates on a system that has [Kernel Soft Reboot](../manage/kernel-soft-reboot.md) enabled, select **Disable Kernel Soft Reboot for this run** checkbox. This selection disables Kernel Soft Reboot as the upgrade requires a full reboot. - -1. Select **Next: Install** to review the list of updates to be installed to each machine. Then, select **Install** to begin installing the operating system updates. One by one, each machine downloads and applies the updates. The update status changes to **Installing updates**. If the updates require a restart, machines are restarted one at a time, moving roles such as VMs between machines to prevent downtime. Depending on the updates being installed, the entire update run can take anywhere from a few minutes to several hours. You would need to sign in to Windows Admin Center multiple times. - - :::image type="content" source="media/upgrade-22h2-to-23h2-windows-admin-center/final-confirmation.png" alt-text="Screenshot of selecting Install to install operating system updates on each machine in the system." lightbox="media/upgrade-22h2-to-23h2-windows-admin-center/final-confirmation.png"::: - - > [!NOTE] - > If the updates fail with a **Couldn't install updates** or **Couldn't check for updates** warning or if one or more machines indicate **couldn't get status** during the run, wait a few minutes, and refresh your browser. You can also use `Get-CauRun` to [check the status of the update run with PowerShell](./upgrade-22h2-to-23h2-powershell.md#check-the-status-of-an-update). - -1. When operating system updates are complete, the update status changes to **Succeeded**. Select **Next: Hardware updates** to proceed to the hardware updates screen. - - > [!IMPORTANT] - > After applying operating system updates, you may see a message that "storage isn't complete or up-to-date, so we need to sync it with data from other servers in the cluster." This is normal after a machine restarts. **Don't remove any drives or restart any machines in the system until you see a confirmation that the sync is complete.** - - > [!NOTE] - > Hardware updates are only available on systems that have the vendor's hardware extension installed. If your Windows Admin Center does not have this extension, there will not be an option to install hardware updates. - -1. Windows Admin Center checks the system for installed extensions that support your specific machine hardware. Select **Next: Install** to install the hardware updates on each machine in the system. If no extensions or updates are found, select **Exit**. - -1. As per security best practices, disable CredSSP as soon as you're finished installing the updates: - - In Windows Admin Center, under **All connections**, select the first machine in your system and then select **Connect**. - - On the **Overview** page, select **Disable CredSSP**, and then, on the **Disable CredSSP** pop-up window, select **Yes**. - -You're now ready to perform the post-upgrade steps for your system. - - -## Next steps - -- [Learn how to perform the post-upgrade steps for your Azure Local.](./post-upgrade-steps.md)