Windows Server / Hyper-V & Failover Clustering
Check failover-cluster node state before restarting a host
A node can be paused, draining or disconnected while resources run elsewhere. Inspect cluster state before taking corrective action.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-ClusterNodeRead the result
With FailoverClusters tools and delegated access, the output reports node states in the selected cluster context. It is not a complete hardware or workload health assessment.
Resolve and verify
Correlate the node's state with maintenance history, cluster events and resource ownership. Restore it through the supported operational procedure after fixing the underlying issue.
Before changing production
Do not restart multiple nodes or resume a node still under maintenance without confirming quorum and workload capacity.