How does CPU monitoring work in the Windows Server 2016 management pack?

  • 發行項

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    May 14, 2017
    nice information, thanks for sharing
  • Anonymous
    May 14, 2017
    HiDoes this logic "multiplied times the number of logical CPU’s for the server" apply to the rest of the OS MP:s (2008-2012)?
    • Anonymous
      May 14, 2017
      No - it would be somewhat different, since the previous MP's for 2008-2012 don't discover logical CPU's - they only discover sockets..... which makes the concept pretty worthless on those versions.
      • Anonymous
        May 15, 2017
        So if I understand this correctly. The monitor for 2016 takes the nr of Logical CPUs from the property "logicalprocessors" on the Windows Server class. Then uses that value in the Queue Lenght part of the monitor?And that is not the case for 2008-2012 monitor?
  • Anonymous
    May 24, 2017
    The comment has been removed
    • Anonymous
      May 24, 2017
      Man, that script is buggy. There are lots of complaints right now.... I am waiting for SCOM 2012 UR13 and SCOM 2016 UR3, to see if they fix it. If it isnt 100%, I'll provide guidance and recommendations on how to disable that. There is a rule and a monitor that runs the script.
      • Anonymous
        May 25, 2017
        Thanks for the reply Kevin, I updated to UR3 hoping the same and found that the script is still causing failures. Seems the MPs did not change from UR2. I will be disabling the Monitors and Rules for now.