You are currently offline, waiting for your internet to reconnect

The IIS Server Instance resource type does not appear in Cluster Administrator on a Windows Server 2003 server cluster

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

You cannot create a clustered Microsoft Internet Information Services (IIS) Web or FTP site on a Microsoft Windows Server 2003 server cluster. When you try to create an IIS Web or FTP site, the IIS Server Instance resource type does not appear in the list of available resources in the Cluster Administrator Microsoft Management Console (MMC) snap-in.

For example, if you right-click a group in the Cluster Administrator MMC snap-in, point to New, and then click Resource, the IIS Server Instance resource type does not appear in the Resource type list.
This behavior occurs because Windows Server 2003 uses a Generic Script resource type to manage a clustered IIS Web or FTP site.

In Windows Server 2003, the following two scripts are available to configure clustering for IIS:
  • For WWW services, Clusweb.vbs.
  • For FTP services, Clusftp.vbs.
Both these files are located in the Windows\System32\Inetsrv folder.
To resolve this issue, configure the clustered Web or FTP site by using the Generic Script resource type together with the appropriate Microsoft Visual Basic script. To do this, follow these steps:
  1. Start the Cluster Administrator tool, and then create a group, or use an existing group, to contain the following resources:
    • A Physical Disk resource.
    • An IP Address resource.
    • A Network Name resource.
    For additional information about how to create a resource in Windows Server 2003, see the "Create a new resource" topic in Cluster Administrator Help.
  2. Bring the IP Address resource and the Network Name resource online. To do this, right-click a resource, and then click Bring Online.
  3. Create a Web or FTP site that points to a folder on a shared hard disk by using the IIS Manager tool. Assign the same IP address that you configured for the IP Address resource to the Web or FTP site. For additional information about how to deploy IIS 6.0, see the Deploying Internet Information Services (IIS) 6.0 guide. To obtain this guide, visit the following Microsoft Web site:
  4. In the group where you created the resources in step 1, create a new Generic Script resource. Point this Generic Script resource to one of the following Visual Basic scripts, depending on the kind of site that you want to create:
    • %systemroot%\System32\Inetsrv\Clusweb.vbs
    • %systemroot%\System32\Inetsrv\Clusftp.vbs
    To do this, follow these steps:
    1. Start the Cluster Administrator MMC snap-in.
    2. Right-click the group that you used in step 1, point to New, and then click Resource.
    3. In the Name box, type a descriptive name for this resource, click Generic Script in the Resource type list, and then click Next.
    4. View the entries in the Possible owners list to make sure that the appropriate cluster nodes appear, and then click Next.
    5. In the Available resources list, click the IP Address resource, click Add->, and then click Next.
    6. In the Script filepath box, type the path of the script that you want to use. For example, to create a clustered Web site, type the following:
    7. Click Finish, and then click OK on the following message that appears:
      Cluster resource 'ResourceName' created successfully.
  5. Bring the Generic Script resource online. To do this, right-click the resource, and then click Bring Online.
  6. Test the connectivity to the clustered Web site. To do this, visit the Web site by using a Web browser program, such as Microsoft Internet Explorer.
In Microsoft Windows 2000, you can use the IISSYNC tool to synchronize the IIS configuration between cluster nodes. However, because of metabase changes in Windows Server 2003, IISSYNC is no longer included in Windows Server 2003. In Windows Server 2003, the content of the Windows 2000 Metabase.bin file is now found in the following two XML files:
In Windows Server 2003, you can use the Iiscnfg.vbs file to synchronize the metabases between the cluster nodes. To do this, run the following command:
%systemroot%\System32\cscript.exe iiscnfg.vbs /copy /ts destinationComputer /tu Account_to_connect_to_destinationComputer /tp Password_to_connect_to_destinationComputer
Note Make sure that the execution of scripts has not been disabled by a domain policy. Additionally, some antivirus programs may prevent these Visual Basic scripts from running.

If you want to migrate your IIS 5.0 Web server to IIS 6.0, you can use the IIS Migration tool. To obtain this tool, visit the following Microsoft Web site:This tool is also available in the IIS 6.0 Resource Kit Tools. To obtain the IIS 6.0 Resource Kit Tools, visit the following Microsoft Web site:Note If you try to create a Generic Service resource for a VBS script instead of a Generic Script for that script, you may receive the following error in the Cluster log. For example, you may receive this error if you try to create a Generic Service resource for one of the following VBS scripts:
  • Clusweb.vbs for WWW services
  • Clusftp.vbs for FTP services
00000c1c.000006b4::Date-Time ERR Generic Service <IIS>: Unable to read parameters from registry for Service '(null)' . Error: 13, property in error is 'ServiceName'
MSCS, clussvc, www, ftp,

Article ID: 887417 - Last Review: 10/30/2006 21:24:08 - Revision: 4.3

Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

  • kbclustering kbtshoot kbprb KB887417
');'ms.dqp0';m.content='true';document.getElementsByTagName('head')[0].appendChild(m);" onload="var m=document.createElement('meta');'ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src=""> ge.locale}}" href="" ng-click="setLanguage(language);" class="ng-binding" id="language-es-py">Paraguay - Español
Venezuela - Español
://">tion () { return Math.floor(Math.random() * 16).toString(16); })).replace("R", (8 | Math.floor(Math.random() * 3)).toString(16)); var m = document.createElement("meta"); m.content = guid; = "ms.dqid"; document.getElementsByTagName("head")[0].appendChild(m);