Cumulative Update 4 - SCOM

[Ackros]

Released on January 31, 2011.

 

Cumulative Update 4 for SCOM 2007 R2 includes all previous cumulative updates for SCOM 2007 R2 and includes all cross-platform updates.

 

Note If you do not have Cumulative Update 3 for SCOM 2007 R2 installed, you must download the latest management packs for monitoring Linux and UNIX computers before you apply Cumulative Update 4 for SCOM 2007 R2.

 

To do this, visit the following Microsoft webpage:

Download the latest management packs for monitoring Linux and UNIX computers

 

 

Cumulative Update 4 for SCOM 2007 R2 resolves the following issues:

 

• 
   
  
• The Performance and Resource Optimization (PRO) Tips feature does not function correctly after you install Cumulative Update 3 for SCOM 2007 R2.
  
• The Alert view does not work correctly when the source of an alert contains both monitors and rules.
  
• The event description is not collected by the Azure management pack. To resolve this issue, build the Windows Azure application by using Windows Azure SDK 1.3.
  
• The monitoring host process may stop responding on a computer that is running on Windows Server 2003 Service Pack 2 (SP2).
  
• The performance of the Diagram view is slow if a user role is in the scope of many groups.
  
• In the web console properties for an alert, the hyperlinks on the Knowledge tab are not active.
  

 

Cumulative Update 4 for SCOM 2007 R2 adds the following features:

 

• 
   
  
• SQL Server 2008 R2 database upgrade support
  
• Automatic recovery for Health Service in a SQL Server failure scenario
   
  

Note By default, this feature is not enabled. For more information about how to enable this feature, see the "Automatic recovery of Health Service in a SQL Server failure scenario" section.

 

To download Cumulative Update 4 for SCOM 2007 R2, visit the following Microsoft Download Center webpage:

Download Cumulative Update 4 for SCOM 2007 R2

 

 

 

 

 

POST INSTALL of CU4 Potential Issues:

 

(source : new-kb-system-center-operations-manager-2007-r2-cu3-amp-cu4-may-cause-non-scom-2007-services-to-restart

 

Summary:

When a System Center Operations Manager 2007 R2 (SCOM) agent is updated to Cumulative Update 3 (CU3) or Cumulative Update 4 (CU4), non-SCOM services may be restarted or a reboot may be requested. The non-SCOM services can be related to other products like SQL Server, Exchange, Windows, SharePoint, etc.

 

The service restarts may happen on Windows Server 2008, Windows Vista and newer operating systems, while the reboot requests may happen on Windows Server 2003 and older operating systems.

 

Resolutions

 

• 
   
  
• Plan agent updates for a time when the possibility of services restarts will not impact service level agreements.
  
• Update Management Servers and databases with the cumulative update, but wait until CU5 to update the agents. CU5 will fix the underlying leak. However, since the update is applying to a system which may have already leaked the reference to EventCommon.dll installing CU5 may exhibit a reboot request as we have disabled the interaction with Restart Manager. Once a system has been updated to CU5 future updates will not cause a reboot request.
  
• You can determine whether a particular computer might be affected by running the following command at the command prompt or in PowerShell and looking for processes besides HealthService.exe & MonitoringHost.exe (specifically WmiPrvSE.exe):
  
• tasklist /m EventCommon.dll
  
• For instance, if you have explored the SCOM performance counters via PerfMon, you may find WmiPrvSE.exe (Windows Management Instrumentation service) in the list of tasks that are currently using EventCommon.dll.
  
• To determine which services will be restarted if the Windows Management Instrumentation (WMI) service is restarted, run the following command in PowerShell:
  

 

 (get-service winmgmt).dependentServices

[Ackros]

How to import the Management Pack before applying CU4

 

MP, IMport, How To....

 

To import a Management Pack

 

• 
   
  
• Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 Management Group.
  
• In the Operations Console, click the Administration button.
   
  

     When you run the Operations Console on a computer that is not a Management Server the Connect To Server dialog box displays. In the Server name text box, type the name of the Operations Manager 2007 Management Server that you want the Operations Console to connect to.

  
  

• Right-click the Management Packs node and then click Import Management Pack(s).
  
• The Select Management Packs to import dialog box displays. If necessary, change to the directory that holds your Management Pack file. Click one or more Management Packs to import from that directory, and then click Open.
  
• In the Import Management Packs dialog box, which displays the Management Packs that you selected, click Add or Remove to edit the list of Management Packs to be imported. When the list is complete, click the Import button.
  
• After the import process is complete, and the dialog box displays an icon next to each Management Pack indicating success or failure of the importation, click the Close button.
  
• The Management Packs pane of the Operations Console lists all imported Management Packs.