Merge pull request #15816 from MicrosoftDocs/main

9/9/2024 PM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -195,6 +195,11 @@
       "redirect_url":"/azure-stack/operator/app-service-release-notes-2302", 
       "redirect_document_id":false
     },    
+    { 
+      "source_path":"azure-stack/operator/azure-stack-app-service-release-notes-update-six.md", 
+      "redirect_url":"/azure-stack/operator/app-service-release-notes-2302", 
+      "redirect_document_id":false
+    },    
     { 
       "source_path":"azure-stack/operator/azure-stack-app-service-release-notes-update-four.md", 
       "redirect_url":"/azure-stack/operator/app-service-release-notes-2302", 

azure-managed-lustre/media/create-file-system-portal/advanced-maintenance-window.png

@@ -26,6 +26,9 @@ Active Directory requirements for Azure Stack HCI include:
 > - You can use your existing process to meet the above requirements. The script used in this article is optional and is provided to simplify the preparation.
 > - When group policy inheritance is blocked at the OU level, enforced GPO's aren't blocked. Ensure that any applicable GPO, which are enforced, are also blocked using other methods, for example, using [WMI Filters](https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/fun-with-wmi-filters-in-group-policy/ba-p/395648) or [security groups](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012).
 
+To manually assign the required permissions for Active Directory, create an OU, and block GPO inheritance, see
+[Custom Active Directory configuration for your Azure Stack HCI, version 23H2](../plan/configure-custom-settings-active-directory.md).
+
 ## Prerequisites
 
 Before you begin, make sure you've done the following:

azure-managed-lustre/media/create-file-system-portal/basics-file-system-details.png

@@ -48,6 +48,8 @@ The following table lists the known issues in this release:
 |---------|---------|---------|
 | Arc VM management| Using an exported Azure VM OS disk as a VHD to create a gallery image for provisioning an Arc VM is unsupported. | |
 | Networking <!--29180461--> | When a node is configured with a proxy server that has capital letters in its address, such as **HTTP://10.100.000.00:8080**, Arc extensions fail to install or update on the node in existing builds, including version 2408. However, the node remains Arc connected. | Follow these steps to mitigate the issue: </br><br> 1. Set the environment values in lowercase. `[System.Environment]::SetEnvironmentVariable("HTTP_PROXY", "http://10.100.000.00:8080", "Machine")`. </br><br> 2. Validate that the values were set. `[System.Environment]::GetEnvironmentVariable("HTTP_PROXY", "Machine").` </br><br> 3. Restart Arc services. </br><br> `Restart-Service himds` </br><br> `Restart-Service ExtensionService` </br><br> `Restart-Service GCArcService` </br><br> 4. Signal the AzcmaAgent with the lowercase proxy information. </br><br> `& 'C:\Program Files\AzureConnectedMachineAgent\azcmagent.exe' config set proxy.url http://10.100.000.00:8080` </br><br>`& 'C:\Program Files\AzureConnectedMachineAgent\azcmagent.exe' config list` |
+| Networking <!--29229789--> | When Arc machines go down, the "**All Clusters**" page, in the new portal experience shows a "**PartiallyConnected**" or "**Not Connected Recently** status. Even when the Arc machines become healthy, they may not show a "**Connected**" status. | There's no known workaround for this issue. To check the connectivity status, use the old experience to see if it shows as "**Connected**". |
+| Security <!--29333930--> | The SideChannelMitigation security feature may not show an enabled state even if it's enabled. | There's no workaround in this release. If you encounter this issue, contact Microsoft Support to determine next steps. |
 
 ## Known issues from previous releases