Merge pull request #15820 from MicrosoftDocs/main

9/10/2024 AM Publish

Author: Taojunshen

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

@@ -57,7 +57,7 @@ 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.
 
     # [PowerShell](#tab/powershell)
     ```powershell
@@ -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  |
@@ -135,7 +135,7 @@ Before you begin, make sure you've completed the following prerequisites:
     ```
 
     ---
-1. Connect to your Azure account and set the subscription. You'll need to open browser on the client that you're using to connect to the server and open this page: `https://microsoft.com/devicelogin` and enter the provided code in the Azure CLI output to authenticate. Get the access token and account ID for the registration.  
+2. Connect to your Azure account and set the subscription. You'll need to open browser on the client that you're using to connect to the server and open this page: `https://microsoft.com/devicelogin` and enter the provided code in the Azure CLI output to authenticate. Get the access token and account ID for the registration.  
 
     # [PowerShell](#tab/powershell)
 
@@ -169,7 +169,7 @@ Before you begin, make sure you've completed the following prerequisites:
 
     ---
 
-1. Finally run the Arc registration script. The script takes a few minutes to run.
+3. Finally run the Arc registration script. The script takes a few minutes to run.
 
     # [PowerShell](#tab/powershell)
 
@@ -214,7 +214,7 @@ Before you begin, make sure you've completed the following prerequisites:
     ```
     ---
 
-1. After the script completes successfully on all the servers, verify that:
+4. After the script completes successfully on all the servers, verify that:
 
 
     1. Your servers are registered with Arc. Go to the Azure portal and then go to the resource group associated with the registration. The servers appear within the specified resource group as **Machine - Azure Arc** type resources.

azure-stack/hci/deploy/deployment-azure-arc-gateway-new-cluster.md

@@ -78,7 +78,7 @@ Azure Stack HCI requires the Arc agent installation to follow a specific procedu
 
 However, for this Preview, you need to invoke the initialization script by passing the  **ArcGatewayID** value. Here's an example of how you should change the initialization script:
 
-```azurecli
+```powershell
 #Install required PowerShell modules in your node for registration
 Install-Module Az.Accounts -RequiredVersion 2.13.2
 Install-Module Az.Resources -RequiredVersion 6.12.0
@@ -130,9 +130,12 @@ You can audit the Arc gateway traffic by viewing the gateway router logs.
 
 Follow these steps to view the logs:
 
-1. Run the `azcmagent logs` command.
+1. Run the following command:
+   ```azurecli
+   azcmagent logs
+   ```
 
-1. In the resulting .zip file, view the logs in the *C:\ProgramData\Microsoft\ArcGatewayRouter* folder.
+1. In the resulting **.zip** file, view the logs in the `C:\ProgramData\Microsoft\ArcGatewayRouter` folder.
 
 
 ## Next steps

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

@@ -139,8 +139,7 @@ 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
 
 Install the Hyper-V role. Run the following command on each server of the cluster:
 
@@ -150,8 +149,7 @@ 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
 

azure-stack/hci/plan/configure-custom-settings-active-directory.md

@@ -112,6 +112,34 @@ To verify that the DNS record exists, run the following command:
 nslookup "machine name"
 ```
 
+## Disjoint namespace
+
+A disjoint namespace occurs when the primary DNS suffix of one or more domain member computers doesn't match the DNS name of their Active Directory domain. For example, if a computer has a DNS name of corp.contoso.com but is part of an Active Directory domain called na.corp.contoso.com, it's using a disjoint namespace.
+
+Before deploying Azure Stack HCI version 23H2, you must:
+
+- Append the DNS suffix to the management adapter of every node.
+- Verify you can resolve the hostname to the FQDN of the Active Directory.
+
+### Example - append the DNS suffix
+
+To append the DNS suffix, run the following command:
+
+```powershell
+Set-DnsClient -InterfaceIndex 12 -ConnectionSpecificSuffix "na.corp.contoso.com"
+```
+
+### Example - resolve the hostname to the FQDN
+
+To resolve the hostname to the FQDN, run the following command:
+
+```powershell
+nslookup node1.na.corp.contoso.com
+```
+
+> [!NOTE]
+> You cannot use group policies to configure the DNS suffix list with Azure Stack HCI, version 23H2.
+
 ## Cluster aware updating (CAU)
 
 Cluster aware updating applies a client access point (Virtual Computer Object) that requires a DNS record.