IIS7 has been re-engineered from the ground up.  The new web server boasts of several areas of improvement including the following:

• Modularity
• Extensibility
• Configuration
• Administrative Tools
• Diagnostics

Modularity

In previous web servers, the functionality was more or less built into the install.  However, in IIS7.0 functionality have been spawned as modules.  Essentially, there are more than 40 components (more can be developed) that can be turned on or off as needed.  The result is a modular web server where administrators can selectively turn on or off components to reduce the footprint and optimize the performance of a server.

Extensibility

The modular design of IIS 7, as hinted above, can be further extended by using the new API's.  ASP.Net integration in IIS7 enables custom modules to be developed using ASP.Net and the .Net Framework. Developers can utilize the extensibility to do things like add value for existing applications (Custom Auth Schemes, state management, and etc)

Configuration

IIS has evolved over the different versions when speaking of configuration.  IIS5 has the bindery store, IIS6 had an XML based Metabase and now IIS7 has a distributed XML based configuration.

These are the configuration files:

1. Machine.config (.NET Framework Global Settings for the Machine)
2. Root Web.config (Global ASP.NET settings)
3. applicationHost.config (Global Configuration)
4. site
   1. web.config
   2. application web.config
   3. directory web.config

Administrative Tools

The admin tools have been completely rewritten. 

• The IIS manager is a new console that provides GUI management for IIS7 and ASP.NET. 
• A new command line tool, Appcmd.exe!
• Microsoft.Web.Administration --- managed API
• WMI Provider
• (Powershell too)

In addition to the tools, administrators can delegate administrative functions to other users in a secure matter

Diagnostics

IIS 7 includes a new Runtime State and Control API (RSCA) that provides a wealth of information about application pools, worker processes, sites, application domains, and running requests. Information from the RSCA can be aquired through the new IIS7 WMI, Microsoft.Web.Administration API, commandline, and IIS manager.

Failed Request Tracing provides  detailed trace events allowing you to trace a request as it makes its way though IIS.  [This is known as FREB]

This chapter in the book was designed as an overview.  Later in the resource kit we will dive deeper.

I am working my way through the IIS7 Resource Kit and thought it best to blog about each of the sections.  Essentially, I am taking notes from the book in blog form.  Although my notes are paraphrases from the text, I wanted to make sure I give credit to the authors of the Resource Kit which I recommend highly!

Bibliography Reference

Volodarsky, M.; Londer, O.; Hill, B.; Cheah, B.; Schofield, S.; Mares, C. A.; Meyer, K. (2008). Internet Information Services (IIS) 7.0. Redmond, Washington. Microsoft Press.

Internet Information Services. Retrieved May 2008, from http://www.iis.net.