Mohammed Atef’s Technical blog

IIS 7.0 Configuration Settings

Dears, today i am going to talk about IIS 7.0 configuration and delegate IIS 7.0 Configuration. i think all of you know that IIS 6.0 settings control hosted in the metabase but now IIS 7.0 has
changed the configuration storage from the metabase to a series of cleartext XML files. These files provide for a distributed hierarchy in which the configuration is shared among the machine-level configuration files and may optionally be set at the directory level along with the web content. This allows the system administrator to delegate control to the site or application administrators.

By default, IIS 7.0 is locked down to allow only the system administrator access to modify the server, site, or application settings.
As with most systems, the configuration files in IIS 7.0 are read and applied in a hierarchical order. The following three files are at the heart of the system:

  • The applicationHost.config file.
  • The machine.config file.
  • The root web.config file.

The applicationHost.config file is located at %systemroot%\system32\inetsrv\config. The
machine.config and root web.config files are both currently located in the %systemroot%\
Microsoft.NET\Framework\v2.0.50727\CONFIG folder. The applicationHost.config file contains the IIS server settings. The machine.config and root web.config files contain the global default values for the .NET Framework settings. Along with the three primary files, additional web.config files may be located in the content directories of individual web sites or applications to control their behavior.
The configuration file inheritance hierarchy begins with the machine.config file then the root web.config, the applicationHost.config file, and then the web.config files that may be in the web-site or application can understand configuration hierarchy throw the following diagram.


IIS 7.0 give users two types of administration One is for the server administrator
using IIS Manager to control access for the site administrator. The other is for the site administrator doing what they have been granted to do. Now Administrators can decide what can or can not be override for Site Administrators.
The Feature Delegation tool allows you to lock or unlock sections for examples include Error
Handling, Compression, Authentication, and many others as shown in below image.

Within the Feature Delegation tool, you can change the Delegation setting, depending on the following list(Read/Write, Read Only, Not Delegated, Reset to Inherited, Configuration , Read/Write, Configuration Read Only).
In our new IIS 7.0 Administration window you will find two types for feature delegation one we have seen before the feature delegation and another is custom site delegation which found in the top right side in your IIS 7.0 Manager from this form you can define you web site settings by override the global IIS 7.0 setting manually.

Hope this help.


July 26, 2009 - Posted by | .Net 2010 | , ,


  1. Great idea, but will this work over the long run?

    Comment by Martin-Kaas | August 21, 2009 | Reply

  2. I think So

    Comment by mohammedatef83 | August 23, 2009 | Reply

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: