Normally I don’t spend a lot of time blogging on MP updates… unless they are a really big deal, but since the MP catalog is not working as well with the conversion to Pinpoint, I will be blogging on these until it gets fixed: at least until we add back sort by date and a search that only shows new MP’s.
I am also including some recommendations at the bottom of this post for modifying the IIS MP’s.
2/8/2010 – Updated IIS management pack to support monitoring Windows Server 2008 SP2 and Windows Server 2008 R2, version 6.0.7600.0
Note – the version of the 2000, 2003, and core Library has also been updated from the previous MP – so make sure you get them all:
Also – interesting to note – there is NO GUIDE in the MSI anymore…. you need to download it as well.
Some points from the guide:
Note: In this guide, the term “Internet Information Services 7” applies equally to IIS 7.0 (which shipped with Windows Server 2008, Windows Server 2008 SP1, and Windows Server 2008 SP2), and IIS 7.5 (which shipped with Windows Server 2008 R2).
What’s New – Microsoft has updated the Management Pack for Internet Information Services 7 to support Windows Server 2008 SP2 and IIS 7.5 on Windows Server 2008 R2.
There is a section in the guide that is incorrect (outdated):
For Operations Manager agents that manage IIS 7 servers with more than 400 sites and application pools, you must override the Health Service Private Bytes Threshold monitor that is targeted to the Health Service. Override the Agent Performance Monitor Type—Threshold parameter to set it to 209715200 (the number of bytes=200 MB). If you do not override this threshold monitor, the agent might consume more than 100 MB of memory and be restarted automatically.
This entire section should be ignored…. because as long as you are running the most current core MP’s – the default value has been changed from 100 to 300MB. If you followed the guide here – and set this to 200MB – you’d be going in the wrong direction. Instead – just make sure you have the latest core MP updates documented HERE.
The IIS MP’s are one of the leading causes of CONFIG CHURN. I recommend setting ALL discoveries in these MP’s to run once per DAY (or less frequent). Once per day is 86,400 seconds.
The MP team obviously has taken note of this, because in this version of the MP – the discoveries for 2008 OS were all changed from 3600 seconds to 14,400 seconds, this change is not documented in the guide. However, this is not enough change to the frequency in most large environments with substantial numbers of IIS being monitored.
You can load the following discoveries up in your console – by creating a scope of:
- IIS 2000 Server Role
- IIS 2003 Server Role
- IIS 7.0 Server Role
- IIS 7.0 Web Site
- IIS 7.0 Application Pool