Enable a Registered Native Module for a Site or an Application (IIS 7)

Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

You might be required to enable a native module for a site or an application if the site or application requires the module's functionality. When you enable a native module for site or an application, you are associating a native module, which has already been registered at the server level, with a specific application that is running on the server.

Note

Before you can enable a native module, you must register the native module at the server level. For more information about registering native modules, see Register and Enable a Native Module on a Web server (IIS 7).

Prerequisites

For information about the levels at which you can perform this procedure, and the modules, handlers, and permissions that are required to perform this procedure, see Native Modules Feature Requirements (IIS 7).

Exceptions to feature requirements

  • None

To enable a native module

You can perform this procedure by using the user interface (UI), by running Appcmd.exe commands in a command-line window, by editing configuration files directly, or by writing WMI scripts.

User Interface

To use the UI

  1. Open IIS Manager and navigate to the level you want to manage. For information about opening IIS Manager, see Open IIS Manager (IIS 7). For information about navigating to locations in the UI, see Navigation in IIS Manager (IIS 7).

  2. In Features View, on the server, site, or applicationHome page, double-click Modules.

  3. On the Modules page, in the Actions pane, click Configure Native Modules.

  4. In the Configure Native Modules dialog box, select the check box for the native module that you want to enable and then click OK.

Command Line

To enable a native module for a site or an application, use the following syntax:

**appcmd add module /name:**string **/app.name:**string

The variable name string is the name of the module that you want to enable for your site or application. The variable app.name string is the virtual path of the site's root application or the virtual path of an application in a site for which you want to enable the module. For example, to enable a module named ImageCopyrightModule for the Default Web Site, type the following at the command prompt, and then press ENTER:

appcmd add module /name:ImageCopyrightModule /app.name:"Default Web Site/"

Note

When you want to enable a module for a site's root application, make sure that you include the "/" after the name of the site. In addition, if your site name has spaces, enclose the whole string in quotation marks.

For more information about Appcmd.exe, see Appcmd.exe (IIS 7).

Configuration

The procedure in this topic affects the following configuration elements:

<modules>

For more information about IIS 7 configuration, see IIS 7.0: IIS Settings Schema on MSDN.

WMI

Use the following WMI classes, methods, or properties to perform this procedure:

  • GlobalModulesSection class

For more information about WMI and IIS, see Windows Management Instrumentation (WMI) in IIS 7. For more information about the classes, methods, or properties associated with this procedure, see the IIS WMI Provider Reference on the MSDN site.

See Also

Concepts

Configuring Native Modules (IIS 7)
Configuring Modules in IIS 7