Besides the standard IIS Status code you can find in this KB. You will find the follow new status codes been introduce with IIS 7.
New -
404.4 - File or directory not found: No module handler is registered to handle the request.
404.5 - URL sequence denied. The specified URL sequence is not accepted by the server.
404.6 - HTTP verb denied. The specified HTTP verb is not accepted by the server.
404.7 - File extension denied. The specified file extension of the resource is not accepted by the server.
404.8 - URL namespace hidden. The namespace of the specified URL is hidden by configuration.
404.9 - File attribute hidden. The requested file has a hidden attribute which prevents it from being served.
404.10 - Request header too long. One of the request headers is longer than the specified limit configured in the server.
404.11 - URL is double-escaped. This URL is denied because it is susceptible to double-escaping attacks.
404.12 - URL has high bit characters. This URL is denied because it has high-bit characters.
404.13 - Content-Length too large. This URL is denied because the Content-Length set is longer than specified by configuration.
404.14 - URL too long. This URL is denied because its length is longer than specified by configuration.
404.15 - Query-String too long. This URL is denied because its Query-String is longer than specified by configuration.
As you may noticed, lot of new 404 entries. 404.13/.14 replaced the 413/414 status codes and re-category under 404.
500.14 - Server error: Invalid application configuration on the server.
500.17 - Server error: URL authorization store cannot be found.
500.19 - Server error: Data for this file is configured improperly in the configuration store.
Removed -
403.20 - Passport logon failed. This error code is specific to IIS 6.0.
As Passport Login support has been removed from IIS 7.0
Duplicate -
405 - HTTP verb used to access this page is not allowed.
Not sure what's the difference with 404.6 :)
Unknown -
401.6 - Unauthorized: URL authorization scope was not found on the server.
401.7 – Access denied by URL authorization policy on the Web server. This error code is specific to IIS 6.0
407 - Proxy authentication required.
410 - File has been removed.
415 – Unsupported media type.
500.11 - Server shutting down
500.12 - Application is busy restarting on the Web server
Not sure if these still supported...
Let me know if you found any new status code...
922427 Error messages that are related to the component that maps ABO interface calls to the configuration system in IIS 7.0 are logged in the %Windir%\System32\Abomapper.log file
926378 When you change the Global.asa file, an ASP Web application that is running on an IIS 6.0 Web server does not restart automatically
926377 Error message when you try to view an ASP page in an Internet Information Services (IIS) 6.0 Web site: "http/1.0 500 Server Error"
I was suprised to read the IIS 7.0 KB on ABO - thought it was the first one :) but further searching shows that there are at least two more IIS 7.0 KBs.
926939 Error message when you request an ASP page that connects to an Access database in IIS 7.0: "Microsoft JET Database Engine error '80004005'"
927672 Server activation fails when you use a SOAP WSDL moniker to activate a COM+ SOAP-enabled server on a computer that is running Windows Vista
The JET error is pretty common FAQ in www.iis.net, while the COM+ issue is related to new security enhancement (request filtering).
Hehe :) Not just me! You have got the power as well.... to manage IIS via PowerShell. Honestly, I'm not a big fan of coding, gave that out many years ago - coz my logical thinking cell somehow resides at right brain. For now, I preferred ready made tools to help me. Prior to version 6, I can't live without adsutil.vbs, with 6.0 - I love all the built-in vbs scripts as well. E.g. iisapp.vbs, iiscnfg.vbs, etc. For IIS 7.0, it will be the appcmd.exe - the new command line tool.
With the recent released of PowerShell, you have got more POWER to manage IIS. I'm happy with the appcmd.exe. If you power hunger - first read the intro here, then if you familiar with WMI, try your own cmd-lets via WMI provider, and the latest show cases - Tobin demostrates another powerful force with Microsoft.Web.Administration component dll. From loading it into the shell to extending its power. Zzzz.. at this point I'm actually abit lost with it :) d*mn complicated! LOL! maybe it just me.