Microsoft KB Archive/813555

= New Resource Types Are Only Available on Windows Server 2003 Nodes in Mixed-Version Clusters =

Article ID: 813555

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition

-





SYMPTOMS
When you perform a rolling upgrade, there is no warning that the new resource types cannot be failed over to other, non-upgraded nodes. For example, when you perform a rolling upgrade from Microsoft Windows 2000 to Windows Server 2003 and do not upgrade all the nodes in the cluster, any new resource types that are created on the new node are not available for the non-upgraded (down-level) nodes.



CAUSE
This behavior occurs because new resource types cannot failover on to down-level nodes.



MORE INFORMATION
Microsoft does not support or recommend that you change the cluster configuration while you run a mixed-version cluster. Do not try to create new resources of the type that are only available on up-level Windows Server 2003-based nodes.

Operation of New Resource Types in Mixed-Version Clusters
The operation of a mixed-version cluster is complicated if a resource type that you add to the cluster is supported in one version of the operating system but not the other. For example, the Cluster service in Windows Server 2003, Enterprise Edition supports the Generic Script resource type. However, older versions of the Cluster service do not support it. A mixed-version cluster can run a Generic Script resource on a node that runs Windows Server 2003, Enterprise Edition, but not on a node that runs Windows 2000.

Cluster Service Sets the Possible Owners of Resource Types
The Cluster service transparently sets the possible owners of new resource types to prevent these resources from failing over to a Windows 2000 node of a mixed-version cluster. When you view the possible owners of a new resource type, a Windows 2000 node will not be in the list, and you will not be able to add this node to the list. If you create such a resource during the mixed-version phase of a rolling upgrade, the resource groups that contain those resources will not fail over to a Windows 2000 node. For more information about mixed-version clusters and rolling upgrades, see the following topics in Windows Server 2003 Getting Started Help:
 * &quot;Operation of new resource types in mixed-version clusters&quot;
 * &quot;Resource behavior during rolling upgrades&quot;

Keywords: kbprb KB813555

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.