You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: WindowsServerDocs/failover-clustering/create-workgroup-cluster.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ A consistent administrator user account must be created on each node. The userna
92
92
93
93
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:
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
265
265
266
266
1. After validation passes, create the workgroup cluster using the following command:
267
267
```PowerShell
268
-
New-Cluster –Name MyCluster -Node server1, server2 -AdministrativeAccessPoint DNS
268
+
New-Cluster -Name MyCluster -Node server1, server2 -AdministrativeAccessPoint DNS
269
269
```
270
270
271
271
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).
Copy file name to clipboardExpand all lines: WindowsServerDocs/networking/network-atc/network-atc.md
+1-13Lines changed: 1 addition & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to deploy host networking with Network ATC for Windows Se
4
4
#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.
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.
After you disable the component ID based symmetry check, you can continue with the intent deployment.
265
-
266
254
### Error: RDMANotOperational
267
255
268
256
:::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":::
Copy file name to clipboardExpand all lines: WindowsServerDocs/virtualization/hyper-v/Supported-CentOS-and-Red-Hat-Enterprise-Linux-virtual-machines-on-Hyper-V.md
+43Lines changed: 43 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,6 +120,49 @@ In this section:
120
120
| Boot using UEFI | Windows Server 2025, 2022, 2019, 2016 <br/>Azure Stack HCI | ✔ Note 14, 17 | ✔ Note 14 |
121
121
| Secure boot | Windows Server 2025, 2022, 2019, 2016 <br/>Azure Stack HCI | ✔ | ✔ |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments