http://blogs.msdn.com/klevereblog/archive/tags/IIS+Monitoring_2C00_+Reporting+and+Debugging/default.aspxTags: IIS Monitoring, Reporting and Debuggingen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/klevereblog/archive/2005/01/12/351555.aspxWed, 12 Jan 2005 20:35:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:351555klevereblog0http://blogs.msdn.com/klevereblog/comments/351555.aspxhttp://blogs.msdn.com/klevereblog/commentrss.aspx?PostID=351555http://blogs.msdn.com/klevereblog/rsscomments.aspx?PostID=351555<p>I spent a good part of the morning reading IIS documentation.&nbsp; Besides reading some docs on IIS 7 and some of the new features and improvments I also came across some other information regarding some best practices recommended by Brett Hill for setting up your IIS 6.0 web server, particulary if you are planning a migration from an early version of IIS.&nbsp; So I thought maybe there are some other steps that people may have taken or some gotchas.&nbsp; When I worked for Interland we were apart of the Windows 2003 Joint Developer Program.&nbsp; So we'd had IIS 6 for some time long before there was any documentation so we had to learn a lot of these things the hard way.</p> <p>&nbsp;</p> <p><a href="http://iisanswers.com/IIS6_tasks.htm">http://iisanswers.com/IIS6_tasks.htm</a></p><img src="http://blogs.msdn.com/aggbug.aspx?PostID=351555" width="1" height="1">IIS Monitoring, Reporting and Debugginghttp://blogs.msdn.com/klevereblog/archive/2005/01/06/347935.aspxFri, 07 Jan 2005 00:58:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:347935klevereblog6http://blogs.msdn.com/klevereblog/comments/347935.aspxhttp://blogs.msdn.com/klevereblog/commentrss.aspx?PostID=347935http://blogs.msdn.com/klevereblog/rsscomments.aspx?PostID=347935<p>In my experience with IIS I have noticed that there is room for improvment in regards to monitoring resources and isolating issues and resource problems.&nbsp; This is of particular concern within the a shared hosting solution when specific abusers need to be isolated and have action taken against them.&nbsp; Unlike many enteprise deployments shared hosting enviroments envolve several users and websites with a wide deployment of code types.&nbsp; Application development often ranges from novice to expert and it is very important that a hoster have the capability to distinguish bad code (i.e. memory leaks, loops) from potential attacks or traffic anomolies.&nbsp; Although their are tools for debuggin iis processes and applications it is often difficult to truly determine the true culprit, or if the system has reached it's limits.&nbsp; Also from a reporting and planning standpoint it would be useful to manage these resources more easily.&nbsp; A lot of trial an error is involved with capacity planning in the shared hosting world.&nbsp; Anytools that would allow hosters to make informed decisions on hardware specs, storage capacity, website usage would be a plus.&nbsp; Also i'd point out that although there are so great debugging solutions such as adplus, iis state, iismon these tools aren't always intuitve and easily configurable for system administrators.&nbsp; I want to know what peoples thoughts are on a troubleshooting tool that can pinpoint utilization issues in a shared hosting enviroment.&nbsp; Are there ways of leveraging the many technologies that are available in this enviroment (WSRM comes to mind).&nbsp; I'll stop babbling and just wait for others to chime in.</p> <p>&nbsp;</p> <p>***Disclaimer-This posting is provided "AS IS" with no warranties, and confers no rights.&nbsp; Use of included script samples are subject to the terms specified at <a href="http://www.microsoft.com/info/cpyright.htm">http://www.microsoft.com/info/cpyright.htm</a>. <br /></p><img src="http://blogs.msdn.com/aggbug.aspx?PostID=347935" width="1" height="1">IIS Monitoring, Reporting and Debugging