Merge pull request #18297 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-stack-docs (branch main)

Author: sethmanheim

azure-local/manage/add-server.md

@@ -4,7 +4,7 @@ description: Learn how to manage capacity on your Azure Local, version 23H2 syst
 ms.topic: how-to
 author: alkohli
 ms.author: alkohli
-ms.date: 05/28/2025
+ms.date: 06/25/2025
 ---
 
 # Add a node on Azure Local
@@ -124,12 +124,6 @@ On a node that already exists on your system, follow these steps:
     Update-AuthenticationToken 
     ```
 
-1. If you are running a version prior to 2405.3, you must run the following command on the new node to clean up conflicting files:
-
-    ```powershell
-    Get-ChildItem -Path "$env:SystemDrive\NugetStore" -Exclude Microsoft.AzureStack.Solution.LCMControllerWinService*,Microsoft.AzureStack.Role.Deployment.Service* | Remove-Item -Recurse -Force
-    ```
-
 1. Run the following command to add the new incoming node using a local administrator credential for the new node:
 
     ```powershell

azure-local/manage/repair-server.md

@@ -4,7 +4,7 @@ description: Learn how to repair a node on your Azure Local, version 23H2 system
 ms.topic: how-to
 author: alkohli
 ms.author: alkohli
-ms.date: 05/08/2025
+ms.date: 06/25/2025
 ---
 
 # Repair a node on Azure Local
@@ -140,13 +140,6 @@ Follow these steps on the node you're trying to repair.
 
 Follow these steps on another node that is a member of the same Azure Local instance.
 
-
-1. If you are running a version prior to 2405.3, you must run the following command to clean up conflicting files:
-
-    ```powershell
-    Get-ChildItem -Path "$env:SystemDrive\NugetStore" -Exclude Microsoft.AzureStack.Solution.LCMControllerWinService*,Microsoft.AzureStack.Role.Deployment.Service* | Remove-Item -Recurse -Force
-    ```
-
 1. Sign into the node that is already a member of the system, with the domain user credentials that you provided during the deployment of the system. Run the following command to repair the incoming node:
 
     ```powershell