Cumulative Update 3 for Microsoft System Center Operations Manager (SCOM) 2007 R2 includes all preceding cumulative updates for System Center Operations Manager 2007 R2. Additionally, Cumulative Update 3 resolves the following issues:
- Feature addition: Azure Application Monitoring
- Feature addition: Parameter Extraction in Web Application Synthetic Transactions
- Some ACS reports do not work as expected in Windows Server 2008
- SCOM 2007 SP1 Reports do not run after a shared Data Warehouse is upgraded to SCOM 2007 R2
- The SDK Services stops working due to an unhandled exception, and the operations console becomes unresponsive
- Multi-selection in the alert view is not maintained during a view refresh
- The operations console stops working when creating an override on the cluster resource group monitor
- When Agentless Exception Monitoring (AEM) is set up to use SharePoint, reports from Watson are blocked
- The Operations Manger Console stops working when a high number of instances of State Views or Alert Views are left open for extended durations
- Upgrading MPs that include new properties may not recreate views correctly
- The total transaction response performance counter in URL monitoring is not accurate
- MPs with empty knowledge elements cannot be imported in Operations Manager 2007 R2
- Monitoringhost.exe does not work reliably on Windows 2003 SP2 X64 Domain Controllers
- Alerts using the “Specific Time Period” criteria are not included during automatic alert view refresh
- ACS forwarders with 15 character names in workgroups are unable to communicate with the ACS collector
- Language packs authored for a previous version of an MP cannot be imported once an updated MP is released
- Language Pack import fails if the MP contains strings which are not contained in the English Management Pack
- Generic performance reports consume a large amount of temporary database space and can fail for Windows Server 2003 Computer Groups
- When using a remote console the notification wizard does not work in certain situations
- The SDK service may stop working due to an arithmetic overflow error in very rare circumstances
- The notification scheduler does not compensate correctly for different time zones
Provides the ability to discover the structure of a Microsoft Azure Application and to monitor the performance and availability of the application.
Feature addition: Parameter Extraction in Web Application Synthetic Transactions
Provides the ability to extract parameters in Web Application Synthetic Transactions. Data from HTTP responses within a web application can request and reuse the parameter in subsequent web application requests.
|Some ACS reports do not work as expected in Windows Server 2008||The user runs any of the following list of reports and finds that no data is returned for Windows 2008 Servers:|
The reports do not account for the changes in logging in versions of Windows Server later than Windows Server 2003. These reports are now registered in the Target User property rather than Primary User Property.
|SCOM 2007 SP1 Reports do not run after a shared Data Warehouse is upgraded to SCOM 2007 R2||The user has deployed the Operation Manager 2007 SP1 infrastructure, and is in the process of upgrading to SCOM 2007 R2. A Management group is upgraded to SCOM 2007 R2. Any reports run from the new management group fail with a “Parameter Validation Error.”|
|The SDK Services stops working due to an unhandled exception, and the operations console becomes unresponsive||During regular monitoring, the operations console freezes. The user finds that the SDK has hung due to an unhandled exception, and restarts it. After the operations console is restarted, the operations console becomes responsive once again.|
|Multi-selection in the alert view is not maintained during a view refresh||The user selects multiple alerts in the alert view. The automatic refresh of the alert view occurs. Some of the previously selected alerts are replaced by new alerts.|
|The operations console stops working when creating an override on the cluster resource group monitor||The user imports the Windows Cluster Management MP, and navigates to Authoring->Management Pack Objects->Monitors. The Resource Group Monitor targeting Cluster Resource Group is selected. The user selects Override the monitor for all objects of class: Cluster Resource Group. After attempting to override the Maintenance Mode Value, the console stops working.|
|When AEM is set up to use SharePoint, reports from Watson are blocked||You deploy SharePoint, and configure AEM to work on the computers that are running SharePoint. Watson reporting is also enabled for those SharePoint sites. However, Watson data is not sent to Microsoft.|
|The Operations Manger Console stops working when a high number of instances of State Views or Alert Views are left open for extended durations||The user has set up multiple alert views / state views for permanent display on various displays. After running these views for an extended period of time, the user receives a “Could not continue scan with NOLOCK due to data movement” error. The console does not resume operation until the SDK service is restarted.|
|Upgrading MPs that include new properties may not recreate views correctly||The user upgrades an MP whose number of properties has been changed from 5 to 10. Views showing all properties continue to only show 5 properties as opposed to the expected 10.|
|The total transaction response performance counter in URL monitoring is not accurate||The user is monitoring a specific URL, and examines the response time performance. The data given is the aggregation of all individual responses, and does not account for responses received in parallel.|
|MPs with empty knowledge elements cannot be imported in Operations Manager 2007 R2||The user attempts to import an MP, but is not able to do so due to the enforcement of the best practice for no empty MP knowledge elements. Certain legacy MPs that were created before this best practice was enforced (for example, MDM) are no longer importable.|
|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. However, Audit Collection Services does not reliably collect forward events from the Security log.|
|Monitoringhost.exe does not work reliably on Windows 2003 SP2 X64 Domain Controllers||Monitoringhost.exe throws Event ID 4000 in the operations manager log on Windows Server 2003 SP2 X64 Domain Controllers, and must be restarted on a regular basis.|
|Alerts using the “Specific Time Period” criteria are not included during automatic alert view refresh||The end user creates a new alert using the “Specific Time Period” criteria. After selecting the alert view, an alert matching this criterion is generated. When the view refreshes automatically, this alert is not shown.|
|ACS forwarders with 15 character names in workgroups are unable to communicate with the ACS collector||The user configures a workgroup machine with a computer name of 15 characters or more. After installing the ACS forwarder and the certificate, Event 4369 is observed in the Event Log. The ACS forwarder is not able to communicate with the collector.|
|Language packs authored for the previous version of an MP cannot be imported once an updated MP is released||The end user imports a new version of an MP, and wants to import the language pack as well. However, the new language pack for this MP is not yet available. Attempting to import the old language pack fails because new strings have not yet been localized in the old language pack.|
|Language Pack import fails if the MP contains strings which are not contained in the English Management Pack||The end user attempts to import a language pack for an MP. However, the language pack defines a string which was left blank in the English MP. This causes the import operation to fail.|
|Generic performance reports consume a large amount of temporary database space and can fail for Windows Server 2003 Computer Groups||The end user has installed multiple Window Server 2003 agents. When attempting to run performance reports, the temporary database can grow up to 200GB prior to producing the report.|
|When using a remote console the notification wizard does not work in certain situations||The end user attempts to create a notification subscription for a remote console by using one of the following conditions:|
|The SDK service may stop working due to an arithmetic overflow error in very rare circumstances||In very rare circumstances, the end user may observe Event ID 26319 in the event log, indicating an arithmetic overflow error. This can occur on 64bit systems running with a high number of domain trusts. Impacted systems are generally configured with 8GB of RAM or higher.|
|The notification scheduler does not compensate correctly for different time zones||The end user sets notifications for subscribers in different time zones, and configures their schedule. However, the schedule is not respected correctly. The scheduler double compensates for time zone differences.|
|A management pack does not show the correct properties in some views after you import the management pack||CU3 includes KB981740. |
You import a new management pack that contains new properties for certain views on a computer that is running System Center Operations Manager 2007 R2. After you do this, you may receive the following error message:
Additionally, you find that the new properties are missing from a specific view.
An object of type Variable with ID Number was not found
The following released Operations Manager 2007 R2 hotfix is not included in this update because it includes SQL Server Transact-SQL scripts, SQL Stored Procedure updates, or cross-platform agent updates. Refer to the individual KB article for information about how to obtain a hotfix for this issues. For up-to-date information, refer to the following article:
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.
- 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 3 for System Center Operations Manager 2007 R2 is applied on User Account Control (UAC)-enabled Windows servers, Root Management Server servers, or gateway servers. To resolve this issue, disable UAC on the server, and then reapply Cumulative Update 3 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.This fix will not be supported on Windows 2000 based computers, and will not be addressed in upcoming CUs.
- The server patch may fail and roll back on Virtual Machines with less than 2GB of memory. This behavior is inconsistent, and is addressed by reapplying the patch.
- The final dialog box is titled "Error", and provides information as to where to identify errors that may have been encoutered during the install process. The correct title for this dialog box is "Information". We will address this in the next Cumulative Update.
- CU3 Rollback / SDK Start Failure: In some cases, Cumulative Update 3 (CU3) rolls back multiple times or the SDK Service does not restart after a rollback of CU3. This is caused by a service timing issue that affects a small percentage of computers. If you encounter this issue, follow the steps that are outlined in Microsoft Knowledge Base article KB992918, and then set the ServicesPipeTimeout to 120000. Restart the affected computer, and then reapply CU3. The CU3 installer may show an error or warning during the installation process. If this occurs, you have to click through the error or warning.
- Pushed agents do not show the correct patch level when looking at the "Patch List" view for agent machines. Two entries should exist for Cumulative Update 3 in this view. If two entries are not present, reboot the agent machine, and select "Repair" for the respective agent through the Operations Console.
- PRO Integration: PRO Tips do not function correctly after CU3 is installed. Event ID 26319 is thrown in the Operations Manager Event Log, and PRO Tips are not shown. If you are leveraging PRO Tips, we advise skipping CU3 and applying CU4 when it is released. Please contact your CSS representative if you have already applied CU3 and are experiencing this issue.
- Service Restart / Machine Reboot: In some cases after you apply CU3, Restart Manager may restart certain services. If you encounter this issue, a machine reboot, or manual restart of the Health Service may be required. This issue has been addressed in CU5.
Installation informationThis 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
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 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 in this article
- Manual import of the Management Packs that is discussed later in this article
- 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
Note: When updating a component from the installer splash screen, it is necessary to go through three patch installers. After selecting the component to update (ie: RMS) each installer will launch and will require clicking "Finish" upon completion. The next installer will start automatically. This is by design, as CU3 consists of three patches (SCOM 2007 R2 Patches, Localized Patches, and Cross-Platform Patches)
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-R2CU3-KB2251525-X86-X64-IA64-ENU.MSI
- 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 the hotfix to be installed.
- 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:
Manual operations that must be performed after you update the Root Management Server and Data Warehouse
Running the provided SQL ScriptsThis update contains fixes that must be manually applied. The “\SQLUpdate\CU3_DataWarehouse.sql” and “\SQLUpdate \CU3_Database.sql” files will need to be run manually against the OM data warehouse (OperationsManagerDW) and the OM database (OperationsManager), respectively.
Important If this is the first time you are running a Cumulative Update, you will also need to apply ”\SQLUpdate \DiscoveryEntitySProcs.sql” on the Operations Manager database first. It is not necessary to apply DiscoveryEntitySProcs.sql otherwise.
To perform these steps please use an account with Local Administrator rights and System Administrator (SA) credentials on the database instances. You will also need to manually import all MPs that are provided in the ManagementPacks folder to complete the install.
- Log on to the computer that hosts the Operations Manager 2007 database as a user who 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 as a user who has appropriate "SA" 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. 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, and then browse for the path where the msi installer placed the appropriate files. Select “\SQLUpdate \CU3_Database.sql”, 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.
- Repeat Steps 1 through 8, connecting to the Operations Manager data warehouse, and by running “CU3_DataWarehouse.sql.”
Importing the provided Management Packs
The management packs supplied in the ManagementPacks folder must be imported manually by using the 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:
Updated Support Tools that are included in the cumulative updateThe following updated file that is located in the SupportTools folder supports the upgrade from SQL Reporting Services 2005 to SQL Reporting Services 2008:
Advanced Installation Instructions - CU3 Command Prompt Installation
The installer (Hotfix Utility) downloaded from this site unpacks the bootstrapper and necessary MSPs to update System Center Operations Manager 2007 R2 to Cumulative Update 3. It is preferable to run the Hotfix Utility on each computer and deploy Cumulative Update 3 via the GUI interface invoked once this is complete. However, it is also possible to bypass multiple installations of the hotfix utility, and deploy Cumulative Update 3 directly by copying the unpacked directory and files (.\System Center 2007 R2 Hotfix Utility\KB 2251525\) to the appropriate computers directly.
If you choose to install Cumulative Update 3 directly via the command prompt, the following command should be used:
Advanced Installation Instruction - Updating manually installed agentsCU3 manually installed agents can be updated without using the full contents of this package. To deploy updates to an agent using the minimal number of required files:
- Install the hotfix utility using the process detailed above.
- Copy all components except ACS, Gateway, ManagementPacks, SCX-Gateway, SQLUpdate, Support Tools and Update Folders, as well as the msp files in the root folder (KB2251525) of the installer
- Push the new folder to all agent machines
- Run the following command
Note: "ENU" in the above command will need to be replaced by the language code of the CU3 package you have downloaded.