Merge pull request #8872 from MicrosoftDocs/main

Deland-Han · web-flow · commit 916ec404296e · 2025-05-07T10:32:07.000+08:00
Auto push to live 2025-05-07 02:31:59
diff --git a/support/azure/azure-kubernetes/create-upgrade-delete/nodepools-not-upgraded-to-gen2-during-node-image-upgrade.md b/support/azure/azure-kubernetes/create-upgrade-delete/nodepools-not-upgraded-to-gen2-during-node-image-upgrade.md
@@ -1,63 +1,65 @@
 ---
-title: Windows nodepools not upgraded to Gen2 during cluster node image upgrade
-description: Troubleshoot why Windows Server nodepools don't get upgraded automatically from Gen1 to Gen2 when a cluster node image is upgraded in Azure Kubernetes Service.
-ms.date: 11/20/2024
+title: Windows Node Pools Not Upgraded to Gen2 During Cluster Node Image Upgrade
+description: Troubleshoot an issue that prevents Windows Server node pools from upgrading automatically to Gen2 when a cluster node image is upgraded in Azure Kubernetes Service.
+ms.date: 04/17/2025
 editor: v-jsitser
-ms.reviewer: chiragpa, cssakscic, v-leedennis
+ms.reviewer: chiragpa, cssakscic, momajed
 ms.service: azure-kubernetes-service
-#Customer intent: As an Azure Kubernetes Services (AKS) user, I want to troubleshoot why Windows Server nodepools don't get upgraded automatically from Gen1 to Gen2 virtual machines (VMs) when a cluster node image is upgraded in Azure Kubernetes Service (AKS).
-ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
+#Customer intent: As an Azure Kubernetes Services (AKS) user, I want to troubleshoot why Windows Server node pools don't get upgraded automatically from Gen1 to Gen2 virtual machines (VMs) when a cluster node image is upgraded in Azure Kubernetes Service (AKS).
+ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or node pool)
 ---
-# Windows Server nodepools not upgraded to Gen2 during cluster node image upgrade
 
-This article discusses how to troubleshoot a scenario in which Windows Server nodepools don't get upgraded automatically from Gen1 to Gen2 virtual machines (VMs) when a cluster node image is upgraded in Microsoft Azure Kubernetes Service (AKS).
+# Windows Server node pools not upgraded to Gen2 during cluster node image upgrade
+
+This article discusses how to troubleshoot a scenario in which Windows Server node pools don't get upgraded automatically from Gen1 to Gen2 virtual machines (VMs) when a cluster node image is upgraded in Microsoft Azure Kubernetes Service (AKS).
 
 > [!NOTE]  
-> This scenario doesn't apply to Gen2 VMs on Linux nodepools.
+> This scenario doesn't apply to Gen2 VMs on Linux node pools.
 
 ## Prerequisites
 
-- [Azure CLI](/cli/azure/install-azure-cli)
+- Azure CLI version 2.0.81 or later. See [Install Azure CLI](/cli/azure/install-azure-cli) for installation instructions.
 
 ## Symptoms
 
-Existing Windows Server nodepools don't get upgraded from Gen1 to Gen2 when you [upgrade the node image](/azure/aks/node-image-upgrade) by using one of the following methods in Azure CLI:
+Existing Windows Server node pools don't get upgraded from Gen1 to Gen2 when you [upgrade the node image](/azure/aks/node-image-upgrade) by using one of the following methods in Azure CLI:
 
