Partager via


Edit a Managed Module (IIS 7)

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

You might have to change some of the settings for a managed module. For example, the module might need a different managed type.

Note

The Modules page lists both managed and native modules used by a site or an application. This list might be a subset of all native and managed modules present on the Web server.

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 Managed Modules Feature Requirements (IIS 7).

Exceptions to feature requirements

  • None

To edit a managed 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, select the managed module that you want to change in the Modules list.

  4. In the Actions pane, click Edit.

  5. On the Edit Managed Module dialog box, edit the information that you want to change and then click OK.

Command Line

To edit a managed module at the server level, use the following syntax:

**appcmd set module /name:**string **/type:**string **/preCondition:**string

The variable namestring is the name of the managed module that you want to edit at the server level. The variable typestring is managed type for the module. Optionally, specify a condition or conditions under which the module will run by including the variable preConditionstring. For example, to change a managed module named FormsAuthentication to have a precondition to run only for requests to managed content, type the following at the command prompt, and then press ENTER:

appcmd set module /name:FormsAuthentication /preCondition:managedHandler

When you want to edit a managed module for a specific site or application, include the virtual path of the site's root application or to an application in a site by specifying a value for the app.name attribute. For example, to edit the same managed module as in the previous example for the Default Web Site, type the following at the command prompt, and then press ENTER:

appcmd set module /name:FormsAuthentication /preCondition:managedHandler /app.name:"Default Web Site/"

Note

When you want to edit 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:

  • ModulesSection class (IIS)

  • HttpModulesSection class (ASP.NET)

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 Managed Modules (IIS 7)
Configuring Modules in IIS 7