Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Upgrade from Windows 2000 on a cluster containing IIS without 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 without using the provided script

  1. Confirm that your hardware is designed for or is compatible with Windows Server 2003, Enterprise Edition, or Windows Server 2003, Datacenter Edition.

  2. 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 nonrolling 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.

  3. 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.

  4. On the Windows 2000 node, note the dependencies of the IIS instance resource. Note resources that depend on the IIS resource and also note what resources IIS itself is dependent on.

  5. Take the group containing the IIS instance resource offline For more information on how to do this see "Take a resource offline" in Related Topics.

  6. Remove any dependencies on the IIS instance resource.

  7. Delete the IIS instance resource.

  8. Move the group to a node running Windows Server 2003 and create a Generic Script resource by following the procedure documented in "Checklist: Creating a clustered IIS Web or FTP service" in Related Topics.

    Notes

    • As part of this step, recreate the dependencies of the Generic Script resource identical to those of the now deleted IIS resource. Make everything that was dependent on the IIS resource dependent instead on the Generic Script resource. Also make the Generic Script resource dependent on everything that IIS was dependent on.

    • 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.

  9. Start the W3SVC service on this node and set the service to start automatically.

  10. Bring the group containing the new Generic Script resource online.

  11. Using IIS, start the Web site on the upgraded node.

  12. Upgrade the final node to Windows Server 2003. Once the upgrade is complete, start the W3SVC on this node and set the service to start automatically.

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.

  • To cluster IIS on Windows Server 2003, you must have a DTC resource on that cluster as well.

  • 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.

  • Many of these steps can be automated using a script provided with Windows Server 2003. For more information, see "Upgrade from Windows 2000 on a cluster containing IIS using the provided script" in Related Topics.

  • tok:changequorumlater1

  • 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.

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.