System Center Operations Manager 2007 R2 Cumulative Update 4

This article contains a complete description of all changes in Cumulative Update 4 for Microsoft System Center Operations Manager (SCOM) 2007 R2.

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

Note Any cross-platform changes for this update and for future updates are no longer described in a separate Microsoft Knowledge Base (KB) article.

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 Microsoft Azure application by using Microsoft 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 R2Note 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

SQL Server 2008 R2 database upgrade support

The feature for SQL Server 2008 database update support lets you upgrade a database for SCOM 2007 R2 to SQL Server 2008 R2. The tools for this feature are in the SupportTools folder of the update package. For more information about how to upgrade a database from SCOM 2007 R2, visit the following Microsoft TechNet article:

How to upgrade a database from SCOM 2007 R2In the following upgrade scenarios, follow the steps that are described on the "How to update a database from SCOM 2007 R2" TechNet website:

• SQL Reporting Services 2005 to SQL Reporting Services 2008 Service Pack 1 (SP1)

• SQL Reporting Services 2008 Service Pack 1 (SP1) to SQL Reporting Services 2008 R2

Important If you have upgraded from SQL Server 2005 to SQL Server 2008, a version of the SRSUpgradeTool tool is already installed. To upgrade a database to SQL Server 2008 R2, uninstall this version of the SRSUpgradeTool tool, and then install the updated version that is included in Cumulative Update 4 for SCOM 2007 R2. To uninstall the previous version of the SRSUpgradeTool tool, follow these steps:

1. Delete the SRSUpgradeHelperInstalled registry key under the following registry key:
   

   HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting

2. Uninstall the SRSUpgradeHelper tool by using the Add or Remove Programs feature.

3. Install the updated version that is included in Cumulative Update 4 for SCOM 2007 R2.

Automatic recovery of Health Service in a SQL Server failure scenario

After SQL Server goes offline, Health Service of Root Management Server (RMS) stops responding. For example, Health Service stops responding after SQL Server disconnects, restarts, or fails. To recover from this issue when SQL Server is available again, you must restart Health Service.

By default, this automatic recovery feature is disabled. The DALInitiateClearPoolSeconds setting controls when RMS drops the current connection pool and when RMS tries to reestablish an SQL connection. We recommend that you set this setting to 60 seconds or more to avoid performance issues. To configure this recommended setting, set the following values for the [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\DAL] subkeys:

• "DALInitiateClearPoolSeconds"=dword:0000003c

• "DALInitiateClearPool"=dword:00000001

Note To apply the DALInitiateClearPoolSeconds setting, restart Health Service of RMS.

Issues that are resolved by Cumulative Update 4 for SCOM 2007 R2

The following released SCOM 2007 R2 hotfix is not included in this update because the hotfix includes SQL Server Transact-SQL scripts, SQL Stored Procedure updates, or cross-platform agent updates. For more information about how to obtain a hotfix for this issue, visit the following Microsoft Knowledge Base article:

981740 System Center Operations Manager 2007 R2 does not display new properties in some views after you import a management pack List of known issues for this update

• Restart of non-Operations Manager services
  In certain cases, non-Operations Manager services may be restarted when the Operations Manager agent is updated. This issue only affects computers that are running Windows Server 2008 or Windows Server 2008 R2. We recommend that you update agents at a time when a service restart or a server restart is acceptable. Or, only update agents that are experiencing one or more of the agent-related issues that are mentioned in the list of resolved issues. This issue will be addressed in an upcoming cumulative update.

• New management pack edit issue
  When you create a new management pack after you install Cumulative Update 4, exporting the management pack and changing it by using the authoring console does not work correctly. This behavior occurs because the authoring console cannot find the .61 version of the Microsoft.SystemCenter.Library Management Pack. This issue is scheduled to be addressed in Cumulative Update 5. For immediate resolution, please contact Microsoft Customer Support Services for a copy of this management pack, or update your references section to use the .0 version of this management pack.

• Rollback / SDK start failure
  Cumulative Update 4 may roll back multiple times. Or, the SDK Service or Config Service does not restart after a rollback of Cumulative Update 4 for SCOM 2007 R2. Additionally, the "CAStartServices: StartService failed. Error Code: 0x8007041D" error message may be logged in the log file for the installation of the update. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

  936707 FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start This issue occurs because of a known .NET Framework 2.0 issue in which a certificate revocation list (CRL) response delay affects a small percentage of computers. If you encounter this issue, apply one of the following workarounds:

  • Follow the steps that are described in the following Microsoft Knowledge Base article.
    
    Note You do not have to install hotfix 963707 if you have the .NET Framework 2.0 Service Pack 1 (SP1) or a later version of the .NET Framework installed.

    936707 FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start After you install hotfix 963707, change the manifest file for the Config Service and SDK Service on the affected computers. This solution disables CRL checking for the specified executables permanently. To do this, use the following tags to edit the <runtime> section of the Microsoft.MOM.ConfigServiceHost.exe.config and Microsoft.MOM.Sdk.ServiceHost.exe.config files that are stored in the OM installation directory:

    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
    <runtime>
    <generatePublisherEvidence enabled="false"/>
    </runtime>
    </configuration>

  • Follow these steps:

    1. Follow the steps that are described in the following Microsoft Knowledge Base article:

       922918 A service does not start, and events 7000 and 7011 are logged in Windows Server 2003

    2. Set the value of the ServicesPipeTimeout registry key to 120000.

    3. Restart the affected computer.

    4. Reapply Cumulative Update 4 for SCOM 2007 R2.
       
       Note The Cumulative Update 4 installer may display an error or warning in the installation process. Ignore all these warnings and errors by clicking to continue.

• When you apply the Audit Collection Services (ACS) update, you may have to restart the computer if an affected file is being used. Additionally, you receive an error message that resembles the following:
  

  Error 2803: Dialog View did not find a record for dialog

  To resolve this issue, restart the computer that has ACS installed after you apply the ACS update.
  
  Note Some ACS report updates that are described together with Cumulative Update 3 are not actually included in either Cumulative Update 3 or Cumulative Update 4 for SCOM 2007 R2. These updates are available in an upcoming update.

• The HealthServiceRuntime.dll file is not updated on some Windows 2000-based agent computers. This means that the resolution for the following issue is not applied:
  

  The monitoring host process does not start the workflows immediately when tasks are received.This hotfix is not supported on Windows 2000-based computers and is not addressed in upcoming cumulative updates.

• Cumulative Update 4 agent patching failure
  If you apply Cumulative Update 3 for SCOM 2007 R2, the pushed agent may not display the update list correctly. This issue occurs because the agent updates in Cumulative Update 3 for SCOM 2007 R2 may require a restart operation followed by a repair operation. If you do not restart these servers after you apply Cumulative Update 3 for SCOM 2007 R2, the agent updates in Cumulative Update 4 for SCOM 2007 R2 are not applied. However, the restart required state is set on these computers. Therefore, you have to restart these computers and then repair the agent to apply the updates in Cumulative Update 4 for SCOM 2007 R2.

• Microsoft Office might be unable to edit Company Knowledge. This issue is not related to SCOM cumulative updates and is introduced by an Office security hotfix. To resolve this issue, apply the following hotfix:

  2458608 Description of the Office Word 2007 hotfix package (wordconv-x-none.msp, word-x-none.msp): December 14, 2010 Note SCOM 2007 R2 supports only the x86-based version of Microsoft Office 2010.