Geeks With Blogs

News This content is my own and does not necessarily represent the views or opinions of Rockwell Collins.
Eric Johnson's Blog IT Architect - My ramblings on work, technology, & life in general

A while back I attended a Microsoft internal briefing moderated by Eric Deily.  This was a very informative presentation and I am grateful to Jeff Brand for getting me involved with the call.   Here is an overview of some of things discussed during the presentation.  Sorry about the delay in posting this information, but I just got my blog and have a lot of back blogging to do. :)


Rich, Unified Configuration System

Brand New administration tool with delegated admin support

Componentized, Extensible Web Core

Improved Integrate Health Monitoring & Diagnostics Features



  • Machine admins could delegate control of setting to application owners
  • Can FTP all app configuration onto a web server
  • Store IIS, ASP.NET + Indigo setting in the same file
  • Uses app.config in conjunction with web.config


Admin Tool

  • More task oriented rather than property page hell
  • Manage everything in one consistent way
    • IIS and ASP.NET integrate together instead of isolated tabs
    • Security set in one place instead of four
  • Use the admin tool for remote hosting scenarios
    • Enable delegated management on a per-site/per-app basis
    • Use HTTP as the wire protocol, manage through proxies/firewalls
    • Admin tool user should not require any admin account on remote server
  • Use the admin tool to easily manage 1000’s of sites
  • Called the “Web Management” Tool
  • Looks like My Computer or Control panel in Windows XP
  • Uses IE style navigation
  • Search for sites to limit the site listing.
  • Group sites by various values (ports, started, stopped)
  • Add sties to favorites to have them show up you the start tab
  • Configuration IIS settings in the web.config




      <roleManager enabled=”true” /> favorites to have them show up you the start tabonfig within <system.web>.



                        <add value=”index.html” />



<directoryBrowse enabled=”true” />







  • Can build modules that extend the web server
    • Add new authentication/authorization schemes
    • Replace directory browsing or logging of the server
  • Build modules using native or managed APIs
    • The module APIs make building modules easy and fast
    • The managed API == the shipping IHttpModule interace in ASP.NET today
  • Functionality + features were integrated across IIS/ASP.NET
    • Existing ASP.NET modules should be applied to non-ASP.NET content
    • Example: forms authentication and role management for static content
    • Help to migrate applications to ASP.NET slower over time.
  • I could find hundreds of modules built by the community
    • Rich ecosystem of modules that I can easily leverage
  • Could customize server workload + reduce its attack surface
    • Install only those modules that you want or need.
  • Can add modules in the web.config
  • On a per applications control what modules your site loads/responds to.  This allows you to create a very secure website.  Even enache cannot ules your site loads/responds to.  This allows you to create a very secure website.
  • Apache 2.0 cannot do this without running multiple instances of Apache.


Most Secure IIS configuration Example: (Only returns a 200 OK response)


      <clear />



  • Sample use for a managed module is to create an gallery like view for directory listings of images
    • Simplay add the module, type and its handeler into the web.config.
Posted on Friday, June 10, 2005 8:02 PM Product Reviews | Back to top

Comments on this post: IIS 7.0

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Eric Johnson | Powered by: