I'm trying to pinpoint what may be the cause of 2 of our servers (out of ~300 with agents) keep alerting on the "OpsMgr Agent process are using too much processor time". Some background/environment info:
1) Both servers are VMs running Windows Server 2008 R2. 2) All servers previously on SCOM 2007 are multi-homed between our 2007/2012 environments. 3) Our SCOM 2007 environment is triggering the alert. 4) Every 5mins the MonitoringHost.exe process on both servers spikes to values between 60-100%. It lasts anywhere from 5-15 seconds. 5) 2007 and 2012 SCOM management servers are patched to the latest respective releases. 6) Agent versions on all multi-homed servers are identical (v7.1.10184.0) 7) The alerts started after pushing out the 2012 agent and multi-homing began. None of our other multi-homed servers (ranging from Windows Server 2003 SP2 to 2012 R2) are alerting on this issue. The MonitoringHost.exe process starts off small around 5MB and steadily grows and eventually resets. I haven't figured out the exact trigger, if it's time or size, but the largest I've seen committed to a single MonitoringHost.exe process is about 175MB. Kevin Holman's blog entry (Link Here<http://blogs.technet.com/b/kevinholman/archive/2009/07/20/do-you-randomly-see-a-monitoringhost-exe-process-consuming-lots-of-cpu.aspx>) points to a hotfix (http://support.microsoft.com/kb/968967) but the newest OS that hotfix applies to is 2008 Std (non-R2). There is a comment from Kevin in the comments section of his article about placing various MPs into Maintenance Mode and seeing if the issue persists. However, due to my novice experience, I'm not sure how to tell which MPs are applied to these two servers-they are both generic 2008 R2 boxes, one has SQL the other IIS. Otherwise they (appear) identical to me. So outside of those two roles/programs, I'm not sure what MPs SCOM would use other than basic Windows OS MPs...I think. Should I be looking in the 2007 environment because the alerts are coming from 2007? Or is there a place to correlate the timestamps of the MonitoringHost.exe spiking to see what monitor/rule or performance data the agent is trying to gather? I understand some of these questions may be quite basic, I don't have much experience (yet) in the SCOM world, and I dug around most of yesterday and part of today to pinpoint what may be the cause, so now just hoping for a little help. Thank you for your time. -Geoff Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
