Today I wanted to learn on the new feature offered by IIS 7.0.I enquired around to check whether products and systems have migrated from IIS 6 to IIS 7 and people have migrated the existing IIS6 application to IIS7 in compatible model as IIS 7.0 is built to be compatible with previous releases of IIS. I then started reading more and plan to learn more of the following in the next few days. i am also planning to play with IIS 7.0 in Windows Server 2008.
A More Modular Web Server
With IIS 7.0, you can choose to completely remove or replace installed modules, including Microsoft built-in modules. You can disable modules at the server, site, or application level. This would lead to reduction in the amount of processing required to serve each request and reduce the potential attack surface of your server. IIS 7.0 is made up of more than 40 separate feature modules. Each feature module can be independently installed on the server and installing only required modules helps reduce administrative overhead.
Server Core Support
On Server Core machine, IIS can be administered locally via the IIS command-line utility AppCmd, or remotely by using WMI. Server Core does not support the .NET Framework, and hence IIS 7.0 Server Core installations cannot run ASP.NET applications. What will be used for? It will be used to install PHP and deploy websites base don PHP. Please note that Server Core installation does not include the Windows user interface and you must manually complete the configuration using the command-line tools
IIS 7.0 introduces a unified XML based configuration system. Server level settings are stored in applicationHost.config, including the settings for every site and application. The new configuration model is hierarchical and some settings defined in applicationHost.config can be overridden in web.config files at the site or application level (for example, default documents and directory browsing) and the capability to override can be controlled from applicationHost.config. It allows enables to delegate administration privileges to users and this enables site owners take control of administering their sites without requiring full admin rights to IIS .
Centralized Web Farm Management (Shared Configuration)
With IIS 7.0, you can copy your configuration onto a network share and point each instance of IIS 7.0 at the central configuration. When the configuration files change, each IIS 7.0 instance recycles only the affected parts of your system. Administrators need only update the central configuration file to update all of the hosted Web sites. In disaster recovery scenarios, this feature dramatically reduces an organization’s downtime and enhances high availability. When there are multiple Web servers running the same apps with the same configuration, a centralized configuration repository is ideal.
Remote Connection & Debugging Support
IIS 7.0 includes a new remote management service that uses HTTPS, and enables to manage your servers through firewalls all while using the same UI as if you were logged on locally to the box. IIS also provides command line tool called AppCmd.exe for performing basic tasks such as creating or modifying sites, listing current requests, or adding a module to a site. In addition PowerShell support for scripting options is supported. What excites me more is that there is a managed API support to administer and manage IIS 7.0 from C#.
IIS 7.0 helps administrators to monitor the activity of Web applications for specified error conditions and this feature can be enabled only for the Web sites that need it. When the defined condition occurs, tracing happens automatically
IIS 7.0 Media Pack
This is something that I do not plan to experiment much, but found very interesting. The IIS 7.0 Media Pack is targeted to help Web developers and content providers to offer audio and video media on their IIS Web servers. They also are expected to enable to manage delivery of multimedia content with IIS 7.0 management tools.