How to Create a Two-Node Windows Failover Cluster
Applies to: Windows Server 2019, 2022 and 2025.
Cluster creation forms the management object and network identity after validation. Quorum and witness design must match site and failure scenarios.
Recovery procedures must be tested before an outage. Protect backup credentials and keep at least one recovery path separate from production. Visit networkmanager.info.
Prerequisites
- Pass cluster validation.
- Reserve cluster name and IP.
- Delegate computer-object creation or pre-stage the CNO.
- Choose witness location.
Procedure
Step 1: Create cluster
Use approved nodes, name and management address.
New-Cluster -Name 'APPCLUSTER' -Node NODE01,NODE02 -StaticAddress 192.0.2.60 -NoStorageStep 2: Review networks
Rename and set roles according to client and cluster traffic.
Get-ClusterNetworkStep 3: Configure witness
Example uses a file-share witness with appropriate permissions.
Set-ClusterQuorum -FileShareWitness '\\FSW01\APPCLUSTER-Witness'Step 4: Add storage or workload role
Use workload-specific supported procedures.
Step 5: Test controlled failover
Move a test role between nodes and review monitoring.
Verification
Check nodes, groups, networks and quorum.
Get-Cluster
Get-ClusterNode
Get-ClusterGroup
Get-ClusterQuorum
Test-ClusterRollback and recovery considerations
Do not Remove-Cluster while workloads or storage depend on it. Migrate roles and preserve data before formal decommissioning.
Operational notes
A two-node cluster normally needs a witness so quorum survives one node failure.
