Verifying Permissions, Hardware, and Software Before Troubleshooting the Quorum Resource
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Before you begin troubleshooting, you should verify permissions, hardware, and software updates, as described in the following list:
Make sure that you have administrative rights on the computer you are troubleshooting.
You cannot modify quorum resource settings unless you are a member of the Administrators group on the computer that you are administering.
To verify that you are a member of the Administrators group on a computer, open the Computer Management snap-in. In the console tree, double-click Local Users and Groups, and then click Groups. In the details pane, double-click Administrators and verify that the account that you logged in with appears in the Members list.
Confirm that your hardware is compatible with Windows Server 2003, Enterprise Edition, or Windows Server 2003, Datacenter Edition. For more information, see the following pages on the Microsoft Web site:
Confirm that cluster hardware is not disconnected or damaged. For example, check the cables to the cluster storage. If you use SCSI, check that the SCSI bus is properly terminated.
Set aside time to review the software updates and service pack level on each node. Consider whether the latest service pack, critical updates, and security updates need to be tested and deployed on the cluster, and if so, choose a time to do so. Carry out this testing and deployment using standard methods for your organization.
If you have not already planned for the testing and deployment of the latest service pack for Windows Server 2003, we strongly recommend that you plan for this. The service pack might enable the cluster to automatically correct future problems with the quorum resource — for example, corruption of a cluster configuration file on the quorum resource. For information about how to install service packs in a cluster, see article 174799 in the Microsoft Knowledge Base.
Set aside time to review the drivers and software, including non-Microsoft drivers and software, on each node. Consider whether updated drivers and software need to be tested and deployed on the cluster, and if so, choose a time to do so. Carry out this testing and deployment using standard methods for your organization.