Integrate > Microsoft SCOM > Install

Install

Before installing OpxCx for Microsoft SCOM, go through a list of the supported operating systems and consider the prerequisites. Determine whether the product will operate in a standalone setup or it will be used in a High Availability (HA) setup.

For non-HA deployment scenario, it is not supported to connect multiple connectors to the same SCOM domain manager.
For HA setup, please make sure to install and configure Operations Connector manually on all nodes comprising the Operations Connector HA cluster.

Before you start with the installation process, familiarize yourself with the conventions listed in the table in this section.

Installation of OpsCx for Microsoft SCOM consists of several tasks. Please note that the tasks are applicable for both standalone and High Availability setups. Complete them in the following order:

  1. Obtain the assembly files from the Microsoft System Center Operations Manager SDK.

  2. Optional: Install the Microsoft SCOM Built-In Diagnostics Loader Stub.

  3. Obtain and install Operations Connector for Microsoft SCOM.

  4. Install the event backward synchronization script.

    This task is mandatory only if you plan to collect Microsoft SCOM events.

  5. Install the OMi topology synchronization package and the OMi content pack for metrics. See Installing OMi Content Pack for Microsoft SCOM topic.

    Although this task is mandatory only if you plan to collect Microsoft SCOM topology or Microsoft SCOM metrics, or if you intend to enrich the collected Microsoft SCOM events with topology-related information, service provider strongly recommends that you perform it in any case.

OpsCx for Microsoft SCOM does not support upgrade scenarios. If you have a previous product version installed on the target host, remove it first. Service provider recommends that all relevant data is backed up prior to the removal.

Conventions Used in the Installation, Configuration, and Other Procedures

The following placeholders are used in the instructions throughout this document. When performing the steps specify the actual value in place of each placeholder.

Placeholder Meaning (Default) Values, Example, Notes
<Version> Product version string of OpsCx for Microsoft SCOM: major version, minor version, and build number. It is embedded in the filename of the installation package.

Example:
03.02.014

This string represents the version 3.02 and the build number 14.

<OvInstallDir>

Program installation directory of Operations Agent that is jointly used by Operations Connector and OpsCx for Microsoft SCOM.

Default value:
C:\Program Files\HP \
\HP BTO Software

<OvDataDir>

Data installation directory of Operations Agent that is jointly used by Operations Connector and OpsCx for Microsoft SCOM.

Default value:
C:\ProgramData\HP\HP BTO Software The C:\ProgramData directory is hidden by default.
<SCOMHome> Program installation directory of Microsoft SCOM.

Default value:

C:\Program Files\Microsoft System Center <version>\Operations Manager

<SDKAssemblyFilesDir> Directory on the Operations Connector host where you temporarily store the Microsoft SCOM SDK assembly files. There is no default value.
<OMiHome> Directory where Operations Manager i is installed.

Default value (Windows):
C:\HPBSM

Value (Linux):
/opt/HP/BSM

Related topics

Support Matrix

Prerequisites

Obtaining the Microsoft SCOM SDK Assembly Files

Installing the Microsoft SCOM Built-In Diagnostics Loader Stub

Installing OpsCx for Microsoft SCOM

Post installation tasks

Installing OMi Content Pack for Microsoft SCOM

Send Help Center feedback