I now have 4 clients on Windows 2008 Server and IIS7 and in each case there have been problems getting ColdFusion 8 and IIS7 playing nicely together.  The issue is the web server connector and if anything is weak in ColdFusion, the web server connector certainly stands in line for first prize, in my opinion.  So here are some of the quirks I have seen with CF8 and IIS7.

HTML displays fine before connecting CF and IIS after connecting simple HTML throws a 500 error.

HTML displays fine when first hitting a web site yet clicking on a single HTML link throws a 500 error.

During the running of the connector to connect IIS and CF we get "Unknown Error".  Close out and try again and it works.

Creating a Virtual Directory in IIS7 creates a re-direct under the covers causing a recursive loop.

Sometimes the ISAPI relationships are created other times they have to be added manually.

Even when the ISAPI relationships are created run-state are not correct-sufficient.

These are actual occurrences that clients have gone through.  So I ask myself, what could be wrong with using Apache on Windows in production?  One big advantage would be that those with Unix systems with Apache would have a common set of underlying configuration-set up files and there would be no need to add third-party Apache emulators such as ISAPI re-writes.  Does anyone have any thoughts or opinions on using Apache on Windows in production?