locked
Problematic event detection monitor on Win2K8, but not on Win2K3 RRS feed

  • Question

  • Hello,

    I am trying to create a new manual reset, single event detection unit monitor with the following criteria:

         Event Log: System
         Event ID: 6000 (Equals)
         Event Source: Eventlog (Equals)

    Seeing as I am targeting all Windows Server OS instances, the monitor target is Windows Server Operating System.

    The problem is that the monitor behaves fine on our Windows Server 2003 boxes, but not on our Windows Server 2008 R2 boxes.  The monitor appears in the list of “Running Rules and Monitors for this Health Service” on the Win2K8R2 boxes.

    Does anyone have any ideas why this might be?  Though I did notice that the log type is Error on Win2K3 & Information on Win2K8, I have not specified an Error Level in my criteria.

    Thanks,

    Larry

    • Edited by larry.leblanc Thursday, February 16, 2012 11:04 PM Added info
    Thursday, February 16, 2012 11:00 PM

Answers


  • Hi,

    Please try creating the same monitor and targeting to “Windows Server 2008 R2 Operating System” and see how it works.

    Thanks.


    Nicholas Li

    TechNet Community Support

    • Proposed as answer by Nicholas Li Monday, February 27, 2012 3:10 AM
    • Marked as answer by Nicholas Li Wednesday, February 29, 2012 8:46 AM
    Monday, February 20, 2012 10:28 AM

  • Hi,

    I think you need also ensure the Action Account has enough privileges on the Windows Server 2008 R2 servers.

    Account Information for Operations Manager 2007
    http://technet.microsoft.com/en-us/library/bb735419.aspx

    Thanks.


    Nicholas Li

    TechNet Community Support

    • Proposed as answer by Nicholas Li Monday, February 27, 2012 3:10 AM
    • Marked as answer by Nicholas Li Wednesday, February 29, 2012 8:46 AM
    Wednesday, February 22, 2012 9:48 AM

All replies


  • Hi,

    Please try creating the same monitor and targeting to “Windows Server 2008 R2 Operating System” and see how it works.

    Thanks.


    Nicholas Li

    TechNet Community Support

    • Proposed as answer by Nicholas Li Monday, February 27, 2012 3:10 AM
    • Marked as answer by Nicholas Li Wednesday, February 29, 2012 8:46 AM
    Monday, February 20, 2012 10:28 AM
  •  

    Hello Nicholas,

    I just re-created the monitor, targeting the Windows Server 2008 R2 Operating System class, as you suggested.  I have confirmed that the monitor is successfully running on my target system (via “Show Running Rules and Monitors for this Health Service”), yet the object's health state remains healthy.  Remember that this cannot be a problem with the monitor, as it works flawlessly against Windows Server 2003 boxes, by targeting the Windows Server Operating System class.

    At v6.0.6794.0, I should point out that we are not running the latest version of the Windows Server Base OS Management Pack.

    Thanks,

    Larry

    Monday, February 20, 2012 5:50 PM

  • Hi,

    I think you need also ensure the Action Account has enough privileges on the Windows Server 2008 R2 servers.

    Account Information for Operations Manager 2007
    http://technet.microsoft.com/en-us/library/bb735419.aspx

    Thanks.


    Nicholas Li

    TechNet Community Support

    • Proposed as answer by Nicholas Li Monday, February 27, 2012 3:10 AM
    • Marked as answer by Nicholas Li Wednesday, February 29, 2012 8:46 AM
    Wednesday, February 22, 2012 9:48 AM
  • Good afternoon Nicholas,

    The action account is LOCAL SYSTEM.  I'll see with a Windows Server admin later this week if it has been stripped of certain prviledes.

    Thanks,

    Larry

    Monday, March 12, 2012 8:54 PM