Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be resolved. Modify the registry at your own risk.
SQL Server 2008 R2 database upgrade support
The feature for SQL Server 2008 database update support lets you upgrade a database for Operations Manager 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 SQL Server 2005 to SQL Server 2008, visit the following Microsoft TechNet website:
In the following upgrade scenarios, follow the steps that are described on the "Upgrading SQL Server 2005 to SQL Server 2008" 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
If you upgraded from SQL Server 2005 to SQL Server 2008, a version of the SRSUpgradeHelper
tool is already installed. To upgrade a database to SQL Server 2008 R2, uninstall this version of the SRSUpgradeHelper
tool, and then install the updated version that is included in Cumulative Update 5 for Operations Manager 2007 R2. To uninstall the previous version of the SRSUpgradeHelper
tool, follow these steps:
- 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 5 for Operations Manager 2007 R2.
Automatic recovery of the System Center Management service in a SQL Server failure scenario
After SQL Server goes offline, the System Center Management service of the root management server (RMS) stops responding. For example, the System Center Management service stops responding after SQL Server disconnects, restarts, or fails. To recover from this issue when SQL Server is available again, you must restart the System Center Management 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 following HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\DAL subkeys:
- "DALInitiateClearPoolSeconds" = dword:0000003c
- "DALInitiateClearPool"= dword:00000001
To apply the DALInitiateClearPoolSeconds
setting, restart the System Center Management service of RMS.
Issues that are resolved by Cumulative Update 5 for Operations Manager 2007 R2
Collapse this tableExpand this table
|Restart of non-Operations Manager services when the agent is updated.||When another application or service has inspected performance counters, that application or service may be restarted when the Operations Manager agent is updated to CU3 or to CU4.|
|Updated ACS reports.||ACS reports are included in the cumulative update package.|
|TCP Port Probe incorrectly reports negative ping latency.||When you use the TCP Port Probe under certain circumstances, a negative ping latency can be reported.|
|MissingEvent Manual Reset Monitor does not work as expected.||The MissingEvent Manual Reset monitor can return an unhealthy state even when the monitored event is detected within the time window.|
|Drillthrough fails because of ParameterTypeMismatch in the EnterpriseManagementChartControl.||When you run Performance reporting on a localized operating system that is trying to drill through, you may receive the error "The value provided for the report parameter 'StartDate_BaseValue' is not valid for its type. (rsReportParameterTypeMisMatch)"|
|ACS - Event log message is truncated or corrupted in SCDW.||Importing a batch of security events sometimes reports error and failed because event description data is corrupted.|
|UI hang that is caused by SDK locking.||Occasionally the Operator console can seem to hang.|
|ACS Filter fails for certain wildcard queries.||When filtering for headers that contain "$," the events are not collected.|
|Edit Schedule button is disabled with SQL 2008 R2.||The Edit Schedule button in the action pane may be disabled even when the report has an associated schedule.|
|Web console is timing out while you open the left navigation tree.||When you open the console, the navigation tree can time out after the 110-second default time-out setting.|
|Scheduled Reports view for Windows Server 2003 and for SQL Server 2005 Reporting Services SP3 CU9 returns "System.IndexOutOfRangeException: Index was outside the bounds of the array."||When you use Windows Server 2003 after you upgrade to CU4, a System.IndexOutOfRangeException can occur when you open the Scheduled Reports view.|
|Signed MPs cannot be imported when new attributes are added to existing classes.||When a new attribute is added to an existing class in a new version of a sealed MP, the MP cannot be imported.|
|Performance data for LVM managed partitions is not available with RHEL 4.8 and later versions or with SLES 10 and later versions.||When you use performance view "Logical Disk\Disk Bytes/sec Performance," all the partitions except root "/" do not show any graph/data for the rule "Disk Bytes/sec."|
|On Solaris or HP-UX, the service name does not show the correct value if the program was started through a symbolic link.||In the Authoring workspace of the Operations console, the Add Monitoring Wizard displays an incorrect Service Name if the service was started through a symbolic link. The Service Name shows the underlying process name instead of the name of the symbolic link.|
|On AIX, the Operations Manager agent may crash when it is enumerating many processes.||On an AIX computer that is running many processes, the scxcimprovagt process (which is part of the Operations Manager agent) may run out of memory when it enumerates all the processes and may crash with a "bad_alloc" error.|
The following released Operations Manager 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, click the following article number to view the article in the Microsoft Knowledge Base :
System Center Operations Manager 2007 R2 does not display new properties in some views after you import a management pack
Known issues for this update
- CU4 update installation entry still exists in ARP after you upgrade to CU5
We plann to resolve this issue in Cumulative Update 6.
- New management packs cannot be edited in the authoring console after the cumulative update is installed
When a new management pack is created after CU4 or CU5 is installed and then an attempt is made to edit the management pack in the Authoring console, the Authoring console cannot edit the management pack because it cannot find the latest version of the Microsoft.SystemCenter.Library management pack (build .61 for CU4 and build .81 for CU5).
To learn more about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
You are prompted for the latest version of the Microsoft.SystemCenter.Library management pack when you try to edit a new management pack in Operations Manager 2007 R2 Manager 2007
- Rollback / SDK start failure
Cumulative Update 5 may roll back multiple times. Or, the System Center Data Access service or the System Center Management Configuration service does not restart after a rollback of Cumulative Update 5 for Operations Manager 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:
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:
- Restart required after ACS update
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 may 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.
The HealthServiceRuntime.dll file is not updated on some Windows 2000 Server-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 Server-based computers and is not addressed in upcoming cumulative updates.
- Cumulative Update 5 agent patching failure
If you apply Cumulative Update 3 for Operations Manager 2007 R2, the pushed agent may not display the update list correctly. This issue occurs because the agent updates in Cumulative Update 3 for Operations Manager 2007 R2 may require a restart operation and then a repair operation. If you do not restart these servers after you apply Cumulative Update 3 for Operations Manager 2007 R2, the agent updates in Cumulative Update 5 for Operations Manager 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 5 for Operations Manager 2007 R2.
- Microsoft Office might be unable to edit Company Knowledge
This issue is not related to Operations Manager cumulative updates and is introduced by an Office security hotfix. To resolve this issue, apply the following hotfix:
Description of the Office Word 2007 hotfix package (wordconv-x-none.msp, word-x-none.msp): December 14, 2010
Note Operations Manager 2007 R2 supports only the x86-based version of Microsoft Office 2010.
- "Path" property of IIS website object might not be displayed correctly
This issue is limited to state views. It does not affect inventory views, and it affects only those state views in which there is duplication of property names between the EnterpriseManagementObject and the class of the object that is being targeted in the state view. The issue is that the Path property of EnterpriseManagementObject collides with the Path property of the class that is being targeted (Microsoft.Windows.InternetInformationServices.WebSite). We are considering fixing this issue in a future cumulative update.
This 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
To apply this cumulative update, you must use an account that has the same user rights that were used during the installation of Operations Manager. When you update the Operation Manager database, use an account that has local administrator rights on the computer and that has system administrator (SA) credentials on the database. When you update RMS, use an account that has administrator rights and that is a member of the Operations Manager Administrators group. Note
Before you apply this update, we recommend that you back up the OperationsManager database.
Recommended installation order
We recommend that you install this cumulative update in the following order:
- Root management server (RMS).
- Manually update the Operations Manager database by running 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.
- Apply the agent update to manually installed agents.
- Audit Collection Services (ACS) role computers.
- 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 when the update is completed. The next installer starts automatically.
- Cumulative Update 5 for Operations Manager 2007 R2 consists of the following three updates:
- Operations Manager 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 an available network share:
- 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 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 let the hotfix 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 for applying this cumulative update to a clustered root management server
For more information about the recommended instructions for applying this cumulative update to 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 scripts
This update contains fixes that must be manually applied. These fixes are applied by running the \SQLUpdate\CU5_DataWarehouse.sql file against the Operations Manager data warehouse (OperationsManagerDW) and by running the \SQLUpdate\CU5_Database.sql file against the Operations Manager 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\CU5_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 through 8. However, connect to the instance of SQL Server that hosts the Operations Manager data warehouse, and then run the \SQLUpdate\CU5_DataWarehouse.sql file.
Import the management packs
The management packs that are supplied in the ManagementPacks folder must be manually imported by using the Import Management Packs Wizard in the Operations 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:
The following updated management packs are located in the ManagementPacks folder of the package installation:
Update the Web.Config file on the Web Console server role computers
To make sure that all cookies that are created by the web console cannot be accessed by the client cscript, add the following configuration to the Web.Config file on the web console server:
However, if the web console is configured to run under SSL, add the following configuration to the Web.Config file instead to make sure that all cookies are encrypted:
<httpCookies httpOnlyCookies="true" requireSSL="true"/>Note
Only one of these lines needs to be added to the Web.Config file. To add one of these lines, scroll down in the Web.Config file until you see the <system.web>
tag, and then add the appropriate new line immediately after the line that contains <system.web>
Install Linux/UNIX management packs, and update Linux/UNIX agents
Cumulative Update 5 for Operations Manager 2007 R2 contains the same Linux/UNIX updates that are included in Cumulative Update 3 for Operations Manager 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 Operations Manager 2007 R2. If you do not upgrade from Cumulative Update 3 for Operations Manager 2007 R2, follow these steps to monitor Linux/UNIX computers:
- Download and then 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 rediscover the Linux and UNIX computers that you monitor. After you rediscover the computers, the agents on those computers upgrade automatically.
Updated support tools that are included in this cumulative update
The 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:
Use the appropriate platform version of this file instead of the file that is supplied in the SupportTools folder of the Operations Manager 2008 R2 distribution media.
Advanced installation instructions at a command prompt
The installer (hotfix utility) that is downloaded from this site unpacks the bootstrapping application and necessary MSP files to install Cumulative Update 5 for Operations Manager 2007 R2. It is better to run the hotfix utility on each computer and to deploy Cumulative Update 5 for Operations Manager 2007 R2 by using the GUI interface that is invoked after you run the hotfix utility. However, you can avoid multiple installations of the hotfix utility by copying the unpacked directory and files to the appropriate computers. These files are unpacked to the following location by the hotfix utility:
\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2495674\
If you decide to install Cumulative Update 5 for Operations Manager 2007 R2 at a command prompt, use the following command:
SetupUpdateOM.exe /x86msp:KB<#>-x86.msp /amd64msp:KB<#>-x64.msp /ia64msp:KB<#>-ia64.msp /x86locmsp:KB<#>-x86-<LOC>.msp /amd64locmsp:KB<#>-x64-<LOC>.msp /ia64locmsp:KB<#>-ia64-<LOC>.msp /UpdateAgent /Silent /norebootNote
flag is not necessary if you want to install Cumulative Update 5 for Operations Manager 2007 R2 by using the GUI interface. Replace the <LOC>
parameter with the appropriate language code for the update that you have downloaded. Replace the <#>
parameter with the Microsoft Knowledge Base article number for this cumulative update.
For example, run the following command for the English version of Cumulative Update 5 for Operations Manager 2007 R2:
SetupUpdateOM.exe /x86msp:KB2495674-x86.msp /amd64msp:KB2495674-x64.msp /ia64msp:KB2495674-ia64.msp /x86locmsp:KB2495674-x86-ENU.msp /amd64locmsp:KB2495674-x64-ENU.msp /ia64locmsp:KB2495674-ia64-ENU.msp /UpdateAgent /Silent /noreboot
Advanced installation instruction to manually update agents
With Cumulative Update 5 for Operations Manager 2007 R2, you can manually update agents without copying the full contents of the package. To deploy updates to an agent, follow these steps:
- Install the hotfix utility by using the instructions in the "Advanced installation instructions at a command prompt" section. By default, the files that you have to have to update the agent are found at the following location:
C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2495674
- Copy the appropriate MSP files to a folder of your choosing (for example, C:\temp\CU5_Agent) on each computer on which you want to manually update the agent.
- Run the following commands at a command prompt from the folder that contains the update files (C:\temp\CU5_Agent if you follow the suggestion here) (ex: x64 architecture and English language):
msiexec.exe /p "C:\temp\CU5_Agent\KB2495674-x64-Agent.msp" REBOOT="ReallySuppress"
msiexec.exe /p "C:\temp\CU5_Agent\KB2495674-x64-ENU-Agent.msp" REBOOT="ReallySuppress"
Note Replace ENU with the language code of the Cumulative Update 5 for Operations Manager 2007 R2 package that you downloaded. Also, if you want to do a silent install, add the /qn switch to the command line.
File list and roles
Collapse this tableExpand this table
|HeaderControl.ascx ||Not applicable||X|
This update installs updated UNIX and Linux agents, and this update removes older UNIX and Linux agents in the following folder:
Program Files\System Center Operations Manager 2007\AgentManagement\UnixAgents
The updated agents have file names that use the following format and a version number of 277
scx-1.0.4-277-server type.server version.architecture.package typeNotes
- The placeholder server type represents the name of the UNIX or Linux server product.
- The placeholder server version represents the version number of the server type.
- The placeholder architecture represents the processor architecture of the destination computer.
- The placeholder package type represents the kind of installation file.
For example, the following is the file name format for the agent for SUSE Linux Enterprise Server 10 (x86):
The agents that are included with Systems Center Operations Manager 2007 R2 Cross Platform Cumulative Update 2 (hotfix 979490) have a version number of 258
. All agent files for this version number are removed during the installation of this update.
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. You have the option of removing these 1-KB files. These files are as follows: