Merge pull request #15628 from MicrosoftDocs/main

8/6/2024 PM Publish

Author: Taojunshen

azure-stack/hci/deploy/deployment-prep-active-directory.md

@@ -3,7 +3,7 @@ title: Prepare Active Directory for new Azure Stack HCI, version 23H2 deployment
 description: Learn how to prepare Active Directory before you deploy Azure Stack HCI, version 23H2.
 author: alkohli
 ms.topic: how-to
-ms.date: 06/13/2024
+ms.date: 08/05/2024
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.subservice: azure-stack-hci
@@ -46,7 +46,7 @@ Before you begin, make sure you've done the following:
 
 ## Active Directory preparation module
 
-The *AsHciADArtifactsPreCreationTool.ps1* module is used to prepare Active Directory. Here are the required parameters associated with the cmdlet:
+The `New-HciAdObjectsPreCreation` cmdlet of the AsHciADArtifactsPreCreationTool PowerShell module is used to prepare Active Directory for Azure Stack HCI deployments. Here are the required parameters associated with the cmdlet:
 
 |Parameter|Description|
 |--|--|
@@ -60,14 +60,13 @@ The *AsHciADArtifactsPreCreationTool.ps1* module is used to prepare Active Direc
 |`-Deploy`|Select this scenario for a brand new deployment instead of an upgrade of an existing system.|-->
 
 > [!NOTE]
-> - The `-AsHciOUName` path doesn't support the following special characters anywhere within the path `- &,”,’,<,>`.
+> - The `-AsHciOUName` path doesn't support the following special characters anywhere within the path: `&,",',<,>`.
 > - Moving the computer objects to a different OU after the deployment is complete is also not supported.
 
 ## Prepare Active Directory
 
 When you prepare Active Directory, you create a dedicated Organizational Unit (OU) to place the Azure Stack HCI related objects such as deployment user.
 
-
 To create a dedicated OU, follow these steps:
 
 1. Sign in to a computer that is joined to your Active Directory domain.

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

@@ -3,7 +3,7 @@ title: Prerequisites to deploy Azure Stack HCI, version 23H2
 description: Learn about the prerequisites to deploy Azure Stack HCI, version 23H2.
 author: alkohli
 ms.topic: conceptual
-ms.date: 05/02/2024
+ms.date: 08/05/2024
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.subservice: azure-stack-hci
@@ -34,7 +34,7 @@ Use the following checklist to gather the required information ahead of the actu
 |Component|What is needed|
 |--|--|
 |Server names|Unique name for each server you wish to deploy.|
-|Active directory OU|A new organizational unit (OU) to store all the objects for the Azure Stack HCI deployment. The OU is created during the [Active Directory preparation](./deployment-prep-active-directory.md).<br>The OU must be specified as the distinguished name (DN). The OU path doesn't support the following special characters anywhere within the path `- &,”,’,<,>`. For more information, see the format of [Distinguished Names](/previous-versions/windows/desktop/ldap/distinguished-names).|
+|Active directory OU|A new organizational unit (OU) to store all the objects for the Azure Stack HCI deployment. The OU is created during the [Active Directory preparation](./deployment-prep-active-directory.md).<br>The OU must be specified as the distinguished name (DN). The OU path doesn't support the following special characters anywhere within the path: `&,",',<,>`. For more information, see the format of [Distinguished Names](/previous-versions/windows/desktop/ldap/distinguished-names).|
 |Active Directory Domain|Fully-qualified domain name (FQDN) for the Active Directory Domain Services prepared for deployment.|
 |Active Directory LCM User credential|A new username and password that is created with the appropriate  permissions for deployment. This account is the same as the user account used by the Azure Stack HCI deployment.<br>The password must conform to the Azure length and complexity requirements. Use a password that is at least 12 characters long. The password must contain the following: a lowercase character, an uppercase character, a numeral, and  a special character.<br> The name must be unique for each deployment and you can't use *admin* as the username.|
 |IPv4 network range subnet for management network intent|A subnet used for management network intent. You need an address range for management network with  a minimum of 6 available, contiguous IPs in this subnet. These IPs are used for infrastructure services with the first IP assigned to fail over clustering.<br> For more information, see the **Specify network settings** page in [Deploy via Azure portal](./deploy-via-portal.md#specify-network-settings).|

azure-stack/hci/manage/virtual-machine-image-centos.md

@@ -7,11 +7,14 @@ ms.topic: how-to
 ms.service: azure-stack
 ms.subservice: azure-stack-hci
 ms.custom: devx-track-azurecli, linux-related-content
-ms.date: 05/15/2024
+ms.date: 08/06/2024
 ---
 
 # Prepare a CentOS Linux image for Azure Stack HCI virtual machines (preview)
 
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that's reached end-of-life (EOL). Consider your use of CentOS and plan accordingly. For more information, see [CentOS end-of-life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
+
 [!INCLUDE [hci-applies-to-23h2](../../includes/hci-applies-to-23h2.md)]
 
 This article describes how to prepare a CentOS Linux image to create a virtual machine (VM) on your Azure Stack HCI cluster. You use the Azure CLI for the VM image creation.