According to the Microsoft SQL Server AlwaysOn Solutions Guide for High Availability and Disaster Recovery, the way to determine the voting is as follows:
Recommended Adjustments to Quorum Voting
To determine the recommended quorum voting configuration for the cluster, apply these guidelines, in
1. No vote by default. Assume that each node should not vote without explicit justification.
2. Include all primary nodes.Each node that hosts an AlwaysOn Availability Group primary replica or is
the preferred owner of the AlwaysOn Failover Cluster Instance should have a vote.
3. Include possible automatic failover owners.Each node that could host a primary replica or FCI, as
the result of an automatic failover, should have a vote.
4. Exclude secondary site nodes.In general, do not give votes to nodes that reside at a secondary
disaster recovery site.You do not want nodes in the secondary site to contribute to a decision to
take the cluster offline when there is nothing wrong with the primary site.
5. Odd number of votes.If necessary, add a witness file share, a witness node (with or without a SQL
Server instance), or a witness disk to the cluster and adjust the quorum mode to prevent possible
ties in the quorum vote.
6. Reassess vote assignments post-failover.You do not want to fail over into a cluster configuration
that does not support a healthy quorum.
For more information on adjusting node votes, see Configure Cluster Quorum NodeWeight
You cannot adjust the vote of a file share witness. Instead, you must select a different quorum mode to
include or exclude its vote.
Note:SQL Server exposes several system dynamic management views (DMVs) that can help you
administer settings related WSFC cluster configuration and node quorum voting.
For more information, seeMonitor Availability Groups(http://