Article ID: 328360 - Last Review: December 3, 2007 - Revision: 7.7

How to enable and disable ISAPI extensions and CGI applications in IIS 6.0

View products that this article applies to.

This article was previously published under Q328360

SUMMARY

This step-by-step article describes how to enable and disable Internet Server Application Programming Interface (ISAPI) extensions and Common Gateway Interface (CGI) applications in Internet Information Services (IIS) 6.0.

By using the Iisext.vbs command line script, which is located in the Sysvol\System32 (default is Windows\System32) directory, a server administrator can enable and disable files that are specified in the Web Service Extension Restriction List (WebSvcExtRestrictionList). These files can be either ISAPI extensions or CGI applications.

Note Before you can enable or disable a Web service extension, you must add it to the Web Service Extension Restriction List. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

328419 (http://support.microsoft.com/kb/328419/ ) How to add and remove Web service extension files in IIS 6.0

The syntax to enable Web service extension files is as follows:

IisExt /EnFile Drive:\Path\FileName [/s Computer [/u [Domain\]User/p Password]]

The syntax to disable Web service extension files is as follows:

IisExt /RmFile Drive:\Path\FileName [/s Computer [/u [Domain\]User [/p Password]]]

Back to the top

Enable Web service extension files

This section describes how to enable Web service extensions. For detailed information about the switches that are used in the examples, see the Parameters section of this article.

Enable Web service extension files on a local server

Note For this example, the Web service extension file is Test.exe.

To enable Web service extension files on a local server, change to the Sysvol\System32 folder (the default is Windows\System32) at a command prompt, and then type the following:

iisext /EnFile c:\Source\Test.exe

You receive the following response:

Connecting to server ...Done.
Enabling extension file complete.

Enable Web service extension files on a remote server

Note For this example, the Web service extension file is Test.dll.

To enable Web service extension files on a remote server, change to the Sysvol\System32 folder (the default is Windows\System32) at a command prompt, and then type the following:

iisext /EnFile c:\Source\Test.dll /s ComputerName /u Domain\User /p Password

You receive the following response:

Connecting to server ...Done.
Enabling extension file complete.

Back to the top

Disable Web service extension files

This section describes how to disable Web service extensions. For detailed information about the switches that are used in the examples, see the Parameters section of this article.

Disable Web service extension files on a local server

Note For this example, the Web service extension file is Test.exe.

To disable Web service extension files on a local server, change to the Sysvol\System32 folder (the default is Windows\System32) at a command prompt, and then type the following:

iisext /DisFile c:\Source\Test.exe

You receive the following response:

Connecting to server ...Done.
Disabling extension file complete.

Disable Web service extension files on a remote server

Note For this example, the Web service extension file is Test.dll.

To disable Web service extension files on a remote server, change to the Sysvol\System32 folder (the default is Windows\System32) at a command prompt, and then type the following:

iisext /DisFile c:\Source\Test.dll /s ComputerName /u Domain\User /p Password

You receive the following response:

Connecting to server ...Done.
Disabling extension file complete.

Back to the top

Parameters

Drive:\Path\FileName: This parameter specifies the file name and path of the Web service extension file to be added.
/s Computer: This parameter specifies the network name or IP address of the remote computer. By default, if this parameter is not used, the script runs on the local computer.
/u Domain\User: This parameter specifies the user account that has administrative privileges on the remote computer and that will run the script. The script uses the locally logged on credentials if this option is not specified.
/p Password: This parameter specifies the password for the account that is used with the /u parameter. If the /s parameter is not used and a password is required, the user is prompted for the password, and the password is obscured.
/?: This parameter displays help at the command prompt.