Updated with final changes from sync with Alpa

Author: LouisBerner

articles/databox-online/TOC.yml

@@ -517,7 +517,9 @@
         href: azure-stack-edge-contact-microsoft-support.md 
   - name: Shared release notes
     items:
-    - name: 2210 - Current
+    - name: 2301 - Current
+      href: azure-stack-edge-gpu-2301-release-notes.md
+    - name: 2210
       href: azure-stack-edge-gpu-2210-release-notes.md
     - name: 2209
       href: azure-stack-edge-gpu-2209-release-notes.md

articles/databox-online/azure-stack-edge-gpu-2301-release-notes.md

@@ -21,13 +21,13 @@ The release notes are continuously updated, and as critical issues requiring a w
 
 This article applies to the **Azure Stack Edge 2301** release, which maps to software version **2.2.2162.730**.
 
-## Supported upgrade paths
+## Supported update paths
 
 This software can be applied to your device if you're running **Azure Stack Edge 2207 or later** (2.2.2026.5318).
 
-You can upgrade to the latest version using the following upgrade paths:
+You can update to the latest version using the following update paths:
 
-| Current version     | Upgrade to | Then apply |
+| Current version     | Update to | Then apply |
 | --------------------| -----------| -----------|
 |2205 and earlier     |2207        |2301
 |2207 and later       |2301        |
@@ -36,8 +36,8 @@ You can upgrade to the latest version using the following upgrade paths:
 
 The 2301 release has the following new features and enhancements:
 
-- Starting March 2023, Azure Stack Edge devices will be required to be on the 2301 release or later to create a Kubernetes cluster. In preparation for this requirement, it is highly recommended that you upgrade to the latest version as soon as possible.
-- Beginning in this release, you can deploy Azure Kubernetes service (AKS) on an Azure Stack Edge cluster. This feature is supported only for SAP and PMEC customers. 
+- Starting March 2023, Azure Stack Edge devices will be required to be on the 2301 release or later to create a Kubernetes cluster. In preparation for this requirement, it is highly recommended that you update to the latest version as soon as possible.
+- Beginning this release, you can deploy Azure Kubernetes service (AKS) on an Azure Stack Edge cluster. This feature is supported only for SAP and PMEC customers. 
 
 ## Known issues from previous releases
 
@@ -70,7 +70,7 @@ The following table provides a summary of known issues carried over from the pre
 |**23.**|Custom script VM extension |There's a known issue in the Windows VMs that were created in an earlier release and the device was updated to 2103. <br> If you add a custom script extension on these VMs, the Windows VM Guest Agent (Version 2.7.41491.901 only) gets stuck in the update causing the extension deployment to time out. | To work around this issue: <br> 1. Connect to the Windows VM using remote desktop protocol (RDP). <br> 2. Make sure that the `waappagent.exe` is running on the machine: `Get-Process WaAppAgent`. <br> 3. If the `waappagent.exe` isn't running, restart the `rdagent` service: `Get-Service RdAgent` \| `Restart-Service`. Wait for 5 minutes.<br> 4. While the `waappagent.exe` is running, kill the `WindowsAzureGuest.exe` process. <br> 5. After you kill the process, the process starts running again with the newer version. <br> 6. Verify that the Windows VM Guest Agent version is 2.7.41491.971 using this command: `Get-Process WindowsAzureGuestAgent` \| `fl ProductVersion`.<br> 7. [Set up custom script extension on Windows VM](azure-stack-edge-gpu-deploy-virtual-machine-custom-script-extension.md).  |
 |**24.**|Multi-Process Service (MPS) |When the device software and the Kubernetes cluster are updated, the MPS setting isn't retained for the workloads.   |[Re-enable MPS](azure-stack-edge-gpu-connect-powershell-interface.md#connect-to-the-powershell-interface) and redeploy the workloads that were using MPS. |
 |**25.**|Wi-Fi |Wi-Fi doesn't work on Azure Stack Edge Pro 2 in this release. |
-|**26.**|Azure IoT Edge |The managed Azure IoT Edge solution on Azure Stack Edge is running on an older, obsolete IoT Edge runtime that is at end of life. For more information, see [IoT Edge v1.1 EoL: What does that mean for me?](https://techcommunity.microsoft.com/t5/internet-of-things-blog/iot-edge-v1-1-eol-what-does-that-mean-for-me/ba-p/3662137). Although the solution does not stop working past end of life, there are no plans to update it.  |To run the latest version of Azure IoT Edge [LTSs](../iot-edge/version-history.md#version-history) with the latest updates and features on their Azure Stack Edge, it is **recommended** to deploy a [customer self-managed IoT Edge solution](azure-stack-edge-gpu-deploy-iot-edge-linux-vm.md) that runs on a Linux VM. For more information, see [Move workloads from managed IoT Edge on Azure Stack Edge to an IoT Edge solution on a Linux VM](azure-stack-edge-move-to-self-service-iot-edge.md). |
+|**26.**|Azure IoT Edge |The managed Azure IoT Edge solution on Azure Stack Edge is running on an older, obsolete IoT Edge runtime that is at end of life. For more information, see [IoT Edge v1.1 EoL: What does that mean for me?](https://techcommunity.microsoft.com/t5/internet-of-things-blog/iot-edge-v1-1-eol-what-does-that-mean-for-me/ba-p/3662137). Although the solution does not stop working past end of life, there are no plans to update it.  |To run the latest version of Azure IoT Edge [LTSs](../iot-edge/version-history.md#version-history) with the latest updates and features on their Azure Stack Edge, we **recommend** that you deploy a [customer self-managed IoT Edge solution](azure-stack-edge-gpu-deploy-iot-edge-linux-vm.md) that runs on a Linux VM. For more information, see [Move workloads from managed IoT Edge on Azure Stack Edge to an IoT Edge solution on a Linux VM](azure-stack-edge-move-to-self-service-iot-edge.md). |
 
 ## Next steps
 

articles/databox-online/azure-stack-edge-gpu-install-update.md

@@ -40,19 +40,20 @@ For information on what's new in this update, go to [Release notes](azure-stack-
 
 - You can update to 2207 from 2106 or later, and then install 2301.
 
-## Upgrade Azure Kubernetes service on Azure Stack Edge
+### Update Azure Kubernetes service on Azure Stack Edge
 
-Use the following procedure only if you are an SAP or a PMEC customer.
+> [!IMPORTANT]
+> Use the following procedure only if you are an SAP or a PMEC customer.
 
-If you have Azure Kubernetes service deployed and your Azure Stack Edge device and Kubernetes versions are either 2207 or 2209, you must upgrade in multiple steps to apply 2301.
+If you have Azure Kubernetes service deployed and your Azure Stack Edge device and Kubernetes versions are either 2207 or 2209, you must update in multiple steps to apply 2301.
 
-Use the following steps to upgrade your Azure Stack Edge version and Kubernetes version to 2301:
+Use the following steps to update your Azure Stack Edge version and Kubernetes version to 2301:
 
-1. Upgrade your device version to 2301.
-1. Upgrade your Kubernetes version to 2210.
-1. Upgrade your Kubernetes version to 2301.
+1. Update your device version to 2301.
+1. Update your Kubernetes version to 2210.
+1. Update your Kubernetes version to 2301.
 
-If you are running 2210, you can upgrade both your device version and Kubernetes version directly to 2301.
+If you are running 2210, you can update both your device version and Kubernetes version directly to 2301.
 
 In Azure portal, the process will require two clicks, the first update gets your device version to 2301 and your Kubernetes version to 2210, and the second update gets your Kubernetes version upgraded to 2301.
 

articles/databox-online/media/azure-stack-edge-gpu-install-update/portal-update-17.png

@@ -3,7 +3,7 @@ author: alkohli
 ms.service: databox
 ms.author: alkohli
 ms.topic: include
-ms.date: 08/04/2022
+ms.date: 01/31/2023
 ---