Preventing Clients From Accessing the Cluster Host
Updated: March 28, 2003
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Before you upgrade a cluster host, you must ensure that no clients have active sessions running on the cluster host. During the upgrade process, the cluster host is still connected to the network infrastructure.
However, to prevent new clients from starting sessions or applications on the cluster host, perform a drainstop on the cluster host to be upgraded. Performing a drainstop prevents new clients from accessing the cluster while allowing existing clients to continue until they have completed their current operations.
In addition, configure the Default state of the Initial host state to Stopped. Configuring the cluster host in this manner ensures the cluster host cannot rejoin the cluster during the upgrade process. Because the upgrade process requires the cluster host to restart, you need to verify that the upgrade completed successfully before adding the cluster host back to the cluster.
You can configure the Initial host state through Network Load Balancing Manager or the property settings of the cluster network adapter.
For more information about performing a drainstop on the source cluster and changing the Default state of cluster host, see "Create and Manage Network Load Balancing Clusters" in Help and Support Center for Windows Server 2003.