Sync release-hotfixes with main

Sync release-hotfixes with main

Author: sethmanheim

.openpublishing.redirection.json

@@ -1339,6 +1339,11 @@
       "source_path": "azure-stack/user/vm-update-management.md",
       "redirect_url": "/azure/azure-monitor/agents/agents-overview",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "azure-stack/hci/manage/processor-compatibility-mode.md",
+      "redirect_url": "/windows-server/virtualization/hyper-v/manage/dynamic-processor-compatibility-mode?pivots=azure-stack-hci",
+      "redirect_document_id": false
     }
   ]
 }

AKS-Hybrid/aks-edge-concept-clusters-nodes.md

@@ -1,10 +1,10 @@
 ---
 title: AKS Edge Essentials clusters and nodes
-description: Clusters and nodes running on AKS Edge Essentials 
+description: Learn about clusters and nodes running on AKS Edge Essentials.
 author: rcheeran
 ms.author: rcheeran
 ms.topic: conceptual
-ms.date: 10/06/2023
+ms.date: 07/11/2024
 ms.custom: template-concept
 ---
 

AKS-Hybrid/aks-edge-concept-networking.md

@@ -4,7 +4,7 @@ description: Basic networking concepts for AKS Edge Essentials
 author: fcabrera23
 ms.author: fcabrera
 ms.topic: conceptual
-ms.date: 10/06/2023
+ms.date: 07/11/2024
 ms.custom: template-concept
 ---
 
@@ -13,7 +13,7 @@ ms.custom: template-concept
 This article describes how to configure the networking between the Windows host OS and the Linux and Windows nodes' virtual machines. For more information about AKS Edge Essentials architecture, see the [AKS Edge Essentials overview](./aks-edge-overview.md).
 
 >[!TIP]
->The following guide describes different networking concepts and configurations available in AKS Edge Essentials. If you are using a single machine cluster, the installer and deployment mechanism handle all the necessary networking configuration. No extra steps or configuration are needed to deploy your cluster.
+>The following guide describes different networking concepts and configurations available in AKS Edge Essentials. If you use a single machine cluster, the installer and deployment mechanism handle all the necessary networking configuration. No extra steps or configuration are needed to deploy your cluster.
 
 ## Networking
 
@@ -34,7 +34,7 @@ The following key networking concepts for AKS Edge Essentials align with Kuberne
 
 If AKS Edge Essentials is deployed using a single machine cluster or a scalable cluster, we support different types of switches, IP address assignation, and configurations, as shown in the following table.
 
-|                     | Single Machine Cluster | Scalable Cluster |
+|                     | Single machine cluster | Scalable cluster |
 | ------------------- | ---------------------- | ---------------- |
 | **Type of virtual switch** | Internal | External |
 | **Virtual switch creation** | Automatic | Manually by user or automatically based on physical net adapter name. |

AKS-Hybrid/aks-edge-deployment-config-json.md

@@ -1,10 +1,10 @@
 ---
 title: AKS Edge Essentials deployment configuration JSON parameters
-description: Description of deployment configuration JSON parameters.
+description: Description of deployment configuration JSON parameters in AKS Edge Essentials.
 author: yujinkim-msft
 ms.author: yujinkim
 ms.topic: conceptual
-ms.date: 10/03/2023
+ms.date: 07/11/2024
 ms.custom: template-concept
 ---
 
@@ -69,5 +69,5 @@ You can find the complete JSON schema file at `C:\Program Files\AksEdge\aksedge-
 
 ## Next steps
 
-- [AKS Edge Essentials nodes and clusters](./aks-edge-concept-clusters-nodes.md)
-- [Set up your machine](./aks-edge-howto-setup-machine.md)
+- [AKS Edge Essentials nodes and clusters](aks-edge-concept-clusters-nodes.md)
+- [Set up your machine](aks-edge-howto-setup-machine.md)

AKS-Hybrid/aks-edge-howto-access-tpm.md

@@ -4,13 +4,13 @@ description: Learn how to access the TPM from a Linux virtual machine.
 author: rcheeran
 ms.author: rcheeran
 ms.topic: how-to
-ms.date: 10/10/2023
+ms.date: 07/12/2024
 ms.custom: template-how-to, linux-related-content
 ---
 
 # TPM access for AKS Edge Essentials
 
-A [Trusted Platform Module (TPM)](/windows/security/information-protection/tpm/trusted-platform-module-top-node) chip is a secure crypto-processor that is designed to carry out cryptographic operations. This technology is designed to provide hardware-based, security-related functions. You can enable or disable the TPM passthrough feature that enables the AKS Edge Essentials virtual machine to use the Windows host OS TPM. The TPM passthrough feature provides read-only access to cryptographic keys stored inside the TPM.
+A [Trusted Platform Module (TPM) chip](/windows/security/information-protection/tpm/trusted-platform-module-top-node) is a secure crypto-processor that is designed to carry out cryptographic operations. This technology is designed to provide hardware-based, security-related functions. You can enable or disable the TPM passthrough feature that enables the AKS Edge Essentials virtual machine to use the Windows host OS TPM. The TPM passthrough feature provides read-only access to cryptographic keys stored inside the TPM.
 
 This article describes how to develop sample code in C# to read cryptographic keys stored inside the device's discrete TPM.
 
@@ -20,9 +20,7 @@ This article describes how to develop sample code in C# to read cryptographic ke
 ## Prerequisites
 
 - A Windows host OS with a TPM or vTPM (if you're using a Windows host OS virtual machine).
-
 - Enable TPM access from the CBL-Mariner virtual machine with TPM passthrough enabled. In your **aksedge-config** file, in the `machines` section, set the `Machine.LinuxNode.TpmPassthrough` value to `True`. You can only enable or disable TPM access when creating a new deployment. Once you set the flag, it can't be changed unless you remove the deployment or node.
-
 - Ensure that the Non-Volatile(NV) index (default index=3001) is initialized with 8 bytes of data. The default **AuthValue** used by the sample is **{1,2,3,4,5,6,7,8}**, which corresponds to the NV (Windows) sample in the **TSS.MSR** libraries when writing to the TPM. All index initialization must take place on the Windows host before reading from the CBL-Mariner VM. For more information about TPM samples, see [TSS.MSR](https://github.com/microsoft/TSS.MSR).
 
 > [!CAUTION]
@@ -37,25 +35,17 @@ The following steps show how to create a sample executable to access a discrete
     :::image type="content" source="media/aks-edge/vs-new-solution.png" alt-text="Screenshot showing Visual Studio create new solution." lightbox="media/aks-edge/vs-new-solution.png":::
 
 1. Type the **Project Name**, **Location** and **Solution Name** fields, then select **Next**.
-
 1. Choose a target framework. The latest .NET 6.0 Long Term Support (LTS) version is preferred. After you choose a target framework, select **Create**. Visual Studio creates a new console app solution.
-
 1. In **Solution Explorer**, right-click the project name and select **Manage NuGet Packages**.
-
 1. Select **Browse** and then search for **Microsoft.TSS**. For more information about this package, see [Microsoft.TSS](https://www.nuget.org/packages/Microsoft.TSS). Choose the **Microsoft.TSS** package from the list, then select **Install**.
-
 1. Edit the **Program.cs** file and replace the contents with the [tpm-read-nv sample code - Program.cs](https://github.com/Azure/iotedge-eflow/blob/main/samples/tpm-read-nv/Program.cs).
-
 1. Select **Build > Build solution** to build the project. Verify that the build is successful.
-
 1. In **Solution Explorer**, right-click the project, then select **Publish**.
-
 1. In the **Publish** wizard, choose **Folder > Folder**. Select **Browse** and then choose an output location for the executable file to be generated. Select **Finish**. After the publish profile is created, select **Close**.
-
 1. On the **Publish** tab, select **Show all settings**. Change the following configuration, then select **Save**:
 
-    - Target Runtime:  **linux-x64**.
-    - Deployment mode: **Self-contained**.
+   - Target Runtime:  **linux-x64**.
+   - Deployment mode: **Self-contained**.
 
 1. Select **Publish**, then wait for the executable to be created.
 
@@ -66,37 +56,36 @@ If publishing succeeds, you should see the new files created in your output fold
 Once the executable file and dependency files are created, copy the folder to the CBL-Mariner virtual machine. The following steps show how to copy all the necessary files and how to run the executable inside the CBL-Mariner virtual machine.
 
 1. Open an elevated PowerShell session.
+1. Change the directory to the parent folder that contains the published files.
 
-1. Change directory to the parent folder that contains the published files.
-
-    For example, if your published files are under the folder **TPM** in the directory **C:\Users\<User>**, you can use the following command to change to the parent folder:
+   For example, if your published files are under the folder **TPM** in the directory **C:\Users\<User>**, you can use the following command to change to the parent folder:
 
-    ```powershell
-    cd "C:\Users\<User>"
-    ```
+   ```powershell
+   cd "C:\Users\<User>"
+   ```
 
 1. Modify the **TPMRead.runtimeconfig.json** file to avoid an [ICU globalization issue](https://github.com/dotnet/core/issues/2186#issuecomment-472629489) inside the Linux VM:
 
-    1. Open **TPMRead.runtimeconfig.json**.
-    2. Add the following line inside the `configProperties` section:
+   1. Open **TPMRead.runtimeconfig.json**.
+   2. Add the following line inside the `configProperties` section:
 
-       ```json
-       "System.Globalization.Invariant": true
-       ```
+      ```json
+      "System.Globalization.Invariant": true
+      ```
 
 1. Create a **tar** file with all the files created in previous steps.
 
-    For example, if you have all your files under the folder **TPM**, you can use the following command to create the **TPM.tar** file:
+   For example, if you have all your files under the folder **TPM**, you can use the following command to create the **TPM.tar** file:
 
-    ```powershell
-    tar -cvzf TPM.tar ".\TPM"
-    ```
+   ```powershell
+   tar -cvzf TPM.tar ".\TPM"
+   ```
 
 1. Once the **TPM.tar** file is successfully created, use the `Copy-AksEdgeNodeFile` cmdlet to copy the **tar** file to the CBL-Mariner VM. For example, if you have the **tar** file name **TPM.tar** in the directory **C:\Users\<User>**, you can use the following command to copy to the CBL-Mariner VM:
 
-    ```powershell
-    Copy-AksEdgeNodeFile -fromFile "C:\Users\<User>\TPM.tar" -toFile "/home/aksedge-user/" -pushFile
-    ```
+   ```powershell
+   Copy-AksEdgeNodeFile -fromFile "C:\Users\<User>\TPM.tar" -toFile "/home/aksedge-user/" -pushFile
+   ```
 
 1. Run the following command to extract all the content from the **tar** file:
 
@@ -106,19 +95,19 @@ Once the executable file and dependency files are created, copy the folder to th
 
 1. After extraction, add executable permission to the main executable file. For example, if your project name was **TPMRead**, your main executable is named **TPMRead**. Run the following command to make it executable:
 
-    ```powershell
-    Invoke-AksEdgeNodeCommand -NodeType "Linux" -command "chmod +x /home/aksedge-user/TPM/TPMRead"
-    ```
+   ```powershell
+   Invoke-AksEdgeNodeCommand -NodeType "Linux" -command "chmod +x /home/aksedge-user/TPM/TPMRead"
+   ```
 
 1. The last step is to run the executable file. For example, if your project name is **TPMRead**, run the following command:
 
-    ```powershell
-    Invoke-AksEdgeNodeCommand -NodeType "Linux" -command "/home/aksedge-user/TPM/TPMRead"
-    ```
+   ```powershell
+   Invoke-AksEdgeNodeCommand -NodeType "Linux" -command "/home/aksedge-user/TPM/TPMRead"
+   ```
 
-    You should see output similar to the following:
+   You should see output similar to the following:
 
-    ![Screenshot showing TPM output.](./media/aks-edge/tpm-read-output.png)
+   ![Screenshot showing TPM output.](./media/aks-edge/tpm-read-output.png)
 
 ## Next steps
 

AKS-Hybrid/aks-edge-howto-expose-service.md

@@ -4,19 +4,19 @@ description: Learn how to expose a Kubernetes service with AKS Edge Essentials.
 author: fcabrera23
 ms.author: fcabrera
 ms.topic: how-to
-ms.date: 10/12/2023
+ms.date: 07/12/2024
 ms.custom: template-how-to
 ---
 
 # Expose Kubernetes services to external devices
 
-If you're working with Kubernetes applications, you might need to make Kubernetes services accessible to external devices so they can interact with the workloads you've deployed. This article explains how to expose Kubernetes services running on an AKS Edge Essentials cluster to external devices. Depending on the networking configuration you used to set up the Kubernetes cluster, there are two different ways to expose the services:
+If you work with Kubernetes applications, you might need to make Kubernetes services accessible to external devices so they can interact with the workloads you've deployed. This article explains how to expose Kubernetes services running on an AKS Edge Essentials cluster to external devices. Depending on the networking configuration you used to set up the Kubernetes cluster, there are two different ways to expose the services:
 
 1. Single machine cluster with port forwarding.
-2. Scalable cluster with external virtual switch.
+1. Scalable cluster with external virtual switch.
 
 > [!NOTE]
-> If you are using Kubernetes services, make sure to set up the `Init.ServiceIPRangeSize` and `Init.ServiceIPRangeStart` parameters during deployment. For more information, see [Deployment configuration JSON parameters](./aks-edge-deployment-config-json.md).
+> If you use Kubernetes services, make sure to set up the `Init.ServiceIPRangeSize` and `Init.ServiceIPRangeStart` parameters during deployment. For more information, see [Deployment configuration JSON parameters](./aks-edge-deployment-config-json.md).
 
 ## Option 1: single machine cluster with port forwarding
 

AKS-Hybrid/aks-edge-howto-metric-server.md

@@ -1,16 +1,16 @@
 ---
-title: Deploy metric server
-description: Steps to deploy metric server.
+title: Deploy metrics server on an AKS Edge Essentials cluster
+description: Learn about the steps to deploy a metrics server on an AKS Edge Essentials cluster.
 author: rcheeran
 ms.author: rcheeran
 ms.topic: how-to
-ms.date: 10/10/2023
+ms.date: 07/11/2024
 ms.custom: template-how-to
 ---
 
 # Metrics server on an AKS Edge Essentials cluster
 
-The [metrics server](https://github.com/kubernetes-sigs/metrics-server) is a tool that inspects your containers' resource consumption. You can find the [YAML file](https://github.com/Azure/AKS-Edge/blob/main/samples/others/metrics-server.yaml) for the metrics server deployment in the **/Samples/Other** folder in the [GitHub repo](https://github.com/Azure/AKS-Edge/).
+The [metrics server](https://github.com/kubernetes-sigs/metrics-server) is a tool that inspects your containers' resource consumption. You can find the [YAML file](https://github.com/Azure/AKS-Edge/blob/main/samples/others/metrics-server.yaml) for the metrics server deployment in the **/Samples/Other** folder [in the GitHub repo](https://github.com/Azure/AKS-Edge/).
 
 ## Deploy metrics server