Which hotfixes should I apply?
This is updated as of 1-16-2010
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.
Before we get to the lists – some general guidance on hotfixes to make you more successful:
ALWAYS - on Server 2008 OS, run the hotfix MSI from an elevated command prompt window. This will launch the install of the hotfix, and then launch the boot-strapper window in an elevated process – which is required. Do this regardless of the UAC configuration of the 2008 OS.
ALWAYS - make sure you read the instructions to understand if the hotfix is a SQL update, installed to the RMS, MS, and/or Gateway, AND/OR applies to agents as well.
ALWAYS - make sure you double-check the DLL version of the updated files to make sure the hotfix successfully applied after installing.
ALWAYS - make sure you double-check the \AgentManagement directory of the management servers and gateways, to make sure if there is an agent update, the x86 and x64 MSP was copied over correctly.
ALWAYS – when installing a hotfix on a SCOM server role, run the downloaded MSI, such as “SystemCenterOperationsManager2007-SP1-KB954049-X86-X64-ENU.MSI” – and install the “System Center 2007 Hotfix Utility” to the DEFAULT location – and then kick off the update FROM THE UI that comes up by clicking “Run Software Update”. This is critical and not following this process is the cause for many failures to apply the hotfix DLL’s, or failure to copy the agent MSP update files to the \Agentmanagement directory. NEVER run the MSP files manually on a SCOM server role… because the additional steps run by the boot-strapper will not execute if you do that.
ALWAYS check the language version of the hotfix, and make sure it is the same language version as your SCOM base install. For instance – if you have a English base SCOM install – do not download a localized German version of a hotfix and apply it – or it can break the English SCOM base install.
Common OpsMgr 2007 Post-R2 hotfixes:
This list ABSOLUTELY assumes you are at OpsMgr R2-RTM level as a base (6.1.7221.0).
| Hotfix | Update Files | Supersedes Hotfix(s) | Resolves
| Applies to: | Comments |
| MP Update | Microsoft.SystemCenter.2007.mp
6.1.7533.0
Microsoft.SystemCenter. OperationsManager.2007.mp 6.1.7533.0
Microsoft.SystemCenter. OperationsManager.AM.DR.2007.mp 6.1.7533.0 | none | Agent restarts, other enhancements | MP import only | I recommend this update for ALL OpsMgr R2 environments. |
974144
R2 CU1 | Multiple. See KB Article. Note this is a DLL update, MP update, and a SQL script update. | none | Cluster removal
CPU utilization on passive nodes
Console crashes
Health State fixes
Re-reads of event logs
Memory leak.
Many other updates. | RMS
MS
GW
Agents
AuditCollector
Console
WebConsole
MP Import
TSQL Script
| I recommend this update for ALL OpsMgr R2 environments.
This hotfix includes a SQL script, which you execute on the database in a query window. |
| 971233 | none | none | The console shows customized subscriptions SMTP{GUID} after you upgrade to OpsMgr R2 from OpsMgr SP1 | Operations Database (TSQL only) | I recommend this hotfix only if you are impacted with this issue. |
| | | | | | |
Common OpsMgr 2007 Post-SP1 hotfixes:
This list ABSOLUTELY assumes you are at OpsMgr SP1 level as a base (6.0.6278.0). These DO NOT APPLY these to OpsMgr R2.
| Hotfix | Update Files | Supersedes Hotfix(s) | Resolves
| Applies to: | Comments |
| MP Update | Microsoft.SystemCenter.2007.mp 6.0.6709.0 Microsoft.SystemCenter. OperationsManager.2007.mp 6.0.6709.0 Microsoft.SystemCenter. OperationsManager.AM.DR.2007.mp 6.0.6709.0 | none | Agent restarts, many other critical enhancements | Management Pack Import only (Import via console once extracted) | I recommend this update for ALL OpsMgr SP1 environments. |
| 971541 | SP1 Rollup hotfix. Multiple files. See KB article | Many. See KB article | Many. See KB article | RMS
MS
GW
Reporting
Agents
Console
MP Import | I recommend this update for ALL OpsMgr SP1 environments. |
| 972881 | Managedentitychange.sp.sql | none | The changes to the display name of a managed entity are not synchronized in the Operations Manager Data Warehouse database | Data Warehouse Database (T-SQL only) | I recommend this update for ALL OpsMgr SP1 environments.
This hotfix includes a SQL script, which you execute on the database in a query window.
|
| 954643 | Managementpackinstall.sp.sql | none | Event ID 31569 is logged after you install a management pack that includes reports on a System Center Operations Manager 2007 SP1 server | Data Warehouse Database (T-SQL only) | I recommend this hotfix only if you are impacted with these events.
This hotfix includes a SQL script, which you execute on the database in a query window.
|
| 974254 | Autotablecreation.sql
Viewcreatesprocs.sql | none | 1. Unable to create large number of groups.
2. Import fails when importing an MP or when creating a MP from a template | Operations Database (TSQL only) | I recommend this hotfix only if you are impacted with this issue.
This hotfix includes a SQL script, which you execute on the database in a query window.
|
| | | | | | |
Common related Windows Operating System Hotfixes:
This list is not sorted by OS or anything special – just a collection of OS related hotfixes that SCOM might require, or might fix an issue with the OS that impacts OpsMgr. These can apply to Sp1 or R2 environments.
| Hotfix | Resolves
| Applies to: | Comments |
| 933061 | WMI Stability in Server 2003 | Agent | I recommend this hotfix for all agent managed computers running Windows Server 2003, SP1 or SP2, x86 or x64 |
| 955360 | Cscript 5.7 update for Server 2003 | Agent | I recommend this hotfix for all agent managed computers running Windows Server 2003, SP1 or SP2, x86 or x64 |
| 968760 | High handle count on the RMS
A managed application has a high number of thread handles and of event handles in the Microsoft .NET Framework 2.0 | RMS | I recommend this hotfix is you are experiencing high handle count on the RMS.
This hotfix requires SP2 for the OS and .NET 2.0 SP2. |
| 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) | RMS
MS
GW
Agent | I recommend this hotfix if you are impacted with this issue.
You might find a MonitoringHost.exe process randomly stuck at 100% CPU. If so – this hotfix might be applicable. |
| 951327 | The System Center Operations Manager 2007 console may crash in Windows Server 2008 or in Windows Vista when you open the Health Explorer window | Any Vista or Server 2008 computer with a SCOM console installed | I recommend this hotfix only if you run the console on Server 2008 or Vista.
This hotfix is already included in Server 2008 SP2. |
| 952664 | The Event Log service may stop responding because of a deadlock on a Windows Server 2008-based or Windows Vista-based computer | RMS
MS
GW
Agent | I recommend this hotfix only if you host an OpsMgr server or agent role on Vista or Server 2008.
This hotfix is already included in Server 2008 SP2. |
| 953290 | An application may crash when it uses legacy methods to query performance counter values in Windows Vista or in Windows Server 2008 | RMS
MS
GW
Agent | I recommend this hotfix only if you host an OpsMgr server or agent role on Vista or Server 2008.
This hotfix is already included in Server 2008 SP2. |
| 958661 | FIX: Small memory leaks may occur when you use RSCA to query runtime statistics in IIS 7.0 | Any OpsMgr Agent/Server role with IIS 7.0 installed | I recommend this hotfix in all cases where you are monitoring servers with IIS 7.0 installed, and use the IIS Management pack.
This hotfix is already included in Server 2008 SP2. |
| 958807 | Windows Server 2008 Failover Clustering WMI provider does not correctly handle invalid characters in the private property names causing WMI queries to fail | Any Server 2008 agent managed cluster node | I recommend this hotfix only if you are impacted with this issue, and use the current Cluster MP. |
| | | | |
Make sure you see these additional posts on the subject of hotfixes:
http://blogs.technet.com/kevinholman/archive/2008/06/25/a-little-tidbit-on-hot-fixes-for-opsmgr.aspx
http://blogs.technet.com/kevinholman/archive/2008/06/24/how-do-i-know-which-hotfixes-have-been-applied-to-which-agents.aspx
http://blogs.technet.com/kevinholman/archive/2008/06/27/a-report-to-show-all-agents-missing-a-specific-hotfix.aspx
http://blogs.technet.com/kevinholman/archive/2009/02/25/applying-an-opsmgr-hotfix-to-a-rms-cluster-node-some-things-to-be-aware-of.aspx
Several of these updates require agent updates as well, so be prepared to deal with those.
