BillS IIS Blog : Samples & Demos

How to Script / Automate IIS7 Configuration (without writing code)

bills — Mon, 02 Jun 2008 00:58:00 GMT

I hear this question a lot in the http://forums.iis.net/, and thanks to Carlos and team's rocking Configuration Editor, figuring this out on your own is a breeze. Here is how you can generate code for ANY IIS7 configuration change, without writing a line yourself.

1) download the IIS7 Administration Pack. What, you don't have it already? You're really missing out on some fantastic tools, including the Configuration Editor. Learn more about the admin pack here http://learn.iis.net/page.aspx/401/using-the-administration-pack/ You can download x86 and x64 from http://www.iis.net/downloads.

2) open "IIS Manager" and click on the "Configuration Editor" feature under the "Management" category:

3) Find the configuration section(s) you want to edit using the drop-down combo box, in this case isapiFilters:

4) use the configuration editor to make your change. In this case, I'm editing a collection, which pops up a collection editor where I can add items to the isapiFilter list by clicking 'add' in the task pane.

5) once you're done making any configuration updates, click on the 'Generate Script' task in the main Config Editor window:

6) the script generator creates three ways of automating the configuration change you just made C#, JavaScript (again the AHAdmin COM interface) and AppCmd.exe

7) Copy and Paste these changes into your own script / code and whoila, you've got sample code for making any IIS7 configuration change.

You may also want to read up on the IIS7 Administration APIs. You can find a lot more information here:

Using Scripts to Automate Management

Managing IIS with the IIS 7.0 PowerShell Provider

Free IIS7 Online Training

bills — Mon, 10 Sep 2007 16:36:00 GMT

A few months ago the IIS team did a quick tour of Europe, speaking in various cities and countries in an all-day IIS conference specifically geared toward training people on IIS7. Luckily, the good people of Poland decided to record and publish the training for everyone to use. Check out the sessions below to watch Brett Hill and Isaac Roybal present IIS7. Here is a list of all the sessions: http://www.microsoft.com/emea/itsshowtime/result_search.aspx?event=69&x=13&y=2

IIS 7 Web Server Platform- Windows Server “Longhorn”

Microsoft’s Next Generation Web Server: What’s New in IIS 7 for IT Pros

Isaac Roybal, Product Manager, Windows Server, Microsoft Corporation

This overview session will highlight the key points of interests for IT Pros in Internet Information Services version 7. IIS7 modularity increases security by allowing a reduced installation footprint and creation of specialized, streamlined servers. Application Pools are now “sandboxed” by default. You’ll see how IIS7 eases administration with a new IIS Manage UI, delegated administration, and new tools for automating administrative tasks. Applications run more reliably as they are easier to troubleshoot with built in tracing and diagnostics. Finally, multiple servers can use a single configuration file with the shared configuration feature for web farms.

IIS7 Administration: The New IIS Manager

Brett Hill, IIS Sr. Technical Evangelist, Microsoft Corporation

IIS7 Administration centers around the new task-oriented IIS Manager. This redesigned administration tool has many major new capabilities including the ability to delegate features, edit .NET configuration and has significantly improved performance when managing many sites. The IIS Manager itself is an extensible, modular application that administrators can customize and developers can extend. In this presentation we’ll explore how use and control the IIS Manager with a special focus on Delegated Administration. In addition, we’ll explore how to use Granular Locking to fine tune your delegated settings beyond those available in the UI.

IIS7 Administration: Shared Configuration, Remote Control, and Automated Tools

Isaac Roybal, Product Manager, Windows Server, Microsoft Corporation

For web farms, IIS7 has a powerful new feature – Shared Configuration. This allows you to configure multiple servers to share a single configuration file. The benefits are clear - all web servers have identical configuration so there’s no need to do configuration replication.

In addition, IIS Manager has built in remote administration capabilities. Using https between the IIS Manager and the remote server, this feature includes the ability to define trusted users in IIS Manager and have identities securely stored in the IIS configuration, Windows SAM or AD, or a .NET provider.

Of course, many organizations need to automate administration tasks. APPCMD is the new powerful, general purpose command line utility for controlling configuration, state for site and pools, and querying status. WMI has been improved specifically for IIS management, and there’s a new managed code API Microsoft.Web.Adminsitrationis that makes it easy for developers use .NET to write IIS management tools. PowerShell can use the managed API or WMI, giving you a superior command line and scripting environment for managing your servers.

