Configuring IIS 7 in Windows Server 2008 R2

IIS 7.0 is the Web server role in Windows Server® 2008 and the Web server in Windows Vista®. IIS 7.5 is the Web server role in Windows Server® 2008 R2 and the Web server in Windows® 7. Windows Server 2008 R2 and Windows Server 2008 operating systems have all the IIS features needed to support the hosting of Web content in production environments. Windows 7 and Windows Vista also include IIS features, but the available features depend on the operating system versions.

The Web server was redesigned in IIS 7.0 to enable you to customize a server by adding or removing modules to meet your specific needs. Modules are individual features that the server uses to process requests. For example, IIS 7.0 and IIS 7.5 use authentication modules to authenticate client credentials and use cache modules to manage cache activity. Both versions of IIS also provide:

  • A new management interface. The interface lets you quickly and easily change the settings for each Web site. It is also possible to edit the settings of a Web site in a text-based configuration file.
  • The ability to share tasks with Web site owners. A hoster with multiple sites can delegate administrative control to developers or content owners.

New in IIS 7.5

IIS 7.0 and IIS 7.5 are together known as IIS 7 or IIS 7 and above; however, IIS 7.5 and Windows Server 2008 R2 include several new features not found in IIS 7.0:

  • Microsoft® ASP.NET runs on Windows Server 2008 R2 Server Core installations.
  • Some of the extensions available to be added to the IIS 7.0 platform are integrated into the IIS 7.5 platform, including:
    • FTP publishing.
    • Web-based Distributed Authoring and Versioning (WebDAV) publishing.
    • Windows PowerShell™ snap-in for IIS.
    • IIS Administration Pack modules.
  • IIS 7.5 includes configuration logging and tracing (IIS 7.0 does not include any built-in tracing mechanisms for configuration changes).
  • IIS 7.5 includes the Best Practice Analyzer, an automated tool for helping to ensure compliance with security best practices.

Leave a Reply

Your email address will not be published. Required fields are marked *