Installing and Configuring the First Cluster Host

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

After you have installed and configured the hardware for the cluster, you are ready to install and configure the first cluster host. The first cluster host acts as a master copy when you use an image-based deployment method (such as RIS, Sysprep, or a third-party product) to deploy the remaining cluster hosts.

An image-based deployment is faster and ensures consistency when implementing the remaining cluster hosts, by reducing or eliminating manual configuration. In addition, the same image-based deployment method can be reused after the deployment to restore failed cluster hosts.

Depending on the type of image-based deployment, different methods are used to customize the cluster host after the image has been restored. For example, Sysprep can allow you to interactively customize the image or use a configuration file — sysprep.inf — to customize the image. For more information about customizing the restored image, see "Designing Unattended Installations," "Designing Image-based Installations with Sysprep," and "Designing RIS Installations" in Automating and Customizing Installations of this kit*.*

Perform the following task on the first cluster host by using the "NLB Cluster Host Worksheet" that your design team completed for the first cluster host:

  1. If you did not use the automated installation process to create the new cluster, start Network Load Balancing Manager and create a new cluster.

    Tip

    • You can start Network Load Balancing Manager by running Nlbmgr.exe.
  2. Install the applications and services on the first cluster host.

    Examples of Windows Server 2003 services to be installed at this time include IIS or Terminal Services. For more information about installing Windows Server 2003 services, see the chapters that discuss those services in the Microsoft® Windows® Server 2003 Deployment Kit.

    Examples of applications to be installed at this time include, Web applications or Windows applications that run on Terminal Services. For more information about installing the applications running on your cluster, see the documentation that accompanies your application.

  3. Enable monitoring and health checking on the first cluster host.

    A Microsoft Operations Manager (MOM) Management Pack exists for Network Load Balancing. When your organization uses MOM to monitor and manage the servers within your organization, include the MOM Management Pack for Network Load Balancing on the cluster hosts.

    For location of additional information about monitoring and health checking the applications and services running on the cluster, review the resources in "Additional Resources for Deploying Network Load Balancing" later in this chapter.

  4. Verify that the first Network Load Balancing cluster host responds to client queries by directing requests to the cluster IP address.

    Test the first cluster host by specifying the cluster IP address or a virtual cluster IP address in the client software that is used to access the application or service running on the cluster. For example, a client accessing an IIS application would put the cluster IP address or virtual cluster IP address in the Web browser address line.

Important

  • Create an entry in DNS for the cluster only after you have completed the deployment of the entire cluster. Prematurely publishing the applications and services in DNS might result in overwhelming the cluster hosts before all cluster hosts are installed