IIS 7 Security: Less Exposure, Greater Control

Brett Hill, IIS Sr. Technical Evangelist, Microsoft Corporation

IIS7 security improvements can be found in many areas. In addition to the ability to control the server footprint, security is improved with the new URLFiltering and URLAuthorization capabilities. Also, you can now use Forms authentication with any content while leveraging .NET role and membership providers. In addition, there are key changes in the user principles and groups used by IIS7 that will make the server both easier to manage and more secure. Finally, application pool sandboxing helps to improve the security boundary between application pools.

IIS 7 Troubleshooting: Failed Request Tracing

Isaac Roybal, Product Manager, Windows Server, Microsoft Corporation

One of the most exciting features in IIS 7 for administrators is the new built-in failed request tracing capabilities. You can configure IIS 7 to automatically create a detailed trace log of events that occurred in the request processing pipeline when specific error codes are seen and/or if a request takes more than N seconds to complete. This is configurable at the server, site, application, or file level, and can be configured in the UI or with a command line tool. The resulting trace log is ideal for identifying bottlenecks. Like everything in IIS 7, it is extensible and can be customized with new events.

MIX '07: IIS7 for Developers Demos and Powerpoint

bills — Wed, 02 May 2007 07:00:00 GMT

I got a lot of requests for the presentation and demo notes from my session at MIX, so here goes. If you're interested in the slides, You can download the PPT here.

If you want to try the SQL Logging Module, I've also attached my wwwroot directory in the state it was in at the end of the demo (working), which includes the sqlLogging_schema.xml file you'll need to copy to the \windows\system32\inetsrv\config\schema directory. You'll also need to create your log table using the createDB.sql file. For a complete step-by-step walkthrough, see this post.

All the credit for the SQL logging module demo goes to CarlosAg. Without his work, you would have had to see my photo DirListModule again. :)

If you're interested in the PHP demos, you should check out this previous post, which includes videos (at the bottom) of the PHP related demos. I'll write-up a separate post on step-by-step instructions soon.

thanks, I hope you enjoyed the talk!

Building an IIS7 SQL Logging Module with .NET

bills — Tue, 01 May 2007 20:59:00 GMT

All the credit for the SQL logging module demo goes to CarlosAg. He built it for an internal Microsoft conference, and I stole it for my MIX talk. It is a great demo because it shows off something you can only do with IIS7 and the integrated pipeline. I love it!

You'll want to prepare for this demo by doing the following:

Download and install Visual Studio Web Developer Express
Download and install SQL Server Express (as part of the previous install)
Download and install the SQL Server Management Studio Express

Make sure you're running on Vista with IIS7 installed (including ASP.NET or at least .NET extensibility).

