• Home
  • Our Services
  • Presentations
  • About me
  • Links
  • Contact Us
  • Privacy Policy

Cloud and Datacenter Management

Cloud at your fingertips
  • Home
  • Our Services
  • Presentations
  • About me
  • Links
  • Contact Us
  • Privacy Policy
Home  /  SystemCenter • Uncategorized  /  Opsmgr Performance problems with healthservice on agents
11 June 2009

Opsmgr Performance problems with healthservice on agents

Written by alexandre@verkinderen.com
SystemCenter, Uncategorized Agents, Issue, manuals, Operations Manager 2007, Opmsgr 2007 R2, opsmgr, opsmgr R2, Performance, scom, WMI Leave a Comment

On some occasions the scom agent can cause a lot of performance issues on the servers. Here I will describe some steps I take when I have performance problems and in most of the cases it works for me.

The first thing you should do is to configure the antivirus exclusions for opsmgr. Have a look at Kevin Holman’s blogpost Antivirus Exclusions for MOM and OpsMgr on how to do this. Configuring anti virus exlusions will help you gain some performance.

This is a screenshot of the performance of my cpu before the anti virus exclusions:

clip_image002[1]

 

And this one is after the anti virus exclusions:

clip_image002[3]

 

The second thing is to have a look at the healthservice.exe. We’ve created a collection performance rule in the previous post to collect the processor time % of the healthservice. If the healthservice is consuming more than 15 a 20 % of your cpu you have a problem . In my case I  had huge performance problems due to the healthservice.exe that was taking all the processor time. My healthservices.exe was taking about 50 to 60 % with peaks to 100% on my agents….You can imagine the reaction of my client….he was not very happy.

Performance view of my healthservice.exe on one of my agents:

clip_image001

So I did some tests, installed all the necessary hotfixes, deleted the healthservice cache, exception of programfilesscom for the antivirus etc etc. But with no results.

So I tought it was WMI and did the following steps to rebuild the wmi:

· Net Stop WinMgmt

· Ren %WinDir%System32WbemRepository %WinDir%System32WbemOldRepository

· Net Start WinMgmt

Still no success, still had performance troubles. I contacted one of our company architects who send me a repairwmi.cmd “program” he developed . It will recompile all the mofiles, re-register all the dll’s, exe’s etc.

Steps to take:

  1. Copy the content of the repairwmi.cmd to the %WinDir%System32Wbem folder

  2. Run the repairwmi.cmd

  3. Stop the opsmgr healthservice

  4. Delete the healthservice cache

  5. Start the opsmgr healthservice

And voila! All my performance problems where gone!!

clip_image002

clip_image003

clip_image004

clip_image005

clip_image006

 

As you can see this reduced drastically the processor time % of the healthservice!

 

Hope this helps,

Alexandre Verkinderen

Related

Share On
Share on Facebook
Share on Twitter
Share on Google+
Share on LinkedIn
alexandre@verkinderen.com

 Previous Article Collect Processor time % of the HealthService.exe of your agents
Next Article   Microsoft Exchange Server 2007 Management Pack for System Center Operations Manager 2007 R2

Related Posts

  • OpsMgr agents not showing up in pending management

    29/03/2015
  • Optimize Azure website performance

    25/01/2015
  • Part 1: Bulk import server locations with PowerShell

    24/03/2014

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Recent Posts

  • Azure API Management Consumption Tier
  • Real Time Twitter sentiment analysis with Azure Cognitive Services
  • Move Managed Disks to another subscription
  • Download MSIgnite 2018 slides
  • Azure Files Updates from Ignite

Twitter

Goodreads

Tags

acs Advisor Agent Agents audit collection service azure Azure Cloud community cubesys end to end monitoring Essentials Events General hotfix HP Issue KB Management Pack manuals MVP Opalis Operations Manager 2007 Opmsgr 2007 R2 opsmgr opsmgr 2012 Opsmgr DB opsmgr R2 Performance powershell R2 reporting SCCM scom SCSM SCVMM service level dashboard Service Manager sql system center teched Uncategorized WAP web application monitoring Windows 2008

Categories

  • Azure
  • IOT
  • it camps
  • MAS
  • OMS
  • Powershell
  • Sharepoint
  • SystemCenter
  • Technet
  • Uncategorized
  • WAP
  • Windows 8

Archives

  • January 2019
  • November 2018
  • October 2018
  • September 2018
  • January 2018
  • December 2017
  • November 2017
  • September 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • November 2016
  • October 2016
  • September 2016
  • July 2016
  • June 2016
  • January 2016
  • December 2015
  • November 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • March 2014
  • January 2014
  • December 2013
  • November 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • November 2012
  • June 2011
  • May 2011
  • April 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • July 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
© Copyright 2017. Alexandre Verkinderen