Sync release-hotfixes with main, fix merge

Author: sethmanheim

AKS-Hybrid/aks-vmware-quickstart-deploy.md

@@ -88,12 +88,16 @@ To complete this quickstart, you need to do these things:
 
 ## Step 3: Create the AKS cluster
 
-Run the following command to create the cluster:
+Run the following command to create the cluster. 
 
 ```azurecli
-az aksarc create -n '<name of your cluster>' -g $resource_group --kubernetes-version 'v1.26.6' --custom-location $custom_location --aad-admin-group-object-ids $aad_group_id --vnet-ids $vnet_id --control-plane-ip $control_plane_ip --generate-ssh-keys --debug
+az aksarc create -n '<name of your cluster>' -g $resource_group --kubernetes-version '<Kubernetes version from the Arc Resource Bridge>' --custom-location $custom_location --aad-admin-group-object-ids $aad_group_id --vnet-ids $vnet_id --control-plane-ip $control_plane_ip --generate-ssh-keys --debug
 ```
 
+   > [!NOTE]
+   > In this preview release, you can only deploy the same Kubernetes version that the Arc Resource Bridge supports. The Kubernetes version you provide in the command must align with the Arc Resource Bridge version. You can find the Arc Resource Bridge version in the Azure portal under **Azure Arc > Management > Resource Bridge**. To determine the corresponding Kubernetes version, see [What's new with Azure Arc resource bridge](/azure/azure-arc/resource-bridge/release-notes).
+
+
 ## Next steps
 
 - See [Supported deployment scale](aks-vmware-scale-requirements.md) for the different configuration options.

AKS-Hybrid/aks-vmware-system-requirements.md

@@ -1,12 +1,12 @@
 ---
 title: System requirements and support matrix for AKS enabled by Azure Arc on VMware (preview)
 description: Learn about system requirements and the support matrix for AKS enabled by Azure Arc on VMware.
-ms.date: 03/22/2024
+ms.date: 09/16/2024
 ms.topic: conceptual
 author: sethmanheim
 ms.author: sethm
 ms.reviewer: leslielin
-ms.lastreviewed: 03/22/2024
+ms.lastreviewed: 09/16/2024
 
 ms.custom: references_regions
 
@@ -70,15 +70,35 @@ You should create a folder for VM templates, to store the Arc Resource Bridge an
 
 ## Supported Kubernetes version
 
-In this preview release, you can only deploy the same Kubernetes version that the Arc Resource Bridge supports. See the [Arc Resource Bridge release notes](https://github.com/Azure/ArcResourceBridge/releases) for information about which Kubernetes version is supported for each specific version number.
+In this preview release, you can only deploy the same Kubernetes version that the Arc Resource Bridge supports. You can find the Arc Resource Bridge version in the Azure portal under **Azure Arc > Management > Resource Bridge**. To determine the corresponding Kubernetes version, see [What's new with Azure Arc resource bridge](/azure/azure-arc/resource-bridge/release-notes).
 
 ## Custom location
 
-If you choose to **Enable Kubernetes Service on VMware [preview]** when you **Connect vCenter to Azure** [from the Azure portal](/azure/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script), a custom location with the prefix **AKS-**, and a default namespace, are created for you to deploy AKS on VMware. If you **Enable Kubernetes Service on VMware [preview]** using the [Azure CLI process](aks-vmware-install-kubernetes-extension.md), you can specify the name of the custom location of your choice with the default namespace.
+If you choose to **Enable Kubernetes Service on VMware [preview]** when you **Connect vCenter to Azure** [from the Azure portal](/azure/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script), a custom location with the prefix **AKS-**, and a default namespace, are created for you to deploy AKS on VMware. If you enable the Azure Kubernetes Service on VMware using the [Azure CLI process](aks-vmware-install-kubernetes-extension.md), you can specify the name of the custom location of your choice with the default namespace.
 
 > [!IMPORTANT]
 > You must use the **default** namespace.
 
+To view the custom location namespace, use the `az customlocation show` command:
+
+```azurecli  
+az customlocation show -g $customLocationResourceGroupName -n $customLocationName
+```
+
+If your custom location was not created with the **default** namespace, use the following command to delete the custom location and create a custom location with the default namespace. For more information about how to manage custom locations, see [Create and manage custom locations](/azure/azure-arc/kubernetes/custom-locations).
+
+Delete the custom location:
+
+```azurecli  
+az customlocation delete -g $customLocationResourceGroupName -n $customLocationName
+```
+
+Create the custom location with the **default** namespace:
+
+```azurecli  
+az customlocation create -g $customLocationResourceGroupName -n $customLocationName --cluster-extension-ids $clusteraksExtensionId --host-resource-id $ArcApplianceResourceId --namespace "default"
+```
+
 ## Azure requirements
 
 You must connect to your Azure account:

azure-stack/hci/deploy/deployment-arc-register-server-permissions.md

@@ -57,17 +57,17 @@ Before you begin, make sure you've completed the following prerequisites:
 > [!IMPORTANT]
 > Run these steps on every Azure Stack HCI server that you intend to cluster.
 
-<!-- 1. Install the [Arc registration script](https://www.powershellgallery.com/packages/AzSHCI.ARCInstaller) from PSGallery.
+1. Install the [Arc registration script](https://www.powershellgallery.com/packages/AzSHCI.ARCInstaller) from PSGallery. **This step is only required if you're using an OS ISO that's older than 2408**. For more information, see [What's new in 2408](../whats-new.md#features-and-improvements-in-2408).
 
     # [PowerShell](#tab/powershell)
     ```powershell
     #Register PSGallery as a trusted repo
     Register-PSRepository -Default -InstallationPolicy Trusted
 
     #Install required PowerShell modules in your node for registration
-    Install-Module Az.Accounts -RequiredVersion 2.13.2
+    Install-Module Az.Accounts -RequiredVersion 3.0.0
     Install-Module Az.Resources -RequiredVersion 6.12.0
-    Install-Module Az.ConnectedMachine -RequiredVersion 0.5.2
+    Install-Module Az.ConnectedMachine -RequiredVersion 0.8.0
     
 
     #Install Arc registration script from PSGallery 
@@ -77,9 +77,9 @@ Before you begin, make sure you've completed the following prerequisites:
     Here's a sample output of the installation:
 
     ```output
-    PS C:\Users\SetupUser> Install-Module Az.Accounts -RequiredVersion 2.13.2
+    PS C:\Users\SetupUser> Install-Module Az.Accounts -RequiredVersion 3.0.0
     PS C:\Users\SetupUser> Install-Module Az.Resources -RequiredVersion 6.12.0
-    PS C:\Users\SetupUser> Install-Module Az.ConnectedMachine -RequiredVersion 0.5.2
+    PS C:\Users\SetupUser> Install-Module Az.ConnectedMachine -RequiredVersion 0.8.0
     PS C:\Users\SetupUser> Install-Module -Name AzSHCI.ARCInstaller                                           
     NuGet provider is required to continue                                                                                  
     PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. The NuGet  provider must be available in 'C:\Program Files\PackageManagement\ProviderAssemblies' or
@@ -89,7 +89,7 @@ Before you begin, make sure you've completed the following prerequisites:
     [Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y
     PS C:\Users\SetupUser>
     ```
-    --- -->
+
 1. Set the parameters. The script takes in the following parameters:
 
     |Parameters  |Description  |

azure-stack/hci/deploy/deployment-install-os.md

@@ -139,7 +139,9 @@ Follow these steps to configure the operating system using SConfig:
     > - Make sure that the local administrator password follows Azure password length and complexity requirements. Use a password that is at least 12 characters long and contains a lowercase character, an uppercase character, a numeral, and a special character.
     > - Do not join the servers with the Azure Stack HCI operating system installed, to the Active Directory domain prior to cloud deployment. Cluster nodes are automatically joined to a domain during the [Deployment via Azure portal](./deploy-via-portal.md).
 
-<!--## Install required Windows roles
+## Install required Windows roles
+
+**This step is only required if you're using an OS ISO that's older than 2408**. For more information, see [What's new in 2408](../whats-new.md#features-and-improvements-in-2408).
 
 Install the Hyper-V role. Run the following command on each server of the cluster:
 
@@ -149,10 +151,9 @@ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
 
 Your servers will restart; this takes a few minutes.
 
-You are now ready to register the Azure Stack HCI server with Azure Arc and assign permissions for deployment. -->
+You are now ready to register the Azure Stack HCI server with Azure Arc and assign permissions for deployment.
 
 ## Next steps
 
 - (Optional) [Configure proxy settings for Azure Stack HCI, version 23H2](../manage/configure-proxy-settings-23h2.md).
-- [Register Azure Stack HCI servers in your system with Azure Arc and assign permissions](./deployment-arc-register-server-permissions.md).
-
+- [Register Azure Stack HCI servers in your system with Azure Arc and assign permissions](./deployment-arc-register-server-permissions.md).

azure-stack/hci/deploy/deployment-introduction.md

@@ -15,8 +15,6 @@ ms.subservice: azure-stack-hci
 
 This article is the first in the series of deployment articles that describe how to deploy Azure Stack HCI, version 23H2. This article applies to both single and multi-node deployments. The target audience for this article is IT administrators who are responsible for deploying Azure Stack HCI in their organization.
 
-[!INCLUDE [important-23h2](../../includes/hci-important-deploy-23h2.md)]
-
 ## About deployment methods
 
 In this release, you can deploy Azure Stack HCI using one of the following methods:

azure-stack/hci/manage/manage-arc-virtual-machines.md

@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-stack
 ms.subservice: azure-stack-hci
-ms.date: 09/09/2024
+ms.date: 09/13/2024
 ---
 
 # Manage Arc VMs on Azure Stack HCI
@@ -15,7 +15,6 @@ ms.date: 09/09/2024
 
 This article describes how to manage Arc virtual machines (VMs) running on Azure Stack HCI, version 23H2. The procedures to enable guest management, start, stop, restart, pause, save, or delete an Arc VM, are detailed.
 
-
 ## Prerequisites
 
 Before you begin, make sure to complete the following prerequisites:
@@ -34,10 +33,11 @@ There are two agents that are important to understand in the context of guest ma
 
 When you enable guest management on an Arc VM, the guest agent installs the [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview). The Azure Connected Machine agent enables you to manage Azure Arc VM extensions on your Azure Stack HCI VM.
 
-Based on whether a guest agent is running on your Arc VM, the steps to enable guest management are different.
+Here are some key considerations for enabling guest management on a VM after provisioning it:
 
-> [!IMPORTANT] 
-> Make sure that your Azure Stack HCI cluster is running 2311 or later to run this procedure.
+- Make sure that your Azure Stack HCI cluster is running 2311 or later.
+- Enabling guest management after VM provisioning isn't supported for Windows Server 2012 and Windows Server 2012 R2.
+- The steps to enable guest management differ based on whether a guest agent is running on your Arc VM.
 
 ### Verify if guest agent is running
 

azure-stack/operator/release-notes.md

@@ -3,7 +3,7 @@ title: Azure Stack Hub release notes
 description: Release notes for Azure Stack Hub integrated systems, including updates and bug fixes.
 author: sethmanheim
 ms.topic: article
-ms.date: 09/06/2024
+ms.date: 09/13/2024
 ms.author: sethm
 ms.reviewer: rtiberiu
 ms.lastreviewed: 04/22/2024
@@ -130,10 +130,10 @@ The Azure Stack Hub 2311 update build type is **Full**. This build contains only
 
 The 2311 update has the following expected runtimes based on our internal testing:
 
-- 4 nodes: 8-28 hours
-- 8 nodes: 11-30 hours
-- 12 nodes: 14-34 hours
-- 16 nodes: 17-40 hours
+- 4 nodes: 36-50 hours
+- 8 nodes: 36-50 hours
+- 12 nodes: 50-80 hours
+- 16 nodes: 50-90 hours
 
 > [!IMPORTANT]
 > Disconnected environments have additional prerequisite steps, which might increase this duration. See the following section for required steps to obtain and update a SQL Server 2019 product key (PID).

azure-stack/user/azure-stack-storage-connect-se.md

@@ -49,8 +49,6 @@ Export and then import Azure Stack Hub certificate for disconnected integrated s
 
 4.  Under **Console Root\Certificated (Local Computer)\Trusted Root Certification Authorities\Certificates** find **AzureStackSelfSignedRootCert**.
 
-    ![Load the Azure Stack Hub root certificate through mmc.exe](./media/azure-stack-storage-connect-se/add-certificate-azure-stack.png)
-
 5. Right-click the certificate, select **All Tasks** > **Export**, and then follow the instructions to export the certificate with **Base-64 encoded X.509 (.CER)**.
 
     The exported certificate will be used in the next step.