In general – you should evaluate all hotfixes available, and only apply those applicable to your environment. However, some of these below I have seen impact almosteveryenvironment, and should be heavily considered.
This list is nothing official…. this is just a general list of the recommended hotfixes I end up proactively applying to most environments…. it is not a complete list of ALL hotfixes, and you may be affected by other issues.
I recommend this hotfix on all Windows Server 2012 R2 DNS servers that are monitored using the DNS management pack, or any type of monitoring which leverages the DNS PowerShell providers. The leak is caused by accessing the DNS PowerShell providers, which scripts will often call.
Config issues with Delta and Snapshot failures
If your management servers are running Windows 2012 RTM (non R2) then you MUST upgrade .NET to 4.5.1 or 4.5.2. This will resolve a problem seen in larger environments where Snapshot and Delta Config fail due to timeouts.
Memory leak occurs when monitoring IIS. The IIS MP discovery modules leverage the same function called out in the KB. This causes a memory leak in Monitoringhost.exe over time on IIS servers, especially when using APM in OpsMgr 2012.
Agent Role or Management Server role running IIS on:
Server 2008 R2 SP1
I recommend this hotfix to be applied to any Server 2008R2 SP1 OS, if it is agent managed and has IIS installed.
The WMI service and the WMI providers stop responding when you use WMI performance classes to monitor performance on a computer that is running Windows 7 or Windows Server 2008 R2
Agent Role Management Server
Server 2008 R2 SP1 Windows 7 SP1
I recommend this hotfix if you are experiencing WMI failures, service crashes, or failures to collect data from WMI performance counters via script. If impacted, it would be applied toany Server 2008R2 or Win7 machine, if it is agent managed or holds a SCOM server role.
The MOMPerfSnapshotHelper.exe process crashes or experiences high CPU usage in Windows Server 2008 SP2
Server 2008 SP2
Assume that you run Microsoft System Center 2012 Operations Manager to collect performance counter information on a computer that is running Windows Server 2008 Service Pack 2 (SP2). In this situation, the MOMPerfSnapshotHelper.exe process crashes or experiences high CPU usage. Note This issue usually occurs on a server that has Microsoft SharePoint 2010 installed. This is because there are more than 64 V2 performance counters installed.
Invalid “Avg. Disk sec/Transfer” value returned by the RegQueryValueEx function in Windows Server 2008 or in Windows Vista
Server 2008 SP2
I recommend this hotfix to be applied to any Server 2008 or Vista machine, if it is agent managed
The CPU usage of an application or a service that uses MSXML 6.0 to handle XML requests reaches 100% in Windows Server 2008, Windows Vista, Windows XP Service Pack 3, or other systems that have MSXML 6.0 installed (Spinlock)
Server 2008 SP2
I recommend this hotfix if you are impacted with this issue, which is very common.
You might find a MonitoringHost.exe process randomlystuckat 100% CPU. If so – this hotfix might be applicable.