Upgrade from Windows 2000 on a cluster containing Message Queuing

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

To upgrade from Windows 2000 on a cluster containing Message Queuing

Confirm that your hardware is designed for or is compatible with Windows Server 2003, Enterprise Edition, or Windows Server 2003, Datacenter Edition.
Take all of the Message Queuing cluster resources offline. For more information on how to do this see "Take a resource offline" in Related Topics.
For each Message Queuing resource, take the Network Name resource that depends on it offline also.
Upgrade all of the nodes from Windows 2000 to Windows Server 2003. You can perform either a rolling upgrade, or a non-rolling upgrade, whichever is appropriate for your installation. Prior to upgrading, be sure to remove the resources that are not supported by Windows Server 2003. For more information, see Related Topics. Manage Your Server will appear when you initially log on to the newly upgraded node as an Administrator. Close Manage Your Server to continue with the upgrade.
Bring the Network Name resources back online. Ensure that the Distributed Transaction Coordinator (DTC) resource is online, then bring the Message Queuing resources online.

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.
tok:changequorumlater1

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.