Hello,

my colleague who is responsible for vmware detected the Agent Process Utilization monitor which causes high cpu value on vmware host because the monitor run on every server with scom agent exactly same time. I found a sync time as cause for this.

At first I override to run only once a hour and have only one sample. Maybe this will reduce the cpu load a little bit.

How can I change that the monitor does not run at same time on every server? Can I disable / delete the sync time? Or ist this monitore not relevant and I can delete it?

Regards

Hi, There could be many reasons why the agent processor utilization is increasing, you need to figure that out, some of them can include - anti virus scans, problems with WMI, new monitors/rules etc, please refer below links for more information

http://thoughtsonopsmgr.blogspot.co.uk/2009/07/opsmgr-sp1-is-process-healthservice-of.html

http://scug.be/scom/2009/06/11/opsmgr-performance-problems-with-healthservice-on-agents/

Hope this helps...

Thanks

We figured the process for this Monitor out. The override helped a Little bit so the peaks are lower.

Hi

As you have found out, using overrides can help fine tune, but to answer your original questions:

1. How can I change that the monitor does not run at same time on every server?

Sadly you can't unless you set a different override of sync time on each server which isn't a realistic option.

2. Can I disable / delete the sync time?

No - the monitor is in a sealed management pack so you can't delete it and the author has not exposed an enable \ disable override for sync time.

3. Or ist this monitore not relevant and I can delete it?

No - the monitor is in a sealed management pack so you can't delete it. You could only disable if not relevant. And this monitor is relevant as it will identify agents that have issues:

http://blogs.technet.com/b/kevinholman/archive/2009/12/21/the-new-and-improved-guide-on-healthservice-restarts-aka-agents-bouncing-their-own-healthservice.aspx

Regards

Graham

Hi

As you have found out, using overrides can help fine tune, but to answer your original questions:

1. How can I change that the monitor does not run at same time on every server?

Sadly you can't unless you set a different override of sync time on each server which isn't a realistic option.

2. Can I disable / delete the sync time?

No - the monitor is in a sealed management pack so you can't delete it and the author has not exposed an enable \ disable override for sync time.

3. Or ist this monitore not relevant and I can delete it?

No - the monitor is in a sealed management pack so you can't delete it. You could only disable if not relevant. And this monitor is relevant as it will identify agents that have issues:

http://blogs.technet.com/b/kevinholman/archive/2009/12/21/the-new-and-improved-guide-on-healthservice-restarts-aka-agents-bouncing-their-own-healthservice.aspx

Regards

Graham

• Marked as answer by D. Hacker 21 hours 26 minutes ago

Hi

As you have found out, using overrides can help fine tune, but to answer your original questions:

1. How can I change that the monitor does not run at same time on every server?

Sadly you can't unless you set a different override of sync time on each server which isn't a realistic option.

2. Can I disable / delete the sync time?

No - the monitor is in a sealed management pack so you can't delete it and the author has not exposed an enable \ disable override for sync time.

3. Or ist this monitore not relevant and I can delete it?

No - the monitor is in a sealed management pack so you can't delete it. You could only disable if not relevant. And this monitor is relevant as it will identify agents that have issues:

http://blogs.technet.com/b/kevinholman/archive/2009/12/21/the-new-and-improved-guide-on-healthservice-restarts-aka-agents-bouncing-their-own-healthservice.aspx

Regards

Graham

• Marked as answer by D. Hacker Monday, June 29, 2015 9:44 AM

Hi Graham,

the overrides helped a lot to minimize the traffic. Thanks for responding the other questions.