This is updated as of 3-31-2021
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 almost every environment, 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.
Operations Manager 2019 update:
| Update Rollup: | Applies to: |
| SCOM 2019 Update Rollup 3 https://kevinholman.com/2021/03/31/ur3-for-scom-2019-step-by-step/ |
MS, WebConsole, Console, GW, Reporting, Agents, MP Import, SQL scripts, UNIX/Linux |
Operations Manager 2016 update:
| Update Rollup: | Applies to: |
| SCOM 2016 Update Rollup 10 https://kevinholman.com/2020/12/07/ur10-for-scom-2016-step-by-step/ |
MS, WebConsole, Console, ACS, GW, Reporting, Agents, MP Import, SQL scripts, UNIX/Linux |
Operations Manager 2012 R2 update:
| Update Rollup: | Applies to: |
| SCOM 2012 R2 Update Rollup 14 https://kevinholman.com/2017/11/28/ur14-for-scom-2012-r2-step-by-step/ |
MS, WebConsole, Console, ACS,GW, Reporting, Agents, MP Import, SQL scripts, UNIX/Linux |
Recommended Windows Operating System Hotfixes:
| Hotfix | Resolves |
Applies to: | Comments |
| 3200006 |
System Center Operations Manager Management Console crashes after you install MS16-118 and MS16-126 |
Console Role Windows 10 Windows 8.1 Windows 7 Server 2016 Server 2012 R2 Server 2012 Server 2008R2 |
I recommend this if you are experiencing a SCOM console crash every time you use a State View in the console. |
| 2954185 | Memory leak in WMIPRVSE.exe caused by monitoring DNS. | Agent role Server 2012 R2 |
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. |
| .NET 4.5.1 |
Config issues with Delta and Snapshot failures |
Management Server Server 2012 |
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. |
| 2923126 | Agents on Windows 2012 R2 Domain Controllers can stop responding or heart-beating | Agent role Server 2012 R2 Windows 8.1 |
I recommend this hotfix on all Windows Server 2012 R2 servers that are experiencing this issue, or proactively on any WS2012R2 domain controller. |
| 2790831 | Handle leak in WmiPrvSE.exe process on Windows 8 or Windows Server 2012 | Agent role Management Server Server 2012 Windows 8 |
I recommend this hotfix to stop the handle leak that WILL occur without it. |
| 2878378 | OpsMgr 2012 or OpsMgr 2007 R2 generates a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1 | Agent Role Management Server Server 2008R2 SP1 |
I recommend this hotfix on all 2008R2 SP1 agents. This helps resolve a slow memory leak in private bytes as well. |
| 2692929 | “0x80041001” error when the Win32_Environment WMI class is queried by multiple requestors in Windows 7 or in Windows Server 2008 R2 | Agent role Server 2008R2 SP1 |
I recommend this hotfix for Server 2008 R2 SP1 machines that also host a ConfigMgr 2007 role, and you are using the ConfigMgr MP. This fixes an annoying issue |
| 2618982 |
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. |
| 2547244 | 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 to any Server 2008R2 or Win7 machine, if it is agent managed or holds a SCOM server role. |
| 2470949 | The RegQueryValueEx function returns a very large incorrect value for the “Avg. Disk sec/Transfer” performance counter in Windows Server 2008 R2 or in Windows 7 | Agent Role Management Server Server 2008 R2 SP1 Windows 7 SP1 |
I recommend this hotfix to be applied to any Server 2008R2 or Win7 machine, if it is agent managed or holds a SCOM server role. |
| 2812950 |
The MOMPerfSnapshotHelper.exe process crashes or experiences high CPU usage in Windows Server 2008 SP2 |
Agent Role 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. |
| 2495300
(see notes) |
Invalid “Avg. Disk sec/Transfer” value returned by the RegQueryValueEx function in Windows Server 2008 or in Windows Vista | Agent Role Server 2008 SP2 |
I recommend this hotfix to be applied to any Server 2008 or Vista machine, if it is agent managed Due to an issue in this KB hotfix breaking teamed network adapters, I recommend deploying:http://support.microsoft.com/kb/2710558/en-us in order to address this issue, which supersedes 2495300 |
| 968967 | 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) |
Agent Role 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 randomlystuck at 100% CPU. If so – this hotfix might be applicable. |
| 981263 | Management servers or assigned agents unexpectedly appear as unavailable in the Operations Manager console in Windows Server 2003 or Windows Server 2008 (ESE jet database corruption) |
Agent Role Server 2008 SP2 Server 2003 SP2 |
I recommend this hotfix for all agent managed servers running Windows Server 2003 SP2, or Windows Server 2008 SP2. |
| MS15-074 |
This enables SHA2 Certificate support is which required to use SCOM 2012R2 UR12 or later. This supercedes previous SHA2 enablers like KB 938397 and KB 968730 |
Agent role Server 2003 SP2 |
I recommend this hotfix for all agent managed computers running Windows Server 2003 SP2 |
| 932370 | The number of physical hyperthreading-enabled processors or the number of physical multicore processors is incorrectly reported in Windows Server 2003 | Agent role Server 2003 SP2 |
I recommend this hotfix for all agent managed computers running Windows Server 2003 SP2 |
| 933061 | WMI Stability in Server 2003 | Agent role Server 2003 SP2 |
I recommend this hotfix for all agent managed computers running Windows Server 2003 SP2 |
| 955360 | Cscript 5.7 update for Server 2003 | Agent role Server 2003 SP2 |
I recommend this hotfix for all agent managed computers running Windows Server 2003 SP2 |
I don’t know if we need any of this in our environment (yet!), but I wanted to say kudos for the well-written post!