Cluster Node Windows build number does not match first node
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2009-09-15
The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine the core version of the Microsoft Windows® operating system running on each node in the cluster:
If the Exchange Server Analyzer finds the value for BuildNumber on the second or subsequent node in the Exchange cluster different from the value for BuildNumber on the first node in the Exchange cluster, an error is displayed.
If an Exchange cluster is running across disparate versions of Windows, failover may not occur as expected or configured. In a mixed vintage Windows environment, failover will only occur from an earlier operating system to a later operating system (for example, from Windows 2000 Advanced Server to Windows Server™ 2003, Enterprise Edition). It will not occur from a later operating system to an earlier operating system (for example, from Windows Server 2003 to Windows 2000 Server).
To resolve this problem, you must upgrade all nodes to the same operating system and service pack. To minimize downtime, you can perform a rolling upgrade of your cluster.
To correct this error
Review the article, "Windows 2000 Clustering: Performing a rolling upgrade" (http://go.microsoft.com/fwlink/?linkid=1718).
Perform a rolling upgrade of each node whose BuildNumber value is not the same as the first node in the cluster.
For information about alternative procedures, see "Alternatives to Rolling Upgrades" (http://go.microsoft.com/fwlink/?LinkId=41363).