Upgrade from Windows 2000 on a cluster containing IIS using the provided script
Updated: January 21, 2005
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 IIS using the provided script
Confirm that your hardware is designed for or is compatible with Windows Server 2003, Enterprise Edition, or Windows Server 2003, Datacenter Edition.
Upgrade all nodes except the node containing the IIS instance resource 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.
If you do not already have a Distributed Transaction Coordinator (DTC) resource on the cluster that you are upgrading, create a DTC resource for this cluster on an upgraded node.
On an upgraded node, open Command Prompt and navigate to the %systemroot%\system32\inetsrv directory.
iis switch cluster name [group name]
The name of a physical node in the cluster that has been upgraded or the name of a virtual server.
This is optional. By default the script will upgrade all IIS Web and FTP resources in the cluster. However, if instead you want to upgrade only one particular group, you can specify the name of that resource group.
The resource group that includes the IIS resource must be on the Windows 2000 node when you run the script.
The script includes a step that will bring the resource group with the newly created Generic Script resource online. However the script will only bring the group online if all resources in the group were online before the script was run. If the group was only partially online or was offline prior to the script being run, the script will take the entire group offline and will not bring any resources back online after the upgrade.
Once the script completes, the newly created resource might immediately fail. This is because the W3SVC service is disabled. You can correct this problem by completing the following step.
Once the script completes, take the newly created Generic Script resource offline, then start the W3SVC service on this node and set the W3SVC to start automatically.
Bring the Generic Script resource online.
Using IIS, start the Web site on the upgraded node.
Upgrade the final node to Windows Server 2003. Once the upgrade completes, start the W3SVC service on this node and set the service to start automatically.
If appropriate, add the final upgraded node to the Possible Owners list for the newly created Generic Script resource. For more information, see "Specify which nodes can own a resource" in Related Topics.
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.
To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.
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.
To cluster IIS on Windows Server 2003, you must have a DTC resource on that cluster as well.
The script will not upgrade IIS resources that are in the cluster group. If you have IIS resources that are in the cluster group, you can instead use the procedure "To upgrade from Windows 2000 without using the provided script on a cluster that includes an IIS resource" in Related Topics.
Only upgraded nodes can be the owner of the Generic Script Resource created in this procedure because this resource type is not supported in Windows 2000.
If you prefer to not use the provided script and instead perform each step manually, see "Upgrade from Windows 2000 on a cluster containing IIS without using the provided script" in Related Topics.
For more information regarding hardware compatibility, see Support resources.
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.
ConceptsUpgrade from Windows 2000 on a cluster containing IIS without using the provided script
Take a resource offline
Specify which nodes can own a resource
Move a group to another node
Move a resource to another group
Bring a resource online
Modify resource dependencies
Delete a resource
Create a new resource
Checklist: Preparation for upgrading a cluster
Checklist: Creating a clustered IIS Web or FTP service
Start Setup on an x86-based computer
How rolling upgrades work
Restrictions on rolling upgrades
Resource behavior during rolling upgrades
Alternatives to rolling upgrades