locked
IIS Management Pack Noise/False Discoveries RRS feed

  • Question

  • Hello, I am running Operations Manager 2012 SP1, with the latest versions of the IIS Management Pack.  I have noticed that the IIS management pack, by the way it is designed, will discover any system that simply has .NET Framework 3.5 installed (which would include all SQL Servers and many other things).  Since IIS gets discovered (falsely), it now tries to monitor services like the Web Management Service and the IIS Admin service.  However, since these services do not exist on this machine, SCOM will report them down.  I find that SCOM only actually reports the failure on an inconsistent basis (intermittent), typically after SCOM agent coming out of maintenance mode (but for whatever reason, doesn't happen every time).  Have other people seen this issue?  How are you dealing with it?  Getting dozens of false positive alerts is very annoying (because they are false reports, they only way to clear them is to reset them).  We had opened a Support Case with Microsoft, but really got no where before the case was closed by MS (best they would say its working as designed/design flaw); but its been this way for over a year, so it doesn't seem like MS has any plans to fix anything.  Anyone in the community have a suggestion for this problem?  Thanks!
    Thursday, March 28, 2013 2:53 PM

Answers

  • Hi

    This is know issue .... and it is indeed a design flaw. You'll also find the discovery "assumes" that an IIS Server will have IISAdmin and WMSvc installed which of course isn't always the case with Windows 2008 so you'll also get alerts from this.

    I create a group for the IIS Servers that don't have the service (or you don't want to monitor the service on) and then override the monitor for that group.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    • Marked as answer by bcehr Saturday, March 30, 2013 4:39 PM
    Friday, March 29, 2013 7:50 AM
  • I have put together a workaround for this. I have created two custom attributes in SCOM, one to search registry for existence for WMSvc and the other to search for IISAdmin.  I then created a Dynamic group to find systems that do not have service installed.  I then created overrides for the Web Management and IISAdmin monitors that disable the monitor for members of this group.  I scoped the attributes under classes in the IIS Management Pack.

    • Marked as answer by bcehr Tuesday, April 2, 2013 1:33 PM
    Tuesday, April 2, 2013 1:33 PM

All replies

  • Hi

    This is know issue .... and it is indeed a design flaw. You'll also find the discovery "assumes" that an IIS Server will have IISAdmin and WMSvc installed which of course isn't always the case with Windows 2008 so you'll also get alerts from this.

    I create a group for the IIS Servers that don't have the service (or you don't want to monitor the service on) and then override the monitor for that group.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    • Marked as answer by bcehr Saturday, March 30, 2013 4:39 PM
    Friday, March 29, 2013 7:50 AM
  • Graham, thanks for the reply and suggestion!  Do you know if MS has any plans to ever fix?  Or they planning to just leave it be?
    Friday, March 29, 2013 10:34 PM
  • I don't know of any plans to change this which is a shame - I have previously entered a feedback item for this and got the same answer as you got from PSS (it is "by design"). There is a roadmap of MP releases here:

    http://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx

    Sorry I can't be of more assistance.


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Saturday, March 30, 2013 12:48 PM
  • Thanks for info Graham. It really is a shame, you would think such a core MP would get more attention from the product team (especially being that fixing this really wouldn't be very hard).

    Saturday, March 30, 2013 4:38 PM
  • I have put together a workaround for this. I have created two custom attributes in SCOM, one to search registry for existence for WMSvc and the other to search for IISAdmin.  I then created a Dynamic group to find systems that do not have service installed.  I then created overrides for the Web Management and IISAdmin monitors that disable the monitor for members of this group.  I scoped the attributes under classes in the IIS Management Pack.

    • Marked as answer by bcehr Tuesday, April 2, 2013 1:33 PM
    Tuesday, April 2, 2013 1:33 PM