New IIS7 MP ships – support for Server 2008 R2 and IIS 7.5

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.



***Pay attention:

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.


***Special note:

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







Comments (10)

  1. Anonymous says:

    Hi Kevin….Fits our situation exactly, hence why we don’t see this. Thx


  2. Anonymous says:

    Great information again! thx Kevin.

    John Bradshaw

  3. Kevin Holman says:

    Thanks Danilele…. good links.

    Still all workarounds.  The fact remains that most customers will go to the MP site – get pinpoint, and then not be able to find what they are looking for.

  4. Kevin Holman says:

    958661 is included in 2008 SP2.  Without SP2 OR this hotfix you WILL LEAK memory.

    957123 is an IIS module update.  It is required as stated… however, it is NOT required if you are running the OpsMgr SP1 rollup, which includes it (which we recommend/mandate for this MP.  It is also not required for OpsMgr R2.

    The guide is still correct on these…. it is letting you know what will happen if you dont have the minimum fixes in place.

  5. Anonymous says:

    It seems that some other info in the Guides may be incorrect……We do not have either of the following Hotfixes on our IIS7 servers, yet we have not experienced either of these issues. The bottom one even says that the servers will not be discovered, but they definitely are and they list all the Websites OK. Maybe this was fixed in CU1??

    "Ensure that you have installed hotfix KB958661 on all IIS 7 servers. Without this hotfix the Operations Manager 2007 agent leaks memory. For more information and to download this hotfix, see the article, “FIX: Small memory leaks may occur when you use RSCA to query runtime statistics in IIS 7.0,” at You can also download this hotfix from the download center at

    • Ensure that you have installed the hotfix discussed in the article KB957123 on all IIS 7 servers. Without this hotfix, you will see Event 4507 from the Health Service in the Operations Manager 2007 event log on servers where IIS 7 is installed, and discovery and monitoring of the IIS 7 servers will not work."

  6. Kevin, I am sure you are aware of the discussion about Pinpoint and the catalog going on

    and on

    I have even built an unsupported script frontend for the webservice catalog, as described on

    I do have an unsupported script

    one of the easiest "quick and dirty" solutions, anyway, is from Stefan:

    and the product team is now also using TWITTER to communicate MP Updates:

  7. Dominique says:

    Hello Kevin,

    As always it is on your site we have more informations than in the documentation …

    Any comments on the new Run As account??

    The RunAs account for the "Privileged Monitoring Account" is set by default to "Local System" which is part of the Local Administrators, isn’t it ?

    Page 9:


    Privileged Monitoring Run As profile, configured by default to use the Local System account. The following tables identify the management pack elements that are configured to use the Privileged Monitoring Run As profile. These management pack tasks cannot
    be run using a low-privilege account


    Is it this "These management pack tasks cannot be run using a low-privilege account" which is blocking the process? as the Local System used in the RunAs account is not sufficient anymore to proceed and I will need to add the svcMOMAction in the "Privileged
    Monitoring Run As profile" and also on all servers…????


    "This profile determines which credentials are used to test connectivity between tiered management groups. If no credentials are provided for a given system, then the Default Action Account is used."


    I am very confused between the two document OM2007_MP_IIS.doc and IIS 7 Management Pack Guide.doc joined on the link…/details.aspx

    I will need to create groups of IIS 7 Servers (or use the "IIS 7 Computer Group" or IIS 7 Server Role Instance group" ??? ) to use the svcMOMAction instead of the Local System… but I could not find this clearly define in the documentation except the comment
    "These management pack tasks cannot be run using a low-privilege account"… which group "IIS 7 Computer Group" or "IIS 7 Server Role Instance group" should be use in the "Priviledged Monitoring" Run As Profile? Both groups are available in the drop dwon list
    on the "Priviledged Monitoring" Run As Profile.

    Also the svcMOMAction defined as Action Account is not listed in the drop down on the "Priviledged Monitoring" Run As Profile????

    So I need to create a new account for this Monitoring?



  8. Hey Kevin, do I need to have IIS logging enabled for IIS 7 / 7.5 with the format set to W3C Extended Log File (the way it has to be configured for IIS 5 & IIS 6)?



  9. Anuj says:

    Hi Kevin,

    I want to import the below mentioned MOM packs, however i couldnt find the links to download them, please help me with the links for downloading the MOM packs.

    The packs are:




  10. Murad says:

    Kevin, any idea what non of my IIS 7.5 server roles/Website getting discovered?

Skip to main content