There is a new web-whitepaper on how to provide a secure hosting envirionment using IIS 7.0, written by "Vikas Malhotra ".  There's some very interesting information there.  Especially the provisioning portion.  Now that I've vested so much time on providing a "better" .NET API for IIS 6.0 tasks (Provware: http://agramont.net/r.ashx?3), I'm wondering if I should just jump in on IIS 7 and provide some tools, web UI, and get a head start there or keep banging out stuff for IIS 6 (comments are very welcome).

Anyhow, here is a link to the article:  http://www.iis.net/1143/SinglePageArticle.ashx

 Overall the article is a nice initial overview, but there is still much work to be done on best practices.  With IIS 7, it's no longer just about ASP.NET.  What I mean by that is today with Windows Server 2000/2003, it's all about getting access to ASP.NET.  Now with IIS7, there is more of a platform for web developers to offer even cooler features that integrate with the web server itself.  So how does the hoster offer those "override" services to customer/developers?  What components shouldn't the hoster allow developers to remove, override, or utilize?  What performance issues will that have and will it crash other customers if there is an issue? 

In looking at some of the latest builds from IIS 7, there are some great answers there (I need time to formulate my responses to my own questions----I know, I suck), but these still need to be addressed.  Not only that, they'll need to be automated in a Web UI, Command Line, Web Service, or whatever mechanism an Admin or automation system needs to kick that off.

I hope to have some more IIS 7 content (including videos) coming soon (If MS lets me).