Windows Server Failover Clustering: Step-by-Step Setup Guide (2026)

Failover Clustering is the foundation that Storage Spaces Direct, clustered Hyper-V, and clustered SQL Server all sit on top of, so getting a solid, validated cluster stood up correctly is worth doing carefully even if your first use case is simple.

• Available in Windows Server Standard and Datacenter, not a Datacenter-only feature
• Needs at least 2 nodes, but always run Test-Cluster validation before creating one, even for 2-node clusters
• Quorum configuration determines how the cluster survives node failures. Get this wrong and a single node loss can take everything offline
• A Cluster Shared Volume (CSV) lets multiple nodes access the same storage simultaneously

Step 1: Install the feature and validate

Install-WindowsFeature Failover-Clustering -IncludeManagementTools on every node, then validate before creating anything:

Test-Cluster -Node Node1,Node2

Fix every error in the report before proceeding. Warnings are often acceptable depending on context, but errors mean the cluster will be unsupported or unstable.

Step 2: Create the cluster

New-Cluster -Name "Cluster01" -Node Node1,Node2 -StaticAddress 10.0.1.50

Step 3: Configure quorum correctly

For 2-node clusters specifically, add a witness. Either a file share witness or (preferably, if you have internet access from the cluster) a cloud witness using Azure Blob Storage. Without a witness, a 2-node cluster can suffer a “split brain” scenario where both nodes think they should be active:

Set-ClusterQuorum -CloudWitness -AccountName "mystorageaccount" -AccessKey "..."

Step 4: Add your first clustered role

With the cluster healthy and quorum configured, add whatever role you’re clustering for. A file server role, a Hyper-V VM, or a SQL Server instance. Test failover manually with Move-ClusterGroup before relying on it, to confirm the role actually comes back online cleanly on the other node rather than assuming it will.

If your end goal is a hyperconverged setup, our guide on configuring Storage Spaces Direct picks up exactly where this one leaves off.

For official guidance, see Microsoft’s Windows Server documentation.