Tuesday, May 15, 2012

[OpsMgr 2007R2] Cumulative Update 6 for System Center Operations Manager 2007 R2 - KB2626076

Cumulative Update 6 contains a number of fixes for Operations Manager 2007 R2, as well as all of the fixes from Operations Manager 2007 R2 CU5. A number of fixes may require manual steps to install.


Version:2007 R2 CU6     Date published:5/14/2012
Language:English




File name
Size
SystemCenterOperationsManager2007-R2CU6-KB2626076-X86-X64-IA64-ENU.MSI1,001.0 MBDownload



Overview

Cumulative Update 6 contains a number of fixes for Operations Manager 2007 R2 including cross platform components, support for IBM AIX 7.1 (POWER), support for Oracle Solaris 11 (x86 and SPARC), as well as all of the fixes from Operations Manager 2007 R2 CU5.

A detailed list of fixes can be found in Knowledge Base article KB2626076.

System requirements

Supported operating systems: Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista

  • Other Software: System Center Operations Manager 2007 R2

Instructions




This article contains a complete description of changes that are contained in Cumulative Update 6 for Microsoft System Center Operations Manager 2007 R2.

Cumulative Update 6 for Operations Manager 2007 R2 includes all previous cumulative updates for Operations Manager 2007 R2 and includes all cross-platform updates.

To download Cumulative Update 6 for Operations Manager 2007 R2, go to the following Microsoft Download Center website:
Download Cumulative Update 6 for System Center Operations Manager 2007 R2 (http://www.microsoft.com/downloads/details.aspx?FamilyID=694147f8-9691-4833-97af-0de918c60141)

Cumulative Update 6 for Operations Manager 2007 R2 resolves the following issues:
  • RMS promotion fails if NetworkName and PrincipalNames are not in sync for agents.
  • UI is limited to only 100 MB for the Memory Usage field in the wizard.
  • Additional OIDs in auth certificate are not processed correctly.
  • AEM creates duplicate computer objects in OpsMgr based on Agents NetBIOS name.
  • Cannot open reporting pane on OpsMgr 2007 R2 remote console.
  • Cannot view schedule for scheduled report.
  • ManagementServerConfigTool with the option "promoterms" fails because it stops polling the SDK Service.
  • OpsMgr reports are failing on Windows 7 with the error: "Cannot initialize report."
  • ACS events have "n/a" as their category in the ACS database.
  • Watch agentless monitoring listener to detect failure to respond.
  • SCOM SDK memory leak on cryptography keys and cryptography contexts.
  • After you click Edit Schedule, a message box appears, and you cannot save the change value.
  • Audit events can be lost when the AdtServer process crashes.
Cumulative Update 6 for Operations Manager 2007 R2 resolves the following cross-platform issues:
  • The installation process for the IBM AIX 6.1 agent incorrectly checks for AIX 5.3 packages.
  • After a system restart, the OpsMgr agent for Solaris may start to run before local file systems are mounted.
  • On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and cannot be monitored.
  • The OpsMgr agent for AIX does not report the arguments for monitored processes.
  • When Microsoft security update MS12-006 is installed on an OpsMgr management server, that management server can no longer communicate with the OpsMgr agent on any Linux or UNIX server.
  • On HP-UX, OpsMgr cannot discover and monitor a logical volume that is composed of more than 127 physical volumes.
Cumulative Update 6 for Operations Manager 2007 R2 adds the following cross-platform features:
  • Support for IBM AIX 7.1 (POWER).
  • Support for Oracle Solaris 11 (x86 and SPARC).
Note The new agents for IBM AIX 7.1 and Oracle Solaris 11 are included in Cumulative Update 6 for Operations Manager 2007 R2. You can download the management packs for these new operating system versions by going to the following Microsoft website:
Issues that are resolved by Cumulative Update 6 for Operations Manager 2007 R2 

SymptomsScenario
Installation of the OpsMgr agent on AIX 6.1 fails with a missing dependency.When you install the OpsMgr agent on AIX 6.1 by using the OpsMgr Discovery Wizard or manually, an error is reported about a missing dependency. This dependency is a file from AIX 5.3 that should not be a prerequisite for installing on AIX 6.1.
After a system restart, the OpsMgr agent on Solaris may fail because it cannot find local files that it needs.The installation process for the OpsMgr agent on Solaris creates a startup entry that does not have a dependency on local file systems being mounted. Therefore, timing variations can cause the agent to run before the local file systems are mounted, with the result that the agent cannot find files that it needs.
On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and monitored.The inability to see LVM disks occurs on all Red Hat Linux 4 and SUSE Linux 9 operating systems that are monitored by using OpsMgr 2007 R2 CU5.
On AIX, the OpsMgr agent does not report the arguments for monitored processes.When you create custom monitors by using the CIM class SCX_UnixProcess, the "Parameters" field is always returned as blank on AIX computers.
When Microsoft security update MS12-006 is installed on an OpsMgr management server, all communication from the management server to the OpsMgr agent on Linux or UNIX results in an HTTP 501 error.Security update MS12-006 made a change in the way data is packaged for transport across SSL/TLS in order to remove a security vulnerability. The change is valid. However, the OpsMgr agent for all Linux/UNIX operating systems makes an incorrect assumption and cannot understand this change. This results in HTTP 501 errors for all communications.
On HP-UX, logical volumes that have more than 127 physical volumes are not discovered and therefore cannot be monitored.When it discovers logical volumes on an HP-UX operating system, the OpsMgr agent for HP-UX receives an internal error when it has a volume that has more than 127 physical volumes. The error results in the disk being ignored and not discovered or monitored.


Please consult http://support.microsoft.com/kb/2626076 for more information about the installation order and additionnal notes


This posting is provided "AS IS" with no warranties.

No comments:

Post a Comment