Server Clusters: Cluster Configuration Best Practices for Windows Server 2003
This document describes several recommended cluster configurations, or topologies, among the many that are possible for Microsoft© Windows? Server 2003. Each configuration is accompanied by a discussion of the relative advantages and disadvantages for various models of application deployment. Source: Microsoft TechNet

The Features of the Local Quorum Resource on Windows Server 2003 Clusters
Microsoft Knowledge Base Article: 283715 - This article discusses the features of the local quorum resource on Windows Server 2003-based clusters

Support WebCast: Windows Server 2003 Clustering: New Features
This Support WebCast will discuss the new features of the server cluster technologies (formerly Microsoft Cluster Service or MSCS) that are included in Windows Server 2003 and Windows Server 2003, Enterprise Edition

Network Load Balancing : Configuration Best Practices for Windows 2000 and Windows Server 2003
This document provides Network Load Balancing requirements and best practices for Microsoft© Windows? 2000 and Windows Server 2003. Requirements must hold for the NLB cluster to function correctly. Best practices are suggestions based on deployment feedback and issues seen in the field. Source: Microsoft TechNet

Network Load Balancing: Frequently Asked Questions for Windows 2000 and Windows Server 2003
This white paper presents and answers the frequently asked questions about network load balancing. Source: Microsoft TechNet

Network Load Balancing : Security Best Practices for Windows 2000 and Windows Server 2003
This document describes the security-related best practices for the Network Load Balancing (NLB), providing guidelines and best practices for Microsoft^© Windows^? 2000 Server Family and the Windows Server 2003 Family. Source: Microsoft TechNet

Using ClusDiag for enhanced Windows server cluster reporting
Learn to use ClusDiag, Microsoft's free tool for Windows server cluster management, to capture logs and view server cluster reports. (July 2008)

Take control of server clusters with Microsoft's ClusDiag tool
Microsoft's Cluster Diagnostics tool is a great utility for managing Windows server clusters. Learn the basics of ClusDiag, as well as installation tips to get you started. (June 2008)

Microsoft tool simplifies Windows server cluster configuration
Cluster configuration manager, commonly called ClusPrep, is a free Microsoft tool for determining if servers are properly configured to support clustering. (February 2008)

Validating Windows server clusters with ClusPrep
Microsoft designed the final steps in its server cluster configuration wizard to ensure that server clusters are set up correctly and functioning properly. (February 2008)

How to Back Up and Restore a Windows Server 2003 Cluster
This article describes how to use the Backup tool in Windows Server 2003 to perform seamless backup and restore operations of the local cluster database

How to Change the Cluster Service Account Password
Microsoft Knowledge Base Article: 305813 - In Windows Clustering for Windows Server 2003, you can change the Cluster service account password on the domain as well as on each local node without having to take the cluster offline

How to Configure Client-Side Caching on a Server Cluster
Microsoft Knowledge Base Article: 285369 - This article describes how to configure client-side caching on a server cluster

How to Configure Windows Clustering Groups for Hot Spare Support
296799 - This article describes the ability of Windows Server 2003 to configure Windows Clustering for hot spare support

How to Configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 Cluster
Microsoft Knowledge Base Article: 301600 - This article describes how to install the Microsoft Distributed Transaction Coordinator (MSDTC) resource on a Windows Server 2003 cluster.

How to Perform a Rolling Upgrade of Windows Server 2003 Server Clusters
Microsoft Knowledge Base Article: 811272 - When a node joins an existing server cluster, the cluster service performs a version check to make sure that the node that is joining has a version of the operating system that is compatible with the rest of the cluster nodes. The check makes sure that only validated and supported configurations run in a mixed-version environment during a rolling upgrade. The checks are based on major operating system versions such as Windows NT4 and Windows 2000. The rules that the cluster service implements do not cover upgrades from release candidate to release candidate.

How to Replace a Disk That Is on a Windows 2000 or a Windows 2003 Server Cluster
Microsoft Knowledge Base Article: 305793 - This article discusses how to replace a shared hard disk that is on a Microsoft Windows Server 2003 or a Windows 2000 server cluster.

How to Set Up a Clustered Print Server
278455 - This article describes how to set up a clustered print server

How to Uninstall the Cluster Service on a Windows Server 2003 Cluster
Microsoft Knowledge Base Article: 282227 - This article describes how to remove the Cluster service on a Windows Server 2003-based cluster

How to Upgrade a Microsoft Windows NT 4.0 Cluster to a Windows Server 2003 Cluster
Microsoft Knowledge Base Article: 301538 - This article describes how to upgrade a Windows NT Server, Enterprise Edition 4.0 server cluster to a Windows Server 2003 Enterprise Server cluster. Because there is a two version difference between Windows NT 4.0 and Windows Server 2003 in the Cluster service, a rolling upgrade is not supported. This means that the server cluster will be unavailable for client access during the upgrade to Windows Server 2003.

Windows Clustering and Geographically Separate Sites
Microsoft Knowledge Base Article: 280743 - Geographically dispersed (majority node set) server clusters are built on a networking and storage infrastructure with characteristics that are very different from a standard quorum device server cluster.

How to Troubleshoot the Cluster Service Account When It Modifies Computer Objects
307532 - This article describes how to troubleshoot the Cluster service when it creates or modifies a computer object in Active Directory for a server cluster (virtual server). about computer objects with regard to the Cluster service

How to Troubleshoot Printing Issues on a Windows Server 2003 Cluster
Microsoft Knowledge Base Article: 302539 - This article describes how to troubleshoot printing issues that are specific to Windows Server 2003-based server clusters. Printers, drivers, and printer settings operate in the same manner whether the print queue is on a server cluster or a stand-alone server. You can use the same procedure to troubleshoot these issues, with the exception of the location where some of the information about the printers is configured and stored. This article describes the architecture and some common troubleshooting steps that you can use to troubleshoot printers on a server cluster.

Failover Behavior on Clusters of Three or More Nodes
299631 -This article documents the logic by which groups fail from one node to another when there are 3 or more cluster node members. The movement of a group can be caused by an administrator who manually moves a group or by a node or resource failure

Incorrect Microsoft Cluster Service Quorum Root Path May Cause Cluster to Stop Responding (Hang)
Microsoft Knowledge Base Article: 283370 - If you type the incorrect path for the Root Path to be used for Quorum logging, this can cause the Microsoft Cluster Server (MSCS) to stop responding (hang).

Cluster Configuration Wizard May Not Detect Network
Microsoft Knowledge Base Article: 297807 - When you configure a cluster, the Cluster Configuration Wizard may generate the following error message: Find Matching Network The subnet mask could not be supplied automatically for this IP address

Cluster Network Name Does Not Come Online After You Upgrade to Windows Server 2003
Microsoft Knowledge Base Article: 311799 - Cluster resources that use a cryptographic provider from a third-party provider do not come online in a mixed-version cluster after you upgrade to Windows Server 2003 or after the nodes are upgraded.