SCOM 2012 Cumulative Update 2 Released
Even though it has only been released officially for just over 4 months SCOM 2012 is already due for it’s second cumulative update. This update is part of the cumulative updates for the wider range of System Center 2012 products. Other updates are available for DPM, Orchestrator and Virtual Machine Manager (VMM). Unlike the previous cumulative update, CU1, this new update only addresses five issues within SCOM 2012, and three of these are Cross-platform/Unix/Linux related.
The issues addressed as per KB2731874 are:
Issue 1- The Windows PowerShell module runspace configuration cache grows indefinitely. This causes memory usage to increase.
Issue 2 – The Set-SCOMLicense cmdlet fails if the management group evaluation expiration time-out has expired.
Issue 3 – The System Center Operations Manager agent may crash on Oracle Solaris root zones that are configured to use a range of dedicated CPUs.
Issue 4 – The UNIX/Linux agent process provider may not enumerate running processes if a process has arguments that include non-ASCII characters. This prevents process/daemon monitoring.
Issue 5 – The .rpm specification file for the agent for Red Hat Enterprise Linux does not specify the distribution.
The cumulative update for SCOM 2012 can be downloaded from here.
Thankfully the cumulative updates in 2012 are far easier to manage than the updates in 2007 R2 and there is now no need to run SQL queries against the database as part of the update.
The recommended update path is as follows:
Server Infrastructure Deployment Order Overview:
- Management server or server
- Gateway servers
- Reporting servers
- Web console server role computer
- Operations console role computers
Update Management Packs Overview:
- Manually import CU2 management packs
Agent Deployment Overview:
- Apply the agent update to manually installed agents, or push installation from the Pending view in the Operations console.
As always, Kevin Holman has written a brilliant article on installing the upgrade and I would highly recommend following his steps to ensure a successful deployment of CU2. The update article can be found here