From 30c5d0f9d5fa8ee5e3de2a87fa3704982f619df8 Mon Sep 17 00:00:00 2001
From: Kartikay Sharma <44971599+SharmaKartikay@users.noreply.github.com>
Date: Thu, 24 Apr 2025 13:15:44 +0100
Subject: [PATCH 1/2] Update troubleshoot-arc-enabled-vms.md

Known issue documented internally and must be published here for customers: https://internal.evergreen.microsoft.com/en-us/topic/8ac50cf1-8e25-005b-9a01-4b0a8a791ab7
---
 .../manage/troubleshoot-arc-enabled-vms.md    | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/azure-local/manage/troubleshoot-arc-enabled-vms.md b/azure-local/manage/troubleshoot-arc-enabled-vms.md
index 530db09b10..5fa1461431 100644
--- a/azure-local/manage/troubleshoot-arc-enabled-vms.md
+++ b/azure-local/manage/troubleshoot-arc-enabled-vms.md
@@ -128,6 +128,35 @@ If your environment fails to recognize Azure CLI after installing it, run the fo
         }
 ```
 
+## Live Migrations on Azure Local 23H2 May Fail Without Error
+
+After upgrading from Azure Local 22H2 to 23H2, or on a clean install of 23H2, you may encounter issues where VMs fail to live migrate in an Azure Local Cluster.  
+
+**Issue:** Live migration attempts may fail silently — no error messages are logged.
+
+This problem is caused by a known issue in Azure Local 23H2 that manifests under specific system configurations.
+
+**Resolution:**  
+
+Run the following PowerShell script locally on one of the cluster nodes. This script will apply a registry fix on all nodes. After running it, reboot each node one at a time for the change to take effect.
+
+```PowerShell
+Get-ClusterNode | ForEach-Object {
+    Invoke-Command -ComputerName $_.Name -ScriptBlock {
+        $RegPath = "HKLM:\System\CurrentControlSet\Services\Vid\Parameters"
+        $ValueName = "SkipSmallLocalAllocations"
+        $ValueData = 0
+
+        # Create the key if it doesn't exist
+        if (-Not (Test-Path $RegPath)) {
+            New-Item -Path $RegPath -Force | Out-Null
+        }
+
+        # Create or update the DWORD value
+        New-ItemProperty -Path $RegPath -Name $ValueName -Value $ValueData -PropertyType DWord -Force
+    }
+}
+```
 
 ## Next steps
 

From e8aba465a9c9a0b001a2dc775b596b4f4a1b84bb Mon Sep 17 00:00:00 2001
From: Diana Richards <v-dirichards@microsoft.com>
Date: Wed, 25 Jun 2025 09:10:56 -0500
Subject: [PATCH 2/2] Apply suggestions from author's review

---
 azure-local/manage/troubleshoot-arc-enabled-vms.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/azure-local/manage/troubleshoot-arc-enabled-vms.md b/azure-local/manage/troubleshoot-arc-enabled-vms.md
index 5fa1461431..bb318d735d 100644
--- a/azure-local/manage/troubleshoot-arc-enabled-vms.md
+++ b/azure-local/manage/troubleshoot-arc-enabled-vms.md
@@ -128,17 +128,19 @@ If your environment fails to recognize Azure CLI after installing it, run the fo
         }
 ```
 
-## Live Migrations on Azure Local 23H2 May Fail Without Error
+## Live migrations on Azure Local 2311.2 and later could fail without error
 
-After upgrading from Azure Local 22H2 to 23H2, or on a clean install of 23H2, you may encounter issues where VMs fail to live migrate in an Azure Local Cluster.  
+After you upgrade to Azure Local 2311.2 or on a new deployment of 2311.2 or later, you could see issues where the Azure Local VMs fail to live migrate in an Azure Local instance.
 
 **Issue:** Live migration attempts may fail silently — no error messages are logged.
 
-This problem is caused by a known issue in Azure Local 23H2 that manifests under specific system configurations.
+Cause: This problem is caused by a known issue in Azure Local, version 2311.2 or later. This problem manifests under specific system configurations.
 
 **Resolution:**  
 
-Run the following PowerShell script locally on one of the cluster nodes. This script will apply a registry fix on all nodes. After running it, reboot each node one at a time for the change to take effect.
+Run the following PowerShell script locally on one of the Azure Local machines. This script applies a registry fix on all the machines of your Azure Local instance.
+
+After you have run the script, reboot each machine one at a time for the change to take effect.
 
 ```PowerShell
 Get-ClusterNode | ForEach-Object {