Export (0) Print
Expand All

Test Installation

Updated: November 11, 2003

Applies To: Windows Server 2003 with SP1

There are several methods for verifying a cluster service installation after the Setup process is complete. These include:

  • Cluster Administrator: If installation was completed only on node 1, start Cluster Administrator, and then attempt to connect to the cluster. If a second node was installed, start Cluster Administrator on either node, connect to the cluster, and then verify that the second node is listed.

  • Services Applet: Use the services snap-in to verify that the cluster service is listed and started.

  • Event Log: Use the Event Viewer to check for ClusSvc entries in the system log. You should see entries confirming that the cluster service successfully formed or joined a cluster.

  • Cluster service registry entries: Verify that the cluster service installation process wrote the correct entries to the registry. You can find many of the registry settings under HKEY_LOCAL_MACHINE\Cluster

  • Click Start, click Run, and then type the Virtual Server name. Verify that you can connect and see resources.

Test Failover

To verify that resources will failover

  1. Click Start, click Programs, click Administrative Tools, and then click Cluster Administrator, as shown in Figure 26 below.

    1a9b5063-2387-489b-97e3-cff57b09db12Figure 26. The Cluster Administrator window.

  2. Right-click the Disk Group 1 group, and then click Move Group. The group and all its resources will be moved to another node. After a short period of time, the Disk F: G: will be brought online on the second node. Watch the window to see this shift. Quit Cluster Administrator.

Congratulations! You have completed the configuration of the cluster service on all nodes. The server cluster is fully operational. You are now ready to install cluster resources such as file shares, printer spoolers, cluster aware services like Distributed Transaction Coordinator, DHCP, WINS, or cluster-aware programs such as Exchange Server or SQL Server.

Community Additions

© 2016 Microsoft