Skip to content

Commit 997663a

Browse files
authored
Merge pull request #18184 from MicrosoftDocs/main
6/12/2025 AM Publish
2 parents fd32b64 + a11a48e commit 997663a

File tree

2 files changed

+4
-10
lines changed

2 files changed

+4
-10
lines changed

azure-local/upgrade/install-solution-upgrade.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Install solution upgrade on Azure Local
33
description: Learn how to install the solution upgrade on your Azure Local instance.
44
author: alkohli
55
ms.topic: how-to
6-
ms.date: 06/10/2025
6+
ms.date: 06/11/2025
77
ms.author: alkohli
88
ms.reviewer: alkohli
99
ms.service: azure-local
@@ -27,12 +27,12 @@ Throughout this article, we refer to OS version 23H2 as the *new* version and ve
2727

2828
Before you install the solution upgrade, make sure that you:
2929

30-
- Validate the system using the Environment Checker as per the instructions in [Assess solution upgrade readiness](./validate-solution-upgrade-readiness.md#run-the-validation).
30+
- Validate the system using the Environment Checker as per the instructions in [Assess solution upgrade readiness](./validate-solution-upgrade-readiness.md#run-the-validation).
3131
- Verify that latest `AzureEdgeLifecycleManager` extension on each machine is installed as per the instructions in [Check the Azure Arc extension](./validate-solution-upgrade-readiness.md#remediation-9-check-the-azure-arc-lifecycle-extension).
3232

3333
:::image type="content" source="media/install-solution-upgrade/verify-lcmextension-installed.png" alt-text="Screenshot of Extensions page showing AzureEdgeLifeCycleManager extension install on an Azure Local machine." lightbox="./media/install-solution-upgrade/verify-lcmextension-installed.png":::
3434
- Have failover cluster name between 3 to 15 characters.
35-
- Have an Active Directory user credential that's a member of the local Administrator group. Work with your Active Directory administrator to obtain this credential.
35+
- Create an Active Directory Lifecycle Manager (LCM) user account that's a member of the local Administrator group. For instructions, see [Prepare Active Directory for Azure Local deployment](../deploy/deployment-prep-active-directory.md).
3636
- Have IPv4 network range that matches your host IP address subnet with six, contiguous IP addresses available for new Azure Arc services. Work with your network administrator to ensure that the IP addresses aren't in use and meet the outbound connectivity requirement.
3737
- Have Azure subscription permissions for [Azure Stack HCI Administrator and Reader](../manage/assign-vm-rbac-roles.md#about-built-in-rbac-roles).
3838

azure-local/upgrade/upgrade-to-24h2-powershell.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Upgrade Azure Stack HCI OS to version 26100.xxxx using PowerShell
33
description: Learn how to use PowerShell to upgrade Azure Stack HCI OS to version 26100.xxxx.
44
author: alkohli
55
ms.topic: how-to
6-
ms.date: 06/10/2025
6+
ms.date: 06/11/2025
77
ms.author: alkohli
88
ms.reviewer: alkohli
99
ms.service: azure-local
@@ -79,12 +79,6 @@ To ensure Resilient File System (ReFS) functions properly during and after OS up
7979
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "RefsEnableMetadataValidation" -Value 0 -Type DWord -ErrorAction Stop
8080
```
8181

82-
1. Create the parameters key if it doesn't exist. If it already exists, the command may fail with an error, which is expected.
83-
84-
```powershell
85-
New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\Vid\Parameters
86-
```
87-
8882
1. Restart the machine to apply changes. If ReFS volumes fail to come online after reboot and the `RefsEnableMetadataValidation` key is reset, toggle the key. Set `RefsEnableMetadataValidation` to **1** and then back to **0**. To check volume status, run the `Get-ClusterSharedVolumeState` command.
8983

9084
1. Update and verify that the registry keys have been applied on each machine in the system before moving to the next step.

0 commit comments

Comments
 (0)