Hi All: I have a server running 64-bit standard sp1 with about 6 websites. On one of the websites I had added "index.php" to the default documents, where it showed up in ISM as a "local" entry.
Then the developer decided they wanted index.php added to all the sites. Rather than add it on a site-by-site basis, I just added it to the server's root config by clicking on the server name in ISM and changing the default document there.
This caused the first website to stop functioning (throwing 500 errors), which I didn't realize for some time. When I tried to check the default document on the first website in ISM, I received an error that there was a conflict in the web.config (preventing any changes from being made), which eventually led me to this technote:
http://support.microsoft.com/default.aspx/kb/949349
And I was able to fix it by first removing the "global" index.php default document setting, then removing the "local" setting, then re-enabling the global setting. Fortunately it was only two websites that had the "local" setting.
It seems strange to me that ISM will "allow" me to make changes that will completely break a website. Just like you can't add the same virtual hostname for two websites without getting an error, I would expect some type of error checking, or at least an alert message, that would have prevented me from performing an action that will break a configuration elsewhere?
Is there any type of utility that will check a server for configuration errors or conflicts like this?