Merge pull request #7679 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/windowsserverdocs (branch main)

Author: robinharwood

WindowsServerDocs/failover-clustering/create-workgroup-cluster.md

@@ -92,7 +92,7 @@ A consistent administrator user account must be created on each node. The userna
 
 1. If the nonbuiltin administrator account isn't used, then you need to set the LocalAccountTokenFilterPolicy in the registry. The policy can be done in PowerShell with the following command:
     ```PowerShell
-    New-itemproperty -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System –Name LocalAccountTokenFilterPolicy -Value 1​
+    New-itemproperty -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name LocalAccountTokenFilterPolicy -Value 1​
     ```
 
 ---
@@ -176,7 +176,7 @@ The following steps show how to install the Failover Clustering feature in Power
 
 1. Run the PowerShell command:
     ```PowerShell
-    Install-WindowsFeature –Name Failover-Clustering –IncludeManagementTools
+    Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools
     ```
 
 1. Once the installation process is done, verify installation was successful by running these commands:
@@ -265,7 +265,7 @@ If you prefer to create a workgroup cluster using PowerShell, follow these steps
 
 1. After validation passes, create the workgroup cluster using the following command:
     ```PowerShell
-    New-Cluster –Name MyCluster -Node server1, server2 -AdministrativeAccessPoint DNS
+    New-Cluster -Name MyCluster -Node server1, server2 -AdministrativeAccessPoint DNS
     ```
 
 1. After the cluster is successfully created, you can do things such as verify cluster [quorum configuration](/azure/azure-local/concepts/quorum?context=/windows-server/context/windows-server-failover-clustering), [create clustered roles](/windows-server/failover-clustering/create-failover-cluster#create-clustered-roles), and optionally, create [Cluster Shared Volumes (CSV)](failover-cluster-csvs.md).

WindowsServerDocs/networking/network-atc/network-atc.md

@@ -4,7 +4,7 @@ description: Learn how to deploy host networking with Network ATC for Windows Se
 #customer intent: As a network administrator, I want to deploy host networking using Network ATC so that I can manage compute, storage, and management networks across all cluster nodes using the same adapters.
 author: robinharwood
 ms.topic: how-to
-ms.date: 07/18/2025
+ms.date: 11/20/2025
 ms.author: roharwoo
 ms.custom:
   - ai-gen-docs-bap
@@ -251,18 +251,6 @@ Get-NetQosPolicy | Remove-NetQosPolicy -Confirm:$false
 Get-NetQosFlowControl | Disable-NetQosFlowControl
 ```
 
-### Error: Network Symmetry Check Failure
-
-You might encounter a situation where functionally symmetric adapters have different component ID strings. It might occur if a substring is added to an adapter's component ID during an upgrade or when combining OCP and PCI NICs within the same intent. To work around this issue, you can disable the component ID based symmetry check by setting the `NicSymmetryCheckEnabled` registry key to 0. This setting allows Network ATC to proceed with the deployment without checking for symmetry based on component IDs. You should only use this workaround if you're certain that the adapters are functionally symmetric.
-
-```powershell
-Stop-Service -Name NetworkATC
-New-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\NetworkATC' -Name "NicSymmetryCheckEnabled" -Value 0 -PropertyType DWord
-Start-Service -Name NetworkATC
-```
-
-After you disable the component ID based symmetry check, you can continue with the intent deployment.
-
 ### Error: RDMANotOperational
 
 :::image type="content" source="../media/network-atc/error-rdmanotoperational.png" alt-text="Screenshot of RDMA Not Operational error."  lightbox="../media/network-atc/error-rdmanotoperational.png":::