Systems Center Operations Manager 2007 R2 Connectors Cumulative Update 2

Article translations Article translations
Article ID: 2274165 - View products that this article applies to.
Expand all | Collapse all

On This Page

INTRODUCTION

This update includes all the features and fixes that were discussed in the following Microsoft Knowledge Base article:
975774 Description of System Center Operations Manager 2007 R2 Connectors update

This update also includes the following additional features:

Support for Remedy 7.5

This update enables support for Remedy 7.5 with the Operations Manager 2007 R2 Connector for Remedy.

Support for HP Operations Manager for UNIX version 9

This update enables support for HP Operations Manager for UNIX v9 when you use the Operations Manager 2007 R2 Connector for HP Operations Manager. The Connector supports HP Operations Manager for UNIX version 9 on the following platforms:
  • HPUX 11i v3 Itanium
  • Solaris 10 SPARC
  • RedHat Enterprise Linux 5.2 x64

This update also includes fixes for the following additional issues:

Incorrect dates are passed to the remote system by the Connector

This update fixes an issue in which the Connector performs an incorrect date conversion and forwards the incorrect date to the remote system.

Product Knowledge is not forwarded when the locale is Canadian English

This update fixes an issue in which the Product Knowledge is not forwarded from Operations Manager to the remote system if the locale on the Operations Manager server is set to Canadian English.

MORE INFORMATION

Update information

How to obtain this update

The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download
Download the update package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this update, you must be running one of the following operating systems:
  • Connector Service and Configuration UI components:
    • Windows Server 2003 Service Pack 1 (SP1) or Service Pack 2 (SP2)
    • Windows Server 2008
  • Windows-based remote system components:
    • Windows Server 2003 SP1 or SP2
    • Windows Server 2008
    • .NET Framework version 2
  • UNIX-based remote system components:
    • HP Operations Manager Connector:
      • HP-UX 11i v3 (IA-64)
      • HP-UX 11i v3 (PA-RISC)
      • HP-UX 11i v2 (IA-64)
      • HP-UX 11i v2 (PA-RISC)
      • Solaris 10 SPARC
      • RedHat 5.2/5.3 x64 (HP Operations Manager for UNIX v9 only)
    • IBM Tivoli Enterprise Console Connector:
      • IBM AIX 5L 5.3, Technology Level 6, SP5 (PowerPC)
      • Solaris 10 SPARC
    • Universal Connector:
      • IBM AIX 5L 5.3, Technology Level 6, SP5 (PowerPC)
      • HP-UX 11i v3 (IA-64)
      • HP-UX 11i v3 (PA-RISC)
      • HP-UX 11i v2 (IA-64)
      • HP-UX 11i v2 (PA-RISC)
      • Solaris 10 SPARC
      • Red Hat Enterprise Linux Server release 5.1 (Tikanaga)
      • SUSE Linux Enterprise Server 10 SP1 (i586)


    Note The Connector system requirements are the same as the system requirements that are documented in the Connectors Predeployment Considerations. This can be found in the Operations Manager 2007 R2 Connectors Deployment Guide. For more information, refer to the “More information” section.

Installation instructions

Installation of the OM2007R2Connectors-KB2274165.exe file


Download OM2007R2Connectors-KB2274165.exe and then follow these steps on both the Connector Service and on the Windows-based Interop Providers to install this update package:
  1. Run the OM2007R2Connectors-KB2274165.exe file. Updated files are extracted to the following folder:
    %Program Files%\OM2007R2Connectors-KB2274165
  2. In the OM2007R2Connectors-KB2274165 folder, find and then run the SetupUpdateInterop.exe file.
  3. Click Yes to accept the License Terms for the System Center Operations Manager 2007 R2 Connectors update.
  4. The installation process displays the release notes. Run the Connectors Setup Wizard, and install the Connector and provider updates.
  5. Click Finish to end the installation.
  6. The Connectors Setup Wizard displays one of the following messages according to the component that is installed on the system:
    Connector Patch was successfully installed
    Provider Patch was successfully installed
Installation of Remedy 7.5 Support


Prerequisites to installing Remedy 7.5 Support:
  • The Remedy 7.5 Provider must be installed on a Windows-based server.
  • You must install the Remedy 7.1 User application on the same server as the Remedy 7.5 Provider.
To install the Remedy 7.5 Provider, follow these steps:
  1. In the Remedy7.5 Provider directory of the update package folder, find and then run the SciProviderSetup.msi file.
  2. Read the License Agreement, and then click Yes to accept the License Agreement.
  3. On the Select Provider page, select Install BMC Remedy 7.1/7.5 Provider, and then click Next.
  4. On the Custom Setup page, make sure that the Remedy 7.1/7.5 Provider is selected to be installed, and then click Next.
  5. On the Ready to install Microsoft Operations Manager 2007 Interop Provider page, click Install.
  6. Click Finish to complete the installation.
Notes
  • You have to apply this update after you install the Connector Service for the BMC Remedy 7.5 Connector through the Connector installation media.
  • You have to configure the BMC Remedy AR Server to work with the Connector.
Installation of HP Operations Manager for UNIX v9 Support on RedHat


Make sure that you install the Cross Platform core before you start. For more information about how to download the latest version of the Cross Platform core from the Operations Manager 2007 R2 Cross Platform Cumulative Update, refer the "More information" section.

To install the provider for HP Operations Manager on a RedHat server, follow these steps:
  1. Run the following command to install the new provider:
    rpm –i MSFTscinteropOvo-<build-number>.rhel.5.x86_64.rpm
  2. When the installation is complete, perform the following post-installation steps :
    • Run the following command to input the password that is required for 'opc_adm':
      /opt/microsoft/scx/bin/scicrypt <password>
    • Run the following command to start the Interop OVO daemon (scinteropd):
      /etc/init.d/scx-scinteropd start
If you upgraded HP Operations Manager for UNIX to v9 on another platform, run the following command to uninstall the existing provider and reinstall the new provider.
Installation of this update for the UNIX Interop Providers
  1. Uninstall the Interop Provider by running the appropriate command.

    Universal Connector
    • For AIX:
      installp –u MSFTscinteropUnv.rte
    • For HPUX 11iv3 (IA-64): 
      swremove MSFTscinteropUnv
    • For HPUX 11iv2 (IA-64): 
      swremove MSFTscinteropUnv
    • For HPUX 11iv3 (PA-RISC):
      swremove MSFTscinteropUnv
    • For HPUX 11iv2 (PA-RISC):
      swremove MSFTscinteropUnv
    • For Solaris 10 SPARC:
      pkgrm MSFTscinteropUnv
    • For RHEL 5.1:
      rpm –e MSFTscinteropUnv
    • For SLES 10:
      rpm –e MSFTscinteropUnv

    Connector for IBM Tivoli Enterprise Console
    • For AIX:
      installp –u MSFTscinteropTec.rte
    • For Solaris 10 SPARC:
      pkgrm MSFTscinteropTec

    Connector for HP Operations Manager for Unix
    • For HPUX 11iv3 (IA-64): 
      swremove MSFTscinteropOvo
    • For HPUX 11iv2 (IA-64): 
      swremove MSFTscinteropOvo
    • For HPUX 11iv3 (PA-RISC):
      swremove MSFTscinteropOvo
    • For HPUX 11iv2 (PA-RISC):
      swremove MSFTscinteropOvo
    • For Solaris 10 SPARC:
      pkgrm MSFTscinteropOvo
  2. Install the new Interop Provider by running the appropriate command.

    Universal Connector
    • For AIX:
      gzip –d /tmp/scinterop-<build-number>.aix.5.3.pcc-unv.lpp.gz
      installp -X -d /tmp/scinterop-<build-number>.aix.5.3.ppc-unv.lpp MSFTscinteropUnv.rte
    • For HPUX 11iv3 (IA-64):  
      uncompress /tmp/scinterop-<build-number>.hpux.11iv3.ia64-unv.depot.Z
      swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.ia64-unv.depot MSFTscinteropUnv
    • For HPUX 11iv3 (PA-RISC):
      uncompress /tmp/scinterop-<build-number>.hpux.11iv3.parisc-unv.depot.Z
      swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.parisc-unv.depot MSFTscinteropUnv
    • For Solaris 10 SPARC:
      gzip –d /tmp/scinterop-<build-number>.solaris.10.sparc-unv.pkg.gz
      pkgadd -d /tmp/scinterop-<build-number>.solaris.10.sparc-unv.pkg MSFTscinteropUnv
    • For RHEL 5.1:
      rpm –i MSFTscinteropUnv-<build-number>.rhel.5.x86.rpm
    • For SLES 10:
      rpm –i MSFTscinteropUnv-<build-number>.suse.10.x86.rpm

    Connector for IBM Tivoli Enterprise Console
    • For AIX:
      gzip –d /tmp/scinterop-<build-number>.aix.5.3.pcc-tec.lpp.gz
      installp -X -d /tmp/scinterop-<build-number>.aix.5.3.ppc-tec.lpp MSFTscinteropTec.rte
    • For Solaris 10 SPARC:
      gzip –d /tmp/scinterop-<build-number>.solaris.10.sparc-tec.pkg.gz
      pkgadd -d /tmp/scinterop-<build-number>.solaris.10.sparc-tec.pkg MSFTscinteropTec

    Connector for HP Operations Manager for Unix
    • For HPUX 11iv3 (IA-64): 
      uncompress /tmp/scinterop-<build-number>.hpux.11iv3.ia64-ovo.depot.Z
      swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.ia64-ovo.depot –x ask=true MSFTscinteropOvo
    • For HPUX 11iv3 (PA-RISC):
      uncompress /tmp/scinterop-<build-number>.hpux.11iv3.parisc-ovo.depot.Z
      swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.parisc-ovo.depot –x ask=true MSFTscinteropOvo
    • For Solaris 10 SPARC:
      gzip –d /tmp/scinterop-<build-number>.solaris.10.sparc-ovo.pkg.gz
      pkgadd -d /tmp/scinterop-<build-number>.solaris.10.sparc-ovo.pkg MSFTscinteropOvo
    • RedHat 5.2/5.3 (x64):
      rpm –i MSFTscinteropOvo-<build-number>.rhel.5.x86_64.rpm
