| Symptoms | Scenario |
| The network device state view does not display the device name. | You add one or more network devices, you open the monitoring pane, you select and then right-click Network Devices, and then you select Personalize View. When you click to select the Device Name check box, the device name does not appear. |
| If the discovery data contains some double-byte characters such as Japanese Characters, the discovery process fails when you try to insert a value into a string. | When a discovery process tries to insert a double-byte character into a string value, the request is rejected by the Root Management Server.
Note Double-byte characters are used in non-Latin languages such as Japanese. |
| The availability reports that are exported to TIF files or to PDF files are truncated. | When you export an availability report to a TIF file or to a PDF file, the print preview feature shows the report truncated. The printout of the report is multiple pages long. |
| The property bags of the WMIEventProvider module do not support including or excluding of specific properties. | Manipulating the output of the Microsoft.Windows.WmiEventProvider module by using the PropertyIncludes and PropertyExcludes configuration parameters in the Management Pack is not supported.
Note These configuration parameters define the included or excluded Windows Management Instrumentation (WMI) properties. |
The color of the chart lines does not match the legend in the Web console in the
Performance view. | The user selects the performance view for an instance that has a large amount of data in the Web console. The user selects and unselects what data is displayed. After the user selects and unselects the data, the chart lines do not correspond to the chart legend. |
| When SQL Reporting Services is enabled in SCOM by using the United States FIPS security, the datawarehouse encounters an InvalidOperationException error. | The user enables the United States FIPS compliance policy on a Root Management Server that is running Windows Server 2008 and that has SCOM Reporting Services installed. When this action is taken, the InvalidOperationException error occurs, and the data is no longer collected in the datawarehouse.
For more information about the United States FIPS, visit the following Microsoft Web site: |
| The monitoring host process does not start immediately when tasks are received. | When a monitoring host sends some workflows to another monitoring host, the second monitoring host does not start the workflows until all tasks are received. |
| The Operations Manager console crashes when you open multiple customized views in a new window. | The user starts the Operations Manager console. In different windows, the user opens more than three state views and opens more than three diagram views. After 5-10 minutes, the console crashes. |
| The Allow Anonymous discovery property in the Internet Information Services (IIS) Management Pack is incorrect in the console. | The user installs IIS together with an FTP site on a server that is running Windows Server 2003. After you install the IIS Management Pack, the Allow Anonymous discovery property changes when the discovery process occurs regardless of how IIS is configured. |
| A restart dialog box appears when you run an update before the files for the update are received. | When you install an update, the user clicks Run Server Update. Then, the user is given the option to restart the computer. However, the update agent has not yet received the updates. |
| The agent update packages are not deployed to servers that have the Terminal Services Gateway (TS Gateway) role installed or that have the Remote Desktop Gateway (RD Gateway) role service installed. | When you install Cumulative Update 1 for Microsoft System Center Operations Manager (SCOM) 2007 R2 on a gateway server, the agent .msp files are not copied from the agent management directory.
For more information about Cumulative Update 1 for Microsoft System Center Operations Manager (SCOM) 2007 R2, click the following article number to view the article in the Microsoft Knowledge Base:
974144 System Center Operations Manager 2007 R2 Cumulative Update 1 Release Notes |
| Audit Collection Services stops collecting data if the Event Log service uses the automatic backup feature. | The user enables the AutoArchive feature on a domain controller. The Audit Collection Services does not reliably collect forward events from the Security log. |
Released fixes that are not included in this update
The following released Operations Manager 2007 R2 hotfixes are not included in this update because they include SQL Server Transact-SQL scripts, SQL Stored Procedure updates, or cross-platform agent updates. Refer to the individual KB articles for information about how to obtain a hotfix for these issues. For up-to-date information, refer to the following article:
| KB article | Article title |
| 981740 | Updating System Center Operations Manager 2007 R2 to show new properties in a view after updating an MP |
List of known issues for this update
- If you apply this cumulative update on agents that are behind a Gateway server role, the agents are not updated. However, these agents seem to be successfully approved in the Pending Agents pane. This issue occurs after you have performed the following steps:
- Installed System Center Operations Manager 2007 Service Pack 1 (SP1) Update to update Root Management Server and the gateway servers in System Center Operations Manager 2007.
For more information about System Center Operations Manager 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
971541 Description of System Center Operations Manager 2007 Service Pack 1 Update
- Upgraded the gateway servers and Root Management Server in Operation Manager 2007 R2 to the builds from 6278-7221.
- Installed Cumulative Update 1 for Microsoft System Center Operations Manager (SCOM) 2007 R2 on the Root Management Server and on the gateway servers. This is an optional step.
For more information about Cumulative Update 1 for Microsoft System Center Operations Manager (SCOM) 2007 R2, click the following article number to view the article in the Microsoft Knowledge Base:
974144 System Center Operations Manager 2007 R2 Cumulative Update 1 Release Notes
- Installed this cumulative update on the Root Management Server and on the gateway servers.An approved agent is pending behind the gateway servers.
- Approved a pending agent that is located behind a gateway server.
To work around this issue, manually update the agent on the respective computers behind the gateway.
- When you apply the Audit Collection Services update, you may have to restart the computer if a file is being used. Additionally, the following error is returned:
Error 2803: Dialog View did not find a record for dialog
To resolve this issue, restart the computer that has Audit Collection Services installed after you apply the update.
- Agents do not go into the pending folder after Cumulative Update 2 for System Center Operations Manager 2007 R2 is applied on User Account Control (UAC)-enabled Windows, Root Management Server, or gateway servers. To resolve this issue, disable UAC on the server, and then reapply Cumulative Update 2 for System Center Operations Manager 2007 R2.
- The HealthServiceRuntime.dll file is not updated on 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.
Note This issue will be addressed in the next cumulative update.
Installation information
This update must be applied to the computers that host any of the following Microsoft Operations Manager servers or agents:
- Root Management Server
- Management Server
- Gateway Server
- Operations console
- Web Console server
- An agent that was manually installed
- Audit Collection Services server
Be aware that to apply this CU, you must use an account that has the same privileges that were used during the installation of Operations Manager. Updating the Operation Manager Database should be run under an account that has Local Administrator rights and System Administrator (SA) credentials on the database. Updating the RMS should occur under an account with Administrator rights that is a member of the Operations Manager Administrators group.
Note Before you apply this update, we recommend that you back up the Operations database.
Recommended Installation order
We recommend that you install this cumulative update in your environment in the following order:
- Root Management Server
- Manual update of the Operations Manager database together with the included stored procedure file that is discussed later
- Manual import of the Management Pack library that is discussed later
- Secondary Management Servers
- Gateway Servers
- Deploy the agent update to the agents that used a discovery-based installation
- Operations console role computers
Note Select the Run Server Update option from the Software Update dialog box. - Web Console server role computers
- Audit Collection Services role computers
- Apply the agent update to manually installed agents
Installation steps
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-shared folder:
SystemCenterOperationsManager2007-R2CU2-KB979257-X86-X64-IA64-ENU.MSI
-
Then, run this file locally on each applicable computer that meets the conditions that were mentioned earlier.
You can run this file by using either Windows Explorer or by using a command prompt.
Note 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 for the installation of the hotfix.
- On the System Center Operations Manager 2007 Software Update window, select the update option that is appropriate for the role that will be updated.
Recommended steps for applying this cumulative update on a clustered Root Management Server
For more information, visit the following Microsoft website:
File information
This update affects the following files:
- HealthService.dll(version 6.1.7221.15)
- MOMModules.dll(version 6.1.7221.15)
- HealthServiceRuntime.dll(version 6.1.7221.15)
- AdtAgent.exe(version 6.1.7221.15)
- Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll(version 6.1.7221.15)
- Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll(version 6.1.7221.15)
- Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.dll(version 6.1.7221.15)
- Microsoft.Mom.DataAccessLayer.dll(version 6.1.7221.15)
- Microsoft.Mom.UI.Common.dll(version 6.1.7221.15)
- Microsoft.SystemCenter.DatawareHouse.Report.Library.mp 6.1.7221.15
- SetupUpdateOM.exe(version 6.1.7221.15)
- ADTSrvdll.dll (version 6.1.7221.15)
- Microsoft.EnterpriseManagement.OperationsManager.dll (version 6.1.7221.15)
- Microsoft.EnterpriseManagement.OperationsManager.Web.ConsoleFramework.dll (version 6.1.7221.15)
- Microsoft.EnterpriseManagement.UI.Authoring.dll version 6.1.7221.15)
- Microsoft.Mom.DiscoveryDatabaseAccess.dll (version 6.1.7221.15)
- Microsoft.Mom.RecorderBarBHO.dll (Version 1.0.0.2)
- Microsoft.Mom.UI.Components.dll (version 6.1.7221.15)
- MobileWebConsole.dll (version 6.1.7221.15)
- MOMConnector.dll (version 6.1.7221.15)
- MOMModules.dll (version 6.1.7221.15)
- MOMNetworkModules.dll ( version 6.1.7221.15)
- RootWebConsole.dll (version 6.1.7221.15)
- RSSWebConsole.dll (version 6.1.7221.15)
- SRSUpgradeTool.exe (version 6.1.7221.15)
- Microsoft.EnterpriseManagement.OperationsManager.ClientShell.dll (version 6.1.7221.15)
- Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.CommonSetup.dll (version 6.1.7221.15)
- FormatTracing.cmd (Not versioned)
- DiscoveryEntitySProcs.sql (Not versioned)
Manual operations that must be performed after you update the Root Management Server
Note You do not have to repeat the DiscoveryEntitySProcs.SQL installation if you have previously installed Cumulative Update 1 for System Center Operations Manager 2007 R2.
The following supplied management pack must be imported manually by using
Import Management Packs wizard 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:
SystemCenterOperationsManager2007-R2CU2-KB979257-X86-X64-IA64-JPN.MSI
This updated management pack is located in the
ManagementPacks folder of the package installation. This package installation is mentioned in the "Procedure 1" section that is shown later in this article.
Microsoft.SystemCenter.DatawareHouse.Report.Library.mp
The following updated SQL stored procedure file that is included must be manually installed. We recommended that this update be applied to the Operations database after you apply the server update to the Root Management Server. The updated stored procedure is located in the
SQLUpdate folder of the package installation. This package installation is mentioned in the "Procedure 1" section that is shown later in this article.
DiscoveryEntitySProcs.sql
Steps to install DiscoveryEntitySPRocs.sql
To apply this DiscoveryEntitySPRocs.sql database update, you have to follow two separate procedures. If the Root Management Server and Operations database role reside on a single computer, and if the hotfix files are installed on the Root Management Server, you have to follow only Procedure 2.
The following is a summary of these procedures:
- Extract the hotfix files from the package by running the MSI file.
- Use Microsoft SQL Server Management Studio to run commands that are in the supplied Transact-SQL file against the Operations Manager Database server.
Details of these procedures are as follows:
Procedure 1
This procedure can be performed on any computer that has SQL Server Management Studio installed and that can connect to the Operations Manager Operations database server.
To extract the management pack files that are contained in this hotfix, follow these steps:
- Copy the following file to either a local folder or to an available network-shared folder:
SystemCenterOperationsManager2007-R2CU2-KB979257-X86-X64-IA64-locale.MSI
- Run this file for everyone. Note the installation path that is suggested in the installation.
Note The installation path is typically the following:
Program Files\System Center 2007 R2 Hotfix Utility
Procedure 2
- On the Root Management Server, stop the System Center Management service, the System Center Management Configuration service, and System Center Data Access service.
- Log on to the computer that hosts the Operations Manager 2007 database server role as a user who has database owner rights (“dbo” rights) to the Operations Manager 2007 database. To perform the database update remotely, log on to a computer that hosts SQL Server Management Studio as a user who has appropriate "dbo" rights to the Operations Manager 2007 database. Run SQL Server Management Studio.
- In the Connect to Server dialog box, connect to the SQL Server that hosts the Operations Manager database.
- Click New Query on the toolbar.
- From the SQL Editor toolbar, use the Available databases option to select the Operations Manager database. For example, the "OperationsManager" database.
- On the File menu, click Open, and then browse for the path that was noted in Procedure 1 and that contains the DiscoveryEntitySProcs.sql file. Select this 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.
- On the Root Management Server, start the System Center Management service, the System Center Management Configuration service, and the System Center Data Access service.
Updated Support Tools that are included
The following updated file that is located in the
SupportTools folder supports the upgrade from SQL Reporting Services 2005 to SQL Reporting Services 2008:
SRSUpgradeTool.exe
Note 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.