Perform a last node rolling upgrade from Windows 2000

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

To perform a last node rolling upgrade from Windows 2000

  1. Confirm that your systems are running Windows 2000.

  2. Confirm that your hardware is designed for or is compatible with Windows Server 2003, Enterprise Edition, or Windows Server 2003, Datacenter Edition. For more information, see "Checklist: Preparation for upgrading a cluster" in Related Topics.

  3. Using the information in "Resource behavior during rolling upgrades" in Related Topics, identify the resources in your cluster that are not supported by Windows Server 2003 and remove those resources.

  4. Again using the information in "Resource behavior during rolling upgrades" in Related Topics, identify the resources in your cluster that are not supported during rolling upgrades and are not covered by other technology specific upgrade procedures listed in Related Topics.

  5. Move all of the resources identified in the previous step to a single node by double clicking the Groups folder in Cluster Administrator's console tree. Click the group that contains the resource and then in the File menu, click Move Group.

  6. Upgrade the operating system on each of the nodes that is not hosting the resources moved in the previous step. After you upgrade each node, close Manage Your Server if it is displayed.

  7. Move all of the resources that you moved in the earlier steps from the node that has not been upgraded to one of the newly upgraded nodes.

  8. Once all of the resources have been moved, upgrade the final node. After you upgrade, close the Manage Your Server dialog box if it is displayed.

Notes

  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.

  • After you upgrade a cluster node from Windows 2000, you must log on with an account that is a member of both the Domain Admins group and the Administrators group on each cluster node before you can restart the Cluster service. This step is required even if the Domain Admins group is already a member of the Administrators group on each cluster node.

  • It is not mandatory to move all of the resources to a single node and upgrade that node last. However, following the procedure as described will typically give you the highest availability of the resources that do not support rolling upgrades.

  • If minor problems occur when you are performing a rolling upgrade, we recommend that you complete the upgrade. This might correct the problems.

  • tok:changequorumlater1

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Concepts

Alternatives to rolling upgrades
Checklist: Preparation for upgrading a cluster
How rolling upgrades work
Perform a rolling upgrade from Windows 2000
Resource behavior during rolling upgrades
Upgrade from Windows 2000 on a cluster containing IIS without using the provided script