The IIS Manager in Internet Information Services 7.0 (IIS 7.0) has undergone many changes from its predecessors. The new IIS Manager was completely rebuilt using .NET’s Windows Form technology. With the overhaul, most of the features available in IIS 6.0 remain intact; however, accessing those features is a completely different experience. Microsoft has done away with the tab-based method of Web Server and Site management and replaced it with a categorized features view.
Along with the intuitive new user interface comes new functionality. IIS 7.0 introduces an additional layer of separation for managing complex web sites with applications. Applications behave just like virtual directories of a web site with the exception that an application also offers the ability to operate under its own application pool and permissions can be managed to control which users can administer the application.
Another impressive feature of the new IIS Manager is its seamless integration with ASP.NET. The new ASP.NET features allow administrators and developers to control several aspects of the server, site, application or virtual directory’s settings such as; compilation, providers, application settings, Forms authentication as well as several other developer orientated features.
The new IIS Manager makes it possible to perform almost any of the common tasks associated with administering a web server. A couple of things that are lacking in IIS 7.0 are the ability to administer web servers that use previous IIS versions or FTP sites. Installing the IIS 6.0 Management Tools can cover both of these things. This allows you to use both IIS 6.0 and 7.0’s IIS Manager on the same server should you need either of those abilities. If for any reason you still need more out of the IIS manager the fact that it was developed with managed .NET code allows for additional modules to be developed.
In order to access the IIS Manager with Windows Server 2008 you must have the Web Server Role installed. Only with the Web Server Role installed you can launch the IIS Manager using one of these methods:
When the IIS Manager is launched, you are presented with the Connections tree view for navigating servers and sites and the Start Page. The IIS Manager Start Page should be a familiar sight to developers. The layout and design of the Start Page is modeled after the Visual Studio 2005 editions Start Pages.

From the IIS Manager Start Page you are provided with links to recent connections, connection tasks and popular online resources for developers and administrators as well as the IIS news feed. The Start Page is the place to go for establishing new connections and getting help and info on web server administration and development.
When you connect to a server through the IIS Manager’s Start Page or Connections tree view you are brought to the server’s Home panel. From the server’s Home panel and every other area besides the Start Page the IIS Manager is split into three columns:

Each feature has its own user interface for managing the feature. When configuring a feature, changes are not applied until you click Apply on the Actions panel or save when prompted after leaving the feature. The new modular architecture used by the IIS Manager’s features decreases its footprint and increases security on the server by not requiring unused features to be installed. Whereas previous versions require unused features to be installed and loaded to memory and simply disables access to them in the user interface.

Below the features list view is a pair of toggle buttons used for switching between the features view and content view. The content view of a server connection provides the ability to add application pools and web sites or switch to their respective features views from the Actions column. If FTP services are installed on the server, FTP sites will also be listed and provide a features view with a link to launch the IIS 6.0 Manager to configure them.

To add a new application pool you must provide; the name, .NET Framework version to use, if any, and whether to use the integrated or classic managed pipeline module to the dialogue. The integrated managed pipeline mode runs request processing within the main IIS process, while classic runs them in a separate process designated for request processing.
To add a new web site you must provide; the name, application pool to run under, the path to the site’s directory on the server, the authentication credentials to use, binding type, IP address, port and host header used to connect to the site to the dialogue.
Application pools are used by IIS to provide a method of organizing processing configuration settings for web sites and applications. Each site or application must be set to run under one application pool, which could be used by multiple sites or applications.

The features view of a server’s application pools provides a list of application pools on the server that can be filtered and grouped. When an application pool is selected, the Actions column provides links for: starting and stopping, basic and advanced settings, recycling, renaming, removing and viewing the applications using the application pool.

An application pool’s Basic Settings dialogue has the same settings as the Add Application Pool dialogue; except for renaming, which is done from the Actions column of the Application Pools features view. The Advanced Settings dialogue allows you to configure the basic settings as well as settings for CPU usage, process model, rapid fail protection and recycling. Recycling can be configured with the Recycling Conditions dialogue as well. The recycling conditions allow you to specify how often the worker processes used by an application are automatically restarted.

When a site, application or virtual directory is selected from the Connections column its features view is displayed with nearly all the same features available to the server. From the action column you have access to explore the physical directory or edit its permissions, and edit the basic and advanced settings. Sites and Applications both provide the ability for viewing their virtual directories. Web Sites have links to: start, restart or stop the site, configure its bindings, connection limits, and view its applications.

The contents view of a site, application, or virtual directory lists their directories and files and allows you to navigate the site’s structure. Files can be viewed with a web browser and permissions can be edited from the contents view, but the IIS manager does not support editing the contents of the files themselves.
All the improvements to the functionality and usability of the IIS Manager are phenomenal. The intuitiveness and ease of use are sure to bring the already low overall cost of operating a web server down, making the “free” price tag of Microsoft’s competitors in the web server market a lot less appealing.
Learn how to setup and administer a web server with Train Signal’s Microsoft Windows IIS Web Server training for Windows Server 2000 and 2003
View the Microsoft Windows IIS Web Server training demo here!
Copyright © Train Signal Inc. All Rights Reserved.
Robert Says:
February 3rd, 2009 at 1:30 pm
Hello
I would like to know how can I use my IIS 7 for setting up a website – even extremely simple (one page only – one word – “TEST”, so it will be accessible over the WEB. I have configured folder permissions, the site is reachable by ping from remote computers and I get a message: Authorization — cannot verify access to path.. I know that I am not the only one that straggles with it as I have found complaints on the web about it and NO REAL hint how to solve the problem.
I wouold appreciate any info on the subject, as it is now the IIS is useless.
Alan Says:
February 16th, 2009 at 1:55 pm
I too would like to see the same. I have a website that was working well under IIS6.0, but I cannot seem to get it to work under IIS7.0.
I thought it would be a simple port, but no such luck.