What you're describing suggests a quorum misconfiguration or a node vote issue.
- Uneven or disabled node votes
- If only one node has a vote and the FSW is a vote, the cluster needs 2/2 votes to stay online.
- If the voting node is shut down, the remaining node + FSW = 1/2 votes → no quorum, cluster goes down.
- This would explain why the node not hosting the Cluster Group can’t keep it online alone.
Check with PowerShell:
Get-ClusterNode | ft Name, NodeWeight
All nodes should show NodeWeight = 1
.
- FSW is misconfigured or not really contributing to quorum
Even if both nodes can reach the File Share Witness, it might not be actively contributing to quorum.
Check quorum configuration:
Get-ClusterQuorum
You should see something like:
ClusterQuorumType : NodeAndFileShareMajority
QuorumResource : FileShareWitness (\\YourWitnessPath)
If it says NodeMajority
, or the file share witness is marked "not in use" or "not online", that's your issue.
- Cluster group is not automatically moving on node shutdown
Though the Cluster Service normally fails over roles before shutdown, if the node shuts down too fast, the cluster might not have time to transition ownership — especially if quorum is not maintained.
Confirm role failover settings:
Get-ClusterGroup | fl Name, AutoFailbackType, PreferredOwners
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin