Skip to content

Commit 482f0e7

Browse files
Merge pull request #4102 from MicrosoftDocs/main
[AutoPublish] main to live - 04/22 07:54 PDT | 04/22 20:24 IST
2 parents 61b8b1f + 228e443 commit 482f0e7

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docset/winserver2025-ps/FailoverClusters/Start-ClusterNode.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The `Start-ClusterNode` cmdlet starts the Cluster service on a node in a failove
2727
is the first node started, then it will wait for other nodes to join. The cluster will begin to run
2828
when a quorum has formed.
2929

30-
This cmdlet with the **FixQuorum** parameter can be used to force quorum, that is, force the start
30+
This cmdlet with the **ForceQuorum** parameter can be used to force quorum, that is, force the start
3131
of a cluster node even if quorum hasn't been achieved. When quorum is forced on a given node, the
3232
copy of the cluster configuration that is on that node will be treated as the authoritative copy and
3333
will be replicated to all other nodes. Therefore, forcing quorum should be considered a last resort,
@@ -62,7 +62,7 @@ This example starts the Cluster service on the node named `node1` on the cluster
6262
### Example 3
6363

6464
```powershell
65-
Start-ClusterNode -FixQuorum
65+
Start-ClusterNode -ForceQuorum
6666
```
6767

6868
This example forces the local node and the local cluster to start, even if quorum hasn't been

0 commit comments

Comments
 (0)