OH MAN!!!!

I haven't been back to check these threads, because of the very problem you mentioned!!! I spent a whole day tracking this one down! I can't believe how little information there was on MSDN regarding that. It seems like it would be a big issue. Turns out that there is a second fix: .Net installs a utility (aspnet_regiis.exe; need to pass it -i) which does the same thing.

I can't believe a quick peak at the UT could have saved me all that headache! Thanks anyway. And I actually learned a lot about IIS going through this the hard way.

>
>Very important!
>
>After installing IIS, you have to run the repair utility to force .NET to re-configure IIS. Insert the Windows Component Update .NET CD and run the following from a command prompt:
>

><CD Drive>:\dotNetFramework\dotnetfx.exe /t:c:\temp /c:"msiexec.exe /fvecms c:\temp\netfx.msi"