System Center Operations Manager 2007 R2 Cumulative Update 3 released

  • Article

Today we released the System Center Operations Manager 2007 R2 Cumulative Update 3 with some valuable fixes (KB2251525)

CU3 includes all the fixes from CU1 and CU2 and you therefore only need to apply CU3 to apply all fixes included in these 3 cumulative updates.

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

More information can be found in the KB: https://support.microsoft.com/kb/2251525

To download Cumulative Update 3 for System Center Operations Manager 2007 R2, visit the following Microsoft Web site: https://www.microsoft.com/downloads/details.aspx?FamilyID=9f1e1154-52ae-42df-aeea-b3ee83247e6a

Kevin Holman has a great blog about the installation of the update: https://blogs.technet.com/b/kevinholman/archive/2010/10/04/opsmgr-2007-r2-cu3-rollup-hotfix-ships-and-my-experience-installing-it.aspx

If you're looking for commandline deployment of the CU3, go have a look at this blog, also from Kevin Holman: https://blogs.technet.com/b/kevinholman/archive/2010/10/12/command-line-and-software-distribution-patching-scenarios-for-applying-an-opsmgr-cumulative-update.aspx

At one customer, the installation failed when it tried to start the SDK service after the first update. This error has been seen before, and is caused by a timeout problem. All I did to make it work, was to follow this KB:https://support.microsoft.com/kb/922918 and set the ServicesPipeTimeout to 3 minuttes (180000 ms) and rebooted the server. After that I could apply the CU3 with success.