Home > Operations Manager 2012 > Patch This?!?

Patch This?!?

(Scott on soap-box)If you are new to Operations Manager, please take a look at this and understand, there are KNOWN problems with running Operations Manager at any version level, and there have been OS level hot-fixes created to fix these problems. These patches will need to be installed to Management Servers and or Agent machines that exhibit these problems, however because they are addressing issues specifically related to Operations Manager or a technology it utilizes, for example WMI, these hot-fixes are not a normal part of the patch Tuesday efforts. To learn more about this please read and subscribe to the following web page as Kevin updates it as frequently. http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx (End Soap-box)

From time to time I get the opportunity to see System Center Operations Manager not working at its best. Today it is a memory issue.
The First time I saw this management group there were two management servers, a remote SQL Server and remote SRS instance, with about 100 agents reporting in. The management servers were humming along with the majority of the standard management pack load installed, from the Base OS MP, to Exchange 2010 MP. The loads on the management servers were nominal, and there was not a single process using over a gig of memory.

One month later the client is not happy with the OpsMgr console performance and is concerned about the health of the management servers as there are alerts about memory utilization. So I get a call to check it out. I noticed that a few more Microsoft management packs were added, and 900 more agents. After taking a look at the management server, there was an alert about Health Service Private Bytes Threshold in a critical state in active alerts. Looking at task manager I was able to see that indeed there was some serious memory utilization going on, from the MonitoringHost.exe processes.


Checking over the server, it was a Fresh Windows 2008 R2 SP1 build that was patched, with OS patches. I did notice that the OpsMgr specific patches were not installed. Specifically the three Windows 2008 R2 SP1 patches, that were not on the server. Shamelessly borrowed from Kevin Holman’s OpsMgr Hot fix page. If you have never seen this page, go check it out now. http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx


Windows 2008 R2 or Windows 2008 R2 SP1, or Win7 2547244 Any OpsMgr Agent Managed or Server role
Windows 2008 R2 SP1 2618982 Any OpsMgr Agent Managed or Server role running IIS on Windows 2008 R2 SP1.
Windows 2008 R2 SP1 2470949 Any opsmgr agent or server


After applying these patches, and rebooting the management servers memory utilization for MonitoringHost.exe went down to a much more manageable, 1.5 gigs total, and the alerts from Health Service Private Bytes went away.

Hope this helps out some folks in the near future.

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: