OpsMgr 2007 R2 Connectors - Cumulative Update 2 shipped


This is an update, if you use the Microsoft branded OpsMgr R2 connectors.

 

KB Article:  http://support.microsoft.com/?kbid=2274165

Download location:  http://www.microsoft.com/downloads/details.aspx?FamilyID=87c27d91-4549-4169-a87a-ca88e4136e4f&displaylang=en

 

This is a cumulative update – which also includes the fixes in the previously shipped update, 975774.

 

Changes in this update:

 

Support for HP Operations Manager for UNIX v9

This update enables support for HP Operations Manager for UNIX v9 with the Operations Manager 2007 R2 Connector for HP Operations Manager.  The Connector supports HP Operations Manager for UNIX v9 on the following platforms:

  • HPUX 11i v3 Itanium
  • Solaris 10 SPARC
  • Red Hat Enterprise Linux 5.2 x64

Support for BMC Remedy AR System 7.5

This update enables support for BMC Remedy ARS 7.5 with the Operations Manager 2007 R2 Connector for Remedy.  This includes Remedy ARS 7.5 installed on Red Hat and SLES platforms. 

Addressed incorrect dates passed to the remote system by the connector

The Connector performed an incorrect date conversion and forwarded the incorrect date to the remote system.  

Addressed Product Knowledge not forwarded when the locale is Canadian English

If the locale on the Operations Manager server is set to Canadian English, the Product Knowledge was not be forwarded from Operations Manager to remote system.

 

This CU2 update includes all fixes from the previous update, 975774:

 

Issue 1: Potential high CPU usage of HP OVO Event Consumer for Windows (scinteropd.exe)

The Scinteropd.exe process of HP OVO Event Consumer for Windows sometimes increases CPU usage to a very high level. This problem occurs only in System Center Operations Manager 2007 R2 Connectors for HP Operations Manager on Windows. It occurs in all language versions of the connectors.

Issue 2: Synchronization issue in HP OVO Connector

HP Operations Manager and System Center Operations Manager 2007 R2 may be in an asynchronous state when alerts are forwarded that have already been resolved. Open events are still present in HP Operations Manager even though the corresponding alerts in System Center Operations Manager 2007 R2 are already resolved.

Issue 3: Remedy connectors do not populate the Computer Name and Domain fields

When an alert is forwarded from System Center Operations Manager 2007 R2 to Remedy, the Computer Name field and the Domain field are left blank in the Remedy notes field. This issue occurs in the release version of System Center Operations Manager 2007 R2 Connector for Remedy 6.3 and Remedy 7.1.

Issue 4: Unresponsiveness of the Interop provider when an Enterprise Management Service (EMS) API call returns an error

The Interop provider may stop responding and not recover when an API calls to the EMS and returns an error.
Note Usually, the API calls to Remedy.
This issue typically occurs when large localized text strings in the Custom Field Alert properties are forwarded to Remedy. However, it can also occur with other properties.
Note This issue is associated with the Remedy connector. However, it might also occur with other connectors. Therefore, the update provided in this article includes the updated Unix Interop providers. However, do not apply the updated Unix Interop providers unless you are instructed to do this by a support professional. To apply the updated Unix Interop providers, you can uninstall the Interop provider and reinstall the new Unix Interop provider packages that are included in this update package.

 

So – if you feel you might be impacted by any of these issues, or desire the added functionality of the new system versions to connect to – grab and apply this update.

Comments (2)

  1. Arun Nadiga says:

    Hi Kevin,

    We are using SCOM 2007 R2 CU3 and using Remedy Connector; we have issue where connector was unable to send the NetBIOS Computer Name and NetBIOS Domain Name values to Remedy, so we have applied KB2274165 Patch (SCOM 2007 R2 Connector Cumulative Update), but we are still facing the same issue (unable to see any values in NetBIOS Computer Name and NetBIOS Domain Name)

    Arun Nadiga

    arunnadiga@gmail.com

  2. Dan_IT says:

    If you are using Remedy 6.3 it is necessary to install the CU's in order (CU1 and then CU2). This should be the only time this is required but it seems that there was a regression in the CU2 release where it included the old version of the 63.dll on the provider that did not include the fix so if you go straight from RTM to CU2 you will still get this issue.

Skip to main content