-- An entire cluster upgrade (by using the [az aks upgrade](/cli/azure/aks#az-aks-upgrade) command)
+- An entire cluster upgrade (by using the [`az aks upgrade`](/cli/azure/aks#az-aks-upgrade) command)
 
-- A specific nodepool upgrade (by using the [az aks nodepool upgrade](/cli/azure/aks/nodepool#az-aks-nodepool-upgrade) command)
+- A specific node pool upgrade (by using the [`az aks nodepool upgrade`](/cli/azure/aks/nodepool#az-aks-nodepool-upgrade) command)
 
 ## Cause
 
-### Cause 1: Existing nodepools aren't automatically upgraded to Gen2 VMs
+### Cause 1: Existing node pools aren't automatically upgraded to Gen2 VMs
 
-By design, a node image upgrade doesn't support updating or upgrading existing nodepools. The `az aks upgrade` and `az aks nodepool upgrade` commands upgrade only the node image (to a later node image version). Those commands don't upgrade the corresponding VM generation.
+By design, a node image upgrade doesn't support updating or upgrading existing node pools. The `az aks upgrade` and `az aks nodepool upgrade` commands upgrade only the node image (to a later node image version). These commands don't upgrade the corresponding VM generation.
 
 ### Cause 2: Cluster upgrade to Kubernetes version 1.25 or a later version upgrades only the OS
 
-When you upgrade your cluster to Kubernetes version 1.25 or a later version, only the operating system (OS) is upgraded (to Windows Server 2022). Existing nodepools aren't affected. The associated VM scale set will contain VMs that have the same Gen1 VM.
+When you upgrade your cluster to Kubernetes version 1.25 or a later version, only the operating system (OS) is upgraded (to Windows Server 2022). Existing node pools aren't affected. The associated Azure Virtual Machine Scale Sets contain VMs that have the same Gen1 VM.
 
-### Cause 3: Cluster upgraded and new nodepool created by using Windows Server 2022 without specifying a valid VM size
+### Cause 3: Cluster upgraded and new node pool created by using Windows Server 2022 without specifying a valid VM size
 
-After you upgrade the cluster to Kubernetes version 1.25 or a later version, you specify Windows Server 2022 as the OS to use on the nodepool's VMs. However, the VMs don't use a Gen2 node image reference because of one of the following reasons:
+After you upgrade the cluster to Kubernetes version 1.25 or a later version, you specify Windows Server 2022 as the OS to use on the node pool's VMs. However, the VMs don't use a Gen2 node image reference for one of the following reasons:
 
 - You don't specify a VM size, and the default VM size in the region doesn't support Gen2 VMs.
 
 - You specify a Gen1-only VM size.
 
-When you upgrade the default OS from Windows Server 2019 (`Windows2019`) to Windows Server 2022 (`Windows2022`), the existing nodepools aren't automatically upgraded to a different VM generation.
+When you upgrade the default OS from Windows Server 2019 (`Windows2019`) to Windows Server 2022 (`Windows2022`), the existing node pools aren't automatically upgraded to a different VM generation.
 
 ## Solution
 
-Upgrade the cluster, and then create a new Windows Server nodepool that supports [Gen2 VM sizes](/azure/virtual-machines/generation-2) on that cluster according to the following guidelines.
+Upgrade the cluster, and then create a new Windows Server node pool that supports [Gen2 VM sizes](/azure/virtual-machines/generation-2) on that cluster according to the following guidelines.
 
 | Kubernetes cluster upgrade version | Cluster creation guidelines |
 |---|---|
-| 1.25 or a later version | When you run the [az aks create](/cli/azure/aks#az-aks-create) command to create a cluster, set the `--node-vm-size` parameter to a [Gen2 VM size](/azure/virtual-machines/generation-2). |
-| Earlier version than 1.25 | When you run the [az aks create](/cli/azure/aks#az-aks-create) command to create a cluster, set the `--os-sku` parameter value to `Windows2022`, and set the `--node-vm-size` parameter value to a [Gen2 VM size](/azure/virtual-machines/generation-2). |
+| 1.25 or a later version | When you run the [`az aks create`](/cli/azure/aks#az-aks-create) command to create a cluster, set the `--node-vm-size` parameter to a [Gen2 VM size](/azure/virtual-machines/generation-2). |
+| Any version earlier than 1.25 | When you run the [`az aks create`](/cli/azure/aks#az-aks-create) command to create a cluster, set the `--os-sku` parameter value to `Windows2022`, and set the `--node-vm-size` parameter value to a [Gen2 VM size](/azure/virtual-machines/generation-2). |
+
 
 > [!NOTE]  
-> If you specify a Gen2 VM size and the operating system as Windows Server 2019, you receive an `ErrorCode_Windows2019NotSupportedWithGen2VM` error code that's accompanied by the following error message:
+> If you specify a Gen2 VM size and set the operating system as Windows Server 2019, you receive an `ErrorCode_Windows2019NotSupportedWithGen2VM` error code that's accompanied by the following error message:
 >
 > > \<virtual-machine-size> is a Gen 2-only VM. Windows2019 does not support Gen 2 VMs. However, you can select a Gen 1 VM size or set os_sku to 2022.
 >
@@ -66,5 +68,11 @@ Upgrade the cluster, and then create a new Windows Server nodepool that supports
 > - Pick a Gen1 VM size to use together with Windows Server 2019.
 >
 > - Set the operating system SKU to **Windows Server 2022** to use together with your Gen2 VM.
+>
+> - Before you create a new node pool, verify that the VM size supports Gen2 VMs in your region. To do this, run `az vm list-sizes --location <region> --query "[?contains(name, 'v2')].name" --output table`.
+>
+> - To verify the current and available node image versions, run the following commands:
+>    - To check the current version: `az aks nodepool show --resource-group <resource-group> --cluster-name <cluster-name> --name <nodepool-name> --query nodeImageVersion`
+>    - To check the latest available version: `az aks nodepool get-upgrades --resource-group <resource-group> --cluster-name <cluster-name> --nodepool-name <nodepool-name> --query latestNodeImageVersion`
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
diff --git a/support/windows-client/networking/mapped-network-drive-fail-reconnect.md b/support/windows-client/networking/mapped-network-drive-fail-reconnect.md
@@ -1,7 +1,7 @@
 ---
 title: Mapped network drive may fail to reconnect in Windows 10, version 1809
 description: An article provides a workaround to resolve mapped network drives not working in Windows 10, version 1809.
-ms.date: 01/15/2025
+ms.date: 05/07/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -51,9 +51,9 @@ while($True){
     foreach( $MappedDrive in $MappedDrives)
     {
         try {
-            New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True
+            New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True -ErrorAction Stop
         } catch {
-            Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"
+            Write-Host "There was an error mapping $($MappedDrive.RemotePath) to $($MappedDrive.LocalPath)"
         }
     }
     $i = $i - 1
@@ -72,28 +72,45 @@ All workarounds should be executed in standard user security context. Executing
 > [!NOTE]
 > This workaround works only for the device that has network access at logon. If the device has not established a network connection by the time of logon, the startup script won't automatically reconnect network drives.
 
-1. Copy the script file (MapDrives.cmd) to the following location:  
-    %ProgramData%\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp  
-2. Copy the script file (MapDrives.ps1) to the following location:  
-    %SystemDrive%\\Scripts\\
-3. A log file (StartupLog.txt) will be created in the %TEMP%\\ folder.
-4. Log off, and then log back on to the device to open the mapped drives.
+1. Copy the script file **MapDrives.cmd** to the following location:  
+    **%ProgramData%\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp**
+2. Copy the script file **MapDrives.ps1** to the following location: **%SystemDrive%\\Scripts\\**.
+3. A log file **StartupLog.txt** is created in the **%TEMP%\\** folder.
+4. Sign out, and then sign in to the device to open the mapped drives.
 
 #### Workaround 2: Create a scheduled task
 
 > [!NOTE]
 > A PowerShell window flashes up when the scheduled task runs.
 
-1. Copy the script file MapDrives.ps1 to the following location:  
-    %SystemDrive%\\Scripts\\  
+1. Copy the script file **MapDrives.ps1** to the following location: **%SystemDrive%\\Scripts\\**.
 2. In **Task Scheduler**, select **Action** > **Create Task**.
-3. On the **General** tab in the **Create Task** dialog box, type a name (such as *Map Network Drives*) and description for the task.
+3. On the **General** tab in the **Create Task** dialog, type a name (such as **Map Network Drives**) and description for the task.
 4. Select **Change User or Group**, select a local user or group (such as **LocalComputer\\Users**) and then select **OK**.
 5. On the **Triggers** tab, select **New**, and then select **At log on** for the **Begin the task** field.
 6. On the **Actions** tab, select **New**, and then select **Start a program** for the **Action** field.
-7. Type _Powershell.exe_ for the **Program/script** field.
+7. Type **Powershell.exe** for the **Program/script** field.
 8. In the **Add arguments (optional)** field, type the following:  
-    _-windowstyle hidden -command .\\MapDrives.ps1 >> %TEMP%\\StartupLog.txt 2>&1_
-9. In the **Start in (optional)** field, type the location (_%SystemDrive%\\Scripts\\_) of the script file.
+   **-windowstyle hidden -command .\\MapDrives.ps1 >> %TEMP%\\StartupLog.txt 2>&1**
+9. In the **Start in (optional)** field, type the location of the script file: **%SystemDrive%\\Scripts\\**.
 10. On the **Conditions** tab, select the **Start only if the following network connection is available** option, select **Any connection**, and then select **OK**.
-11. Log off, and then log back on to the device to run the scheduled task.
+11. Sign out, and then sign in to the device to run the scheduled task.
+
+#### Workaround 3: Create a scheduled task for VPN connection Event ID 20225
+
+> [!NOTE]
+> Event ID 20225 indicates that a virtual private network (VPN) connection is successfully established.
+
+1. Copy the script file **MapDrives.ps1** to the following location: **%SystemDrive%\\Scripts\\**.
+2. In **Task Scheduler**, select **Action** > **Create Task**.
+3. On the **General** tab in the **Create Task** dialog, type a name (such as **Map Network Drives**) and description for the task.
+4. Select **Change User or Group**, select a local user or group (such as **LocalComputer\\Users**) and then select **OK**.
+5. On the **Triggers** tab, select **New**, and then select **On an event** for the **Begin the task** field.
+6. Select **Application** from the **Log** dropdown list, type **RasClient** in the **Source** field, and type **20225** in the **Event ID** field. Then, select **OK**.
+7. On the **Actions** tab, select **New**, and then select **Start a program** for the **Action** field.
+8. Type **Powershell.exe** for the **Program/script** field.
+9. In the **Add arguments (optional)** field, type the following:  
+   **-windowsstyle hidden -command .\\MapDrives.ps1 >> %TEMP%\\StartupLog.txt 2>&1**
+10. In the **Start in (optional)** field, type the location of the script file: **%SystemDrive%\\Scripts\\**.
+11. On the **Conditions** tab, select the **Start only if the following network connection is available** option, select **Any connection**, and then select **OK**.
+12. Sign out, and then sign in to the device to run the scheduled task.
