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.
- 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.
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:
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:
- 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
- Delete the SRSUpgradeHelperInstalled registry key under the following registry key:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting
- Uninstall the SRSUpgradeHelper tool by using the Add or Remove Programs feature.
- 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:
Issues that are resolved by Cumulative Update 4 for SCOM 2007 R2
|The PRO Tips feature does not function correctly after you install Cumulative Update 3 for SCOM 2007 R2.||The user enables PRO integration and installs Cumulative Update 3 for SCOM 2007 R2. Pro alerts are no longer displayed, and an event that has Event ID 26319 is logged in the Operations Manager log.|
|The Alert view does not work correctly when the source of an alert contains both monitors and rules.||An Alert view contains both monitors and rules as the source of events. This Alert view is configured by using only the specific resolution state – new condition. After an alert is raised and then closed, the Alert view continues to display the closed alert.|
|The description fields for the events that are collected by the monitoring management pack for a Microsoft Azure application are always empty.||The event description is not transferred to Azure diagnostics and is not collected by the Azure Management Pack.|
|The monitoring host process may stop responding on a computer that is running on Windows Server 2003 SP2.||When an instance of Event Code 19 is logged in the System log on an x86-based or x64-based version of Windows Server 2003 SP2, the monitoring host process may stop responding.|
|The performance of the Diagram view is slow if a user role is in the scope of many groups.||A user configures multiple user groups that are in the scope of multiple objects. A user is in many groups. When you open a Diagram view such as AD Topology, the diagram view takes up to 10 minutes to update.|
|In the web console properties for an alert, the hyperlinks on the Knowledge tab are not active.||The user adds custom product information on the Knowledge tab of a monitor or of an alert. This information contains a Universal Naming Convention (UNC) or HTTP link. When you click the link in the web console, the link does not work.|
- 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 startThis 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 startAfter 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"?>
- Follow these steps:
- 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
- Set the value of the ServicesPipeTimeout registry key to 120000.
- Restart the affected computer.
- 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.
- Follow the steps that are described in the following Microsoft Knowledge Base article:
- Follow the steps that are described in the following Microsoft Knowledge Base article.
- 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:To resolve this issue, restart the computer that has ACS installed after you apply the ACS update.Error 2803: Dialog View did not find a record for dialog
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, 2010Note SCOM 2007 R2 supports only the x86-based version of Microsoft Office 2010.
Installation informationThis update must be applied to computers that host any of the following Microsoft Operations Manager servers or agents:
- Root Management Server (RMS)
- Management Server
- Gateway Server
- Operations console
- Web Console server
- An agent that was manually installed
- Audit Collection Services (ACS) server
Note Before you apply this update, we recommend that you back up the Operations database.
Recommended installation orderWe recommend that you install this cumulative update in the following order for an environment:
- Root Management Server (RMS).
- Manually update the Operations Manager database and run the included stored procedure file that is discussed later in this article.
- Manually import the Management Packs that are discussed later in this article.
- Secondary Management Servers.
- Gateway Servers.
- Deploy the agent update to agents that used a discovery-based installation.
- Operations console role computers.
Note When you update this role, select the Run Server Update option from the Software Update dialog box.
- Web Console server role computers.
- Audit Collection Services (ACS) role computers.
- Apply the agent update to manually installed agents.
- When you update a component by using the installer splash screen, you have to complete three update installers. When you update a component such as RMS, each installer starts and requires you to click Finish upon completion. The next installer starts automatically.
- Cumulative Update 4 for SCOM 2007 R2 consists of the following three updates:
- SCOM 2007 R2 updates
- Localized updates
- Cross-platform updates
To extract the files that are contained in this update, follow these steps:
- Copy the following file to either a local folder or to an available network share: SystemCenterOperationsManager2007-R2CU4-KB2449679-X86-X64-IA64-ENU.MSI
- Run this file locally on each applicable computer. For example, run this file on the Root Management Server (RMS).
- Run this file by using either Windows Explorer or by using a command prompt.
- To run this file on a computer that is running Windows Server 2008, you must use an elevated command prompt. An elevated command prompt is a command prompt that was started by using the Run as Administrator option. If you do not run this Windows-based installer file under an elevated command prompt, the System Center Operations Manager 2007 Software Update splash screen does not allow the hotfix to be installed.
- In the System Center Operations Manager 2007 Software Update window, select the update option for the role that will be updated.
Recommended steps that apply this cumulative update on a clustered Root Management Server
For more information about the recommended instructions that apply this cumulative update on a clustered Root Management Server, visit the following Microsoft website:
Manual operations that must be performed after you update the Root Management Server and Data Warehouse
Run the SQL scriptsThis update contains fixes that must be manually applied. These fixes are applied by running the \SQLUpdate\CU4_DataWarehouse.sql file against the OM data warehouse (OperationsManagerDW) and by running the \SQLUpdate\CU4_Database.sql file against the OM database (OperationsManager).
To do this, follow these steps:
- Log on to the computer that hosts the Operations Manager 2007 database by using a user account that has database system administrator (SA) rights to the Operations Manager 2007 database instance. To perform the database update remotely, log on to a computer that hosts SQL Server Management Studio by using a user account that has the appropriate SA rights to the Operations Manager 2007 database.
- Run SQL Server Management Studio.
- In the Connect to Server dialog box, connect to the instance of SQL Server that hosts the Operations Manager database. The default database name is OperationsManager.
- Click New Query on the toolbar.
- From the SQL Editor toolbar, use the Available databases option to select the Operations Manager database.
- On the File menu, click Open, select the \SQLUpdate\CU4_Database.sql file that was extracted by the Windows installer (.msi file), and then click Open.
- When the file is loaded, click Execute in the SQL Editor toolbar.
- View the Messages pane to check whether the Transact-SQL commands ran successfully.
- Exit SQL Server Management Studio.
- For the Operations Manager data warehouse, repeat steps 1-8. However, connect to the instance of SQL Server that hosts the Operations Manager data warehouse, and run the \SQLUpdate\CU4_DataWarehouse.sql file.
Import the management packsThe management packs supplied in the ManagementPacks folder must be manually imported by using the Import Management Packs Wizard and by using the Operations Manager console. The Windows Installer packages that are released for each localized version of Operations Manager contain the appropriate localized version of the management pack. For example, the following file contains the localized version of the management pack for the Japanese localized version of Operations Manager:
Cumulative Update 4 for SCOM 2007 R2 contains the same Linux/UNIX updates that are included in Cumulative Update 3 for SCOM 2007 R2. Therefore, you do not have to install the Linux/UNIX management packs and agents if you have already updated your monitored Linux/UNIX computers by using Cumulative Update 3 for SCOM 2007 R2. If you do not upgrade from Cumulative Update 3 for SCOM 2007 R2, follow these steps to monitor Linux/UNIX computers:
- Download and install the updated management packs from the following Microsoft website:
- Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
- Use the Operations Manager 2007 R2 Discovery Wizard to re-discover the Linux and UNIX computers that you monitor. After you re-discover the computers, the agents on those computers upgrade automatically.
Updated support tools that are included in this cumulative updateThe following updated file in the SupportTools folder supports the upgrade from SQL Reporting Services 2005 to SQL Reporting Services 2008 and from SQL Reporting Services 2008 to SQL Reporting Services 2008 R2:
Advanced installation instructions at a command promptThe installer (hotfix utility) downloaded from this site unpacks the bootstrapping application and necessary MSP files to install Cumulative Update 4 for SCOM 2007 R2. It is better to run the hotfix utility on each computer and deploy Cumulative Update 4 for SCOM 2007 R2 by using the GUI interface that is invoked after you run the hotfix utility. However, you can also bypass multiple installations of the hotfix utility, and then directly deploy unpacked the directory and files to the appropriate computers. The files are in .\System Center 2007 R2 Hotfix Utility\KB 2449679\.
If you decide to install Cumulative Update 4 for SCOM 2007 R2 directly by using the command prompt, use the following command:
Advanced installation instructions if you are using Windows Server CoreWindows Server Core does not include certain DLL files, such as these:
msiexec.exe /p "C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2449679\Agent\KB2449679-x86-Agent.msp" REBOOT="ReallySuppress"
msiexec.exe /p "C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2449679\Agent\KB2449679-x86-ENU-Agent.msp" REBOOT="ReallySuppress"
Advanced installation instruction to manually update installed agents
With Cumulative Update 4 for SCOM 2007 R2, you can manually update installed agents, and you do not have to use the full contents of the package. To deploy updates to an agent by using the minimal number of required files, follow these steps:
- Install the hotfix utility by using the instructions in the "Advanced installation instructions at a command prompt" section.
- Copy all components except ACS, Gateway, ManagementPacks, SCX-Gateway, SQLUpdate, Support Tools and Update Folders, and the msp files in the root folder (KB2449679) of the installer.
- Push the new folder of these coped files to all agent computers.
- Run the following command:SetupUpdateOM.exe /x86msp:KB2449679-x86.msp /amd64msp:KB2449679-x64.msp /ia64msp:KB2449679-ia64.msp /x86locmsp:KB2449679-x86-ENU.msp /amd64locmsp:KB2449679-x64-ENU.msp /ia64locmsp:KB2449679-ia64-ENU.msp /Agent /NoReboot
File list and roles
- <server type> is the name of the UNIX or Linux server product.
- <server version> is the version number of the server type.
- <architecture> is the processor architecture of the destination computer.
- <package type> is the kind of installation file.
The agents that are included with System Center Operations Manager 2007 R2 Cross Platform Agent Update (hotfix 973583) have a version number of 252. All agent files for this version number are removed during the installation of this update.
The agents that are included with the original release of System Center Operations Manager 2007 R2 have a version number of 248. These files are not removed during installation. However, these files are replaced with 1-kilobyte (KB) files. These 1-KB files can be removed by you if you want:
ID do Artigo: 2449679 - Última Revisão: 20/06/2014 - Revisão: 1