Configuring the BMC Remedy AR Server version 7.5


To create an AR Server user for Operations Manager, follow these steps:
  1. Use an account that has application configuration permissions to open the BMC Remedy User application.
  2. Open the Remedy Application Administration Console.
  3. Click Create next to People Configuration and enter the following information:

    First Name = Operations
    Last Name = Manager
    Client Type = Office Based Employee
    Contact Type = Tech Support
    Company = <Your Company>
    Organization = <Your Organization> (This is an optional field)
    Department = <Your Department> (This is an optional field)
    Support Staff = Yes
    E-mail Address = <Generic email address >(Required for user type)
    Site = <Appropriate site> (Select the1 appropriate site from the drop-down list)
    Login Name = opsmgr
    Password = Manager
    License Type = Fixed
    Full Text License Type = None
    Application Permissions = Incident Master, AR System Administrator (to have access to CI data, Asset Viewer will automatically be assigned) and Incident User
    User must be a member of any of the support groups that has the availability set to "No"
  4. Click Add to create the record.


Important: The opsmgr Login Name must be a member of the Remedy Administrators group.

To create Operations Manager Alert ticket categorizations, follow these steps:
  1. Open the Remedy Application Administration Console.
  2. Click Create next to Operational Category Configuration and enter the following information:
    Operational Categorization Tier 1 = "Monitoring"
    Operational Categorization Tier 2 = "OpsMgr"
    Operational Categorization Tier 3 = "Alert"
    Status = "Enabled"
    Make Category available for = "Current company"
  3. Click Add to create the record.

Operations Manager 2007 R2 Connectors Interface Forms and Filters for Remedy ARS


When you install the Interop Provider component in the Remedy ARS environment, a file that contains the Operations Manager 2007 R2 Interface form, together with other forms and filters, is copied to the designated Remedy AR Server. These Remedy ARS forms and filters must be imported to enable the flow of Operations Manager 2007 R2 alerts to Remedy ARS tickets.

The .xml file that contains these forms and filters is copied to the Interop Provider installation folder. The file for Remedy ARS 7.1 is located in the following directory:
C:\Program Files\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to BMC Remedy AR System 7.1 Provider\