To start with, let's build a simple module with hard coded connection string. First, let's create the database. Open SQL Server Management Studio, and run the following script as 'sa'. (you'll want to enable the sa account first to make this work, and you may need to edit the physical path below to one that exists on your machine)

USE [master]
GO
/****** Object: Database [techready]    Script Date: 02/03/2007 12:16:42 ******/
CREATE DATABASE [MIX] ON PRIMARY
( NAME = N'mix', FileName='x:\mix.mdf' )
GO
USE [MIX]
GO
/****** Object: Table [dbo].[Log]    Script Date: 02/03/2007 12:18:13 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[Log](
    [Date] [datetime],
    [Method] [varchar](50) NULL,
    [IPAddress] [varchar](50) NULL,
    [Url] [varchar](50) NULL,
    [UserName] [varchar](255) NULL,
    [UserAgent] [varchar](255) NULL,
    [ResponseCode] [varchar](50) NULL,
    [SiteName] [varchar](50) NULL,
    [ApplicationName] [varchar](50) NULL
) ON [PRIMARY]

GO
SET ANSI_PADDING OFF

Once the database has been created, we can create a module to connect to it. Create an App_Code directory in your Web site / application, and drop in your first sqlLoggingModule.cs code (you'll want to replace billsiis7demo with the name of your machine):

using System;
using System.Data;
using System.Web;
using System.Web.Security;
using System.Data.SqlClient;
using System.Web.Hosting;

public class SqlLoggingModule : IHttpModule
{
public SqlLoggingModule()
{

}

    public void Dispose()
    {
    }

    public void Init(HttpApplication context)
    {
        context.LogRequest += new EventHandler(context_LogRequest);
    }

    void context_LogRequest(object sender, EventArgs e)
    {
      HttpApplication application = (HttpApplication)sender;
      LogRequest(application.Context);
    }

    private void LogRequest(HttpContext httpContext)
    {
      string connectionString = "server=billsiis7demo\\sqlexpress;database=MIX;uid=sa;pwd=sa";

//on Beta 3 and beyond
//httpContext.Response.DisableKernelCache();

using (SqlConnection connection = new SqlConnection(connectionString)) {

        SqlCommand cmd = connection.CreateCommand();
        cmd.CommandText =
            "insert into Log (Date, Method, IPAddress, Url, UserName, UserAgent, ResponseCode, SiteName, ApplicationName) values" +
                          "(@Date, @Method, @IPAddress, @Url, @UserName, @UserAgent, @ResponseCode, @SiteName, @ApplicationName)";

        cmd.Parameters.AddWithValue("@Date", DateTime.Now);
        cmd.Parameters.AddWithValue("@Method", httpContext.Request.HttpMethod);
        cmd.Parameters.AddWithValue("@IPAddress", httpContext.Request.UserHostAddress);
        cmd.Parameters.AddWithValue("@Url", httpContext.Request.Url.ToString());
        cmd.Parameters.AddWithValue("@UserName", httpContext.Request.ServerVariables["LOGON_USER"]);
        cmd.Parameters.AddWithValue("@UserAgent", httpContext.Request.UserAgent);
        cmd.Parameters.AddWithValue("@ResponseCode", httpContext.Response.StatusCode + "." + httpContext.Response.SubStatusCode);
        cmd.Parameters.AddWithValue("@SiteName", HostingEnvironment.SiteName);
        cmd.Parameters.AddWithValue("@ApplicationName", httpContext.Request.ApplicationPath);

        connection.Open();
        cmd.ExecuteNonQuery();
      }
    }

}

Note: since this logging module runs in user mode, kernel cached responses will not be logged. In Longhorn Server Beta 3 a new method DisableKernelCache() was added to allow modules to disable the kernel cache for these kind of scenarios. I've added the code above, but commented it out. Disabling the kernel cache may have a negative impact on performance. You would test this scenario before ever putting it onto a real server, right? :)

Pretty simple, eh? Before you can use it, you'll need to register it as a module with IIS. Go to the modules feature for this site / application, and click 'add managed module', or add the following configuration to your web.config file inside :

Request a page from your site, and look in the table to see the request logged. It should "just work" if all is well with the world.

Now let's add configuration extensibility. To do this, you'll want to create a new sqlLogging_schema.xml file that looks like this and drop it in the \windows\system32\inetsrv\config\schema directory:

Once you've done that, you'll need to register it in \windows\system32\inetsrv\config\applicationHost.config file. Add the section here under sectionGroup name=system.webServer like so:

Now you'll want to make a few changes to your module. First, you need to remove that horrible hard coded connection string, and add it to your web.config. Simple edit web.config and add it like this inside , replacing billsiis7demo with your machine name:

Now it's time to fix your module. First, let's replace the hard coded connection string with a GetConnectionString(httpContext) method. It looks like this:

private string GetConnectionString(HttpContext httpContext)
{
ConfigurationSection section = WebConfigurationManager.GetSection("system.webServer/sqlLogging");
return (string)section["connectionString"];
}

Don't forget to add using Microsoft.Web.Administration; in your .cs file (you may need to add reference to \windows\system32\inetsrv\Microsoft.Web.Administration.dll first). Now you can not only use Microsoft.Web.Administration to read/write to your new configuration section - just like GetConnectionString(httpContext) does above, but you can use appcmd.exe (our command-line tool) and VB/JScript using COM. Here are some examples:

Using AppCmd:
==to get configuration:
C:\windows\system32\inetsrv\appcmd.exe list config "Default Web Site" /section:sqlLogging

==to set configuration:
C:\windows\system32\inetsrv\appcmd.exe set config "Default Web Site" /section:sqlLoggingconnectionString:"server=billsiis7demo\sqlexpress;database=MIX;uid=sa;pwd=sa"

==vbScript to get configuration:
Dim adminManager, section
Set adminManager = WScript.Createobject("Microsoft.ApplicationHost.AdminManager")
Set section = adminManager.GetAdminSection("system.webServer/sqlLogging", "MACHINE/WEBROOT/APPHOST/Default Web Site")
WScript.Echo(section.Properties.Item("connectionString").Value)

And there you have it! A sql logging module that was built using .NET with 66 lines of code and an IIS7 configuration section that is scriptable, programmatically accessible, and usable from the cmd-line. Hope this help!

IIS7 at Microsoft Technology Summit

bills — Wed, 28 Mar 2007 14:50:00 GMT

Carlos and I spoke at the Microsoft Technology Summit yesterday, a conference dedicated to influential influencers who are experts in alternative platforms. It was a really fun talk as we were able to show off how IIS7 provides a very extensive public extensibility model for adding, removing and replacing any IIS7 feature, on top of which the IIS team built the IIS product itself.

I showed off the new IIS7 modular architecture, and the more than 40 components that can be added or removed independently. Carlos showed off how to build a SQL logging module in 40 lines of code using .NET extensibility, which was really impressive. I showed off the traditional DirListModule demo, and how easy it is to xcopy deploy a new managed module as part of your site that can replace the built-in IIS directory listing module.

While we were on the topic of modularity, I announced the new FastCGI module for IIS, which we were excited to announce will now be included in Longhorn Server and Vista SP1. I demonstrated how using it can double performance of the QDig application and as part of that demo I also showed off the dynamic output cache can provide blazing fast kernel mode caching of PHP content. I also demo'd the use of ASP.NET forms authentication for the PHP app, which unfortunately due to my configuration error, didn't work the first time (though I fixed it while Carlos went on with the next demo and showed them later that it did in fact work once I stopped fat-fingering config. :)).

Carlos then went on to show how easy it is to extend IIS7 configuration, including simple XML-based section extensibility and encryption support. He was then able to use the built-in command line, scripting, and .NET APIs to read and write to his custom configuration section (in this case, a connection string for his SQL Logging module) which was really powerful.

Last, Carlos showed off the admin tool, and how powerful the UI extensibility story is for IIS. This is an area I'm always completely blown away by, everytime I see Carlos demo it. He showed off 4-5 modules he has built that demonstrate nativagation tree extensibility, action pane extensibility, feature extensibility with some really compelling features including the IIS Reports module, and the Most Recently Used module (which comes with source).

The response so far has been very positive. Channy Yun wrote up his thoughts on the PHP on IIS7 demo, including a youtube video of it in action. Travis Swicegood also appreciated the improved PHP support. Ben Galbraith wrote up an extensive write-up of the entire presentation and summarized with my favorite quote so far:

I walked away fairly impressed with this one. Who doesn’t love Apache, but IIS7 seems to trump it pretty handily in both configurability, manageability, and extensibility

I couldn't have said it better myself. :)

IIS7 Logging UI for Vista - Download Now

bills — Tue, 30 Jan 2007 07:33:00 GMT

It's no secret that there is no way to configure logging settings in IIS7/Vista. A PM convinced me that configuring "logging" settings on a "Developer" machine simply isn't interesting - and "if they want to do it, they can always use config".

But, I have two pieces of good news for those seeking the logging UI.

First: it will reappear in SP1. It was already in "Longhorn Server", but for various reasons I won't elaborate on was removed from Vista. Now that we've heard your feedback, it will magically reappear when you install Vista SP1, as soon as it is available. As I said, it has always been in Longhorn Server, so look for it there too with the upcoming Beta 3 release. (I'm VERY excited about this, and when it is released, I think you will be too, when you hear what we've been up to. :))

Second: for those who don't want to wait, Tobin just posted a module to the DownloadCENTER which provides basic UI for log settings. Thanks to the completely extensible admin tool we've built with IIS7, he used the same APIs the Dev team did to build the original feature, and plugged in his own version. It is pretty darn sweet. Check it out here: http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1328

Thanks Tobin!

bill

Image Gallery - DirListModule Available for Download

bills — Mon, 29 Jan 2007 06:19:00 GMT

By popular demand, in conjunction with the DownloadCENTER release, I decided to release the famous DirListModule I originally created for IIS7 demos, several years ago. In fact, I think it was the first real managed module that anyone on the team had built, and it has been used in hundreds of demos ever since, including BobMu's keynote at PDC in 2005.

What does it do? It is pretty simple - it is a module/handler combo that can turn any directory full of images on your site into an image gallery, without any code. You can easily customize the look and feel by tweaking the themes/ HTML and stylesheets. It does all the dynamic thumbnails, image resizing, previewing, and caching for you. It even has a few configuration tweaks you can play with.

Get it here: http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1325

And leave me lots of good reviews and ratings. ;)

PS, if you're looking for sample source, and how to do this, I recommend you check out Mike's blog.

PHP on IIS7 w/FastCGI

bills — Tue, 31 Oct 2006 15:31:00 GMT

I'm attending ZendCon today and giving a demo in the keynote presentation by Andi Gutmans, one of the creators of PHP, and co-founder of Zend. I'm psyched to show off IIS7 and PHP along-side Andi!

I only have 5 mins to demo, so I decided to focus the demo on two things: 1) how easy it is to get PHP up and running and 2) the early results of our collaboration on performance for PHP on Windows.

Demo Preparation

Throughout the demo I'll be using Qdig, a simple, but powerful image gallery application. Setup of Qdig is really easy. To use the thumbnails and image resize features of Qdig, make sure you've enabled the GD library in your php.ini file. Download the zip file, unzip it to C:\inetpub\qdig, grab some of your favorite images and place them in a subdirectory, then - as described in the install.txt file - allow IUSR and NetworkService full control of the qdig-files directory, browse to the site once, then re-set permissions back to read/execute.

Part of this demo is measuring the performance gains we've made. To simulate load on the application, I'll be using an application called 'WCat', short for Web Capacity Analysis tool. It is a VERY powerful tool, and we'll only be scratching the surface of what it can do. The version of WCat that I'm using is in the IIS6 resource kit. There are some cool tools in there, and while they haven't been tested on IIS7, most of them do work. Once you've downloaded the resource kit, and installed it, proceed to the next step.

I've setup a simple wcat script to test my QDig performance. You can download the zip file with .bat and configuration scripts here. Unzip to C:\demo\performance and check out the contents. ThomaD gave me these a while back, and I've been tweaking them ever since. startStress.bat will launch both the controller, and the client, which will pound the URLs found in php_script.cfg for about 10 seconds. You'll see a quick summary of the results after the test has run.

I wanted to do something useful with Windows Sidebar during the demo, so I created my very first gadget last weekend, which you can download from the Gadget Gallery site. It launches perfmon, or any other configured path (I configure mine to launch my c:\demo\performance\perfmon.msc file, which has the get requests/sec perf counter).

Installing PHP on IIS7

The first part of the demo follows the steps of my previous blog post, and is really straight forward. The steps are described in this post titled: How to install PHP on IIS7 (RC1). Once I've got PHP installed, I run my performance test using that fancy gadget and get the following results:

PHP.net download performance using ISAPI (fast, but unreliable) - (full size image)

As you can see, I'm getting a little over 60 requests per second. This is about as fast as PHP can go today, using the community distribution of PHP from http://www.php.net/. ISAPI runs PHP inside the IIS worker process on multiple threads, making it similar to ASP or ASP.NET. Unfortunately, since some PHP extensions aren't yet threadsafe, running it in this way usually leads to crashes.

Installing IIS7' FastCGI module & PHP

As a result of the collaboration between Microsoft and Zend, there is now a faster and more reliable way to run PHP. The first step is to download the new IIS FastCGI feature, available as a Technical Preview release on this page of the IIS.net site. Download and unzip it to c:\fastCGI.

The next step is to download PHP itself. You can, of course, use the IIS FastCGI feature with the community distribution of PHP which we downloaded for the first demo. If you want the latest PHP core engine performance enhancements from Zend, you can also download a Technical Preview here. This zip file contains a special build of PHP for this Technical Preview, and is for experimental use only. Please don't ask Zend for support. I unzipped my copy to C:\zendPHP.

I should also mention that if you want to try Zend's Core product, which contains Zend's fastCGI implementation as well as some other cool features and tools, you can download from Zend. Zend's products are eligible for full support, and are truly Enterprise-class software. We plan to work with Zend in the future to enable Microsoft's FastCGI feature to integrate closer with Zend's products.

Once you've unpacked both the fastCGI module, as well as the PHP distribution you're ready to use, run the fastCGI installer like this:

Install FastCGI and register PHP handler (full size image)

Now that you've got the FAST version of CGI installed, and the handler re-mapped, run our performance benchmark again and see the results (shown side-by-side the previous run for comparison):

FastCGI performance rocking! (full size image)

Wow! Despite the fact that Microsoft and Zend just started working together, the results look very, very good. The FastCGI + Zend PHP numbers for Qdig, on my laptop, are almost twice what I get from today's PHP. And don't forget, Zend has committed to submit the performance enhancements back to the PHP community, so they will be showing up soon in the usual PHP.net distributions.

In addition to the great performance, the FastCGI method of running PHP should be significantly more stable than the ISAPI method. This is because with FastCGI, PHP is still running single-threaded in one or more processes in the FastCGI pool.

IIS Kernel Mode Caching for PHP applications

Of course, this is just the start for PHP developers. Once they're on Windows and IIS7, there are a ton of cool features to begin taking advantage of like distributed configuration, a sexy new admin tool for IIS configuration, diagnostic tools like failed request tracing, .NET integration (think ASP.net forms auth for a PHP app!) and more - all of which are unique to IIS7. One of the cool things that I wanted to show off, while we're talking about performance, is the new output cache.

The IIS7 output cache is a new feature in IIS7 which makes it possible to cache entire responses in memory - even from dynamic content. Unlike the existing caches IIS has, it is a 'smart' cache, enabling you to configure it to cache separate copies of responses for the same page (like index.php) based on query string value, so it works great for the Qdig application we've been using. One of the other really cool things about it is the fact that it is integrated with the http.sys (kernel mode driver) cache, allowing for blazing fast performance. Output caching is going to be a very powerful feature for all kinds of applications, from PHP to ColdFusion, Classic ASP to CGI. It will work with any content type, and can significantly speed up performance for applications where the underlying data doesn't change (like our image gallery), or where the changes occur at a predictable rate (so you can timeout the cache at the expected interval). Even in cases where the data is changing, say, once a second, it may make great sense to use the output cache with an expiration of 1 second. This allows for the dynamic processing to occur only once a second, instead of on every request, significantly speeding up response times and lowering CPU.

To configure output caching for QDig's index.php page, we first need to "unlock" the <caching> configuration section. Open \windows\system32\inetsrv\config\applicationhost.config file and search for <caching>. Cut it from it's current location, then search for (<location path="" - without parenthesis) and paste the caching configuration section in below it like this:

The point here is to move it under the section of applicationhost.config that is marked as overrideMode="Allow", which enables it to be set at the application level.

Now that you've unlocked it, create a web.config in your QDig directory, and paste in the following configuration:

Now that you've got kernel caching configured, run the performance test again. Before you do that, you may want to change the scale of your perfmon chart from (0..100) to (0.8,000). :) Here is what I get with kernel caching enabled:

Kernel Mode Caching PHP responses @ 6000 requests per second! (full size image)

To be honest, I'd expect it to be even faster. It would normally be in the 10s of thousands. The main reason it isn't is that I'm running the client and server on the same box, and any client generating 6000 RPS is going to use quite a bit of CPU, limiting the time slice kernel has to use. But going from 100+ RPS to 6000RPS isn't to shabby, eh?

One of the cool things in Vista is a new command line tool that will show you what is in the http.sys cache. Run "netsh http show cache" to get a snapshot:

NetSh cmd-line tool showing http.sys cache (full size image)

Summary

IIS' new FastCGI feature is going to be a huge benefit for web application frameworks like PHP which expect single-threaded environments. It lets them run fast and reliably on Windows, and begin take advantage of all the cool features of IIS. Using it, along with Zend's PHP enhancements in this demo almost doubled QDig performance on my machine, and made it much more stable.

To make sure anyone can take advantage of FastCGI on all of our existing platforms, we've built an ISAPI version of it that can run on Windows XP and Windows 2003 (IIS 5.1 and IIS 6.0) as well as a new module version for IIS 7.0. Check out the IIS FastCGI page for more information.

Technorati Profile