To import Connector Interface Forms and Filters on a Remedy 7.5 server only, follow these steps:
  1. Use an account that has administrative permissions to log on to Remedy Administrator.
  2. Make sure that any existing Operations Manager Connectors forms or filters are removed. To do this, open all objects in the Remedy Developer Studio, double-click Forms and Filters, and then select and delete all forms that begin with "SCI:" in the Forms or the Filters pane.

    Important If you want to keep existing Work Flow ticket ID information on forwarded tickets, do not delete the SCI:OMI:IncidentSearch form.
  3. Select File and Import from the menu in the Remedy Developer Studio.
  4. In the Import dialog box:
    1. Open the BMC Remedy Developer Studio by clicking the right arrow button that is next to it.
    2. Select Object Definitions and then click the Next button.
    3. Select the appropriate server and then click the Next button.
    4. Browse and then select the "SCIOpsMgr2007Interface-71.xml" file.
  5. In the Object Selection dialog box:
    1. Use standard Windows selection methods to select all objects.
    2. Click Finish.
    3. Verify the installation process. The number of the imported object is as follows:
      Forms: 4
      Filters: 35
      Filter Guides: 2
      Menus: 1


To import the State Transitions data file, follow these steps:
  1. Open the BMC Remedy Data Import tool, and log on with administrator permissions.
  2. Select File from the menu, and then select New Mapping.
  3. In the Source Data File field, browse and then select the "SCIState Transitions-71.xml" file from the Provider installation file folder.
  4. Select the target server.
  5. Select the target form name that is called SCI:StateTransitions.
  6. Click Auto Map. All form fields should be displayed in the Field Value Mappings table.
  7. Select Import from the menu, and then select Start Import.
  8. Verify that 56 records are imported.

Restart requirement

You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Connectorconfigdialog.exe6.1.7000.13876,80009-Jul-201022:49x86
Connectorconfiguicommon.dll6.1.7000.13884,99209-Jul-201022:49x86
Connectorservice.exe6.1.7000.138262,14409-Jul-201022:49x86
Interop.wsmanautomation.dll1.0.0.023,06415-Jul-200921:50x86
Microsoft.systemcenter.interop.ui.dll6.1.7000.138400,89609-Jul-201022:49x86
Microsoft.systemcenter.interop.ui.remedy.dll6.1.7000.138141,82409-Jul-201022:49x86
Microsoft.systemcenter.interop.ui.hpovo.dll6.1.7000.138114,17609-Jul-201022:49x86
Microsoft.systemcenter.interop.ui.tec.dll6.1.7000.138103,93609-Jul-201022:49x86
Microsoft.systemcenter.interop.ui.unv.dll6.1.7000.13882,43209-Jul-201022:49x86
Scicert.exe6.1.7000.13871,95209-Jul-201022:41x86
Scicli.exe6.1.7000.13816,89609-Jul-201022:49x86
Scinteropd.exe6.1.7000.6983,80025-Sep-200923:04x86
Scinteropovo.dll6.1.7000.69332,12025-Sep-200923:06x86
Scinteropremedy63.dll6.1.7000.58375,12815-Jul-200922:15x86
Scinteropremedy71.dll6.1.7000.138376,59209-Jul-201022:41x86
Scinteroptec.dll6.1.7000.69287,06425-Sep-200923:06x86
Scinteropunv.dll6.1.7000.69279,38425-Sep-200923:06x86
Scinteropprov.dll6.1.7000.138300,30409-Jul-201022:41x86

MORE INFORMATION

For more information about Connectors Predeployment Considerations, visit the following Microsoft website:
General information about the Connectors Predeployment Considerations
For more information about how to download the latest version of the Cross Platform core from the Operations Manager 2007 R2 Cross Platform Cumulative Update, visit the following Microsoft website: 
Download information about the latest version of the Cross Platform core from the Operations Manager 2007 R2 Cross Platform Cumulative Update
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 2274165 - Last Review: January 30, 2012 - Revision: 2.0
APPLIES TO
  • Microsoft System Center Operations Manager 2007 R2
Keywords: 
atdownload kbexpertiseinter kbsurveynew kbfix KB2274165

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com