Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Connector10.11

Integrate > Microsoft SCOM > Install > Prerequisites

Prerequisites

The sections that follow list the prerequisites that need to be fulfilled to enable installation of OpsCx for Microsoft SCOM and use of all the functionality it provides.

Application Software

Before you install OpsCx for Microsoft SCOM, the following software applications must be installed and configured:

Application	Supported Versions
Microsoft System Center Operations Manager	2016, 2012 R2, 2012 SP1, 2012, 2007 R2.
Operations Manager i	10.01 or higher
Operations Connector	10.01 or higher Operations Connector must be configured as a connected server in Operations Manager i and properly integrated into Operations Manager i. Service provider recommends that Microsoft System Center Operations Manager and Operations Connector are installed on different host systems. To use the Ops Connector for SCOM 3.02 High Availability feature, you must install 10.11 or later. Make sure to apply hotfix QCCR1A187851. If you are using an Operations Connector version earlier than 10.00, upgrade it first. For instructions, see the BSM Connector Installation and Upgrade section.

Application

Supported Versions

Microsoft System Center Operations Manager

2016, 2012 R2, 2012 SP1, 2012, 2007 R2.

Operations Manager i

10.01 or higher

Operations Connector

10.01 or higher

Operations Connector must be configured as a connected server in Operations Manager i and properly integrated into Operations Manager i. Service provider recommends that Microsoft System Center Operations Manager and Operations Connector are installed on different host systems.

To use the Ops Connector for SCOM 3.02 High Availability feature, you must install 10.11 or later. Make sure to apply hotfix QCCR1A187851.

If you are using an Operations Connector version earlier than 10.00, upgrade it first. For instructions, see the BSM Connector Installation and Upgrade section.

For installation and configuration information, see the corresponding documentation.

Additionally, the following auxiliary software must be installed on the Operations Connector host:

Auxiliary Software	Required Version, Notes
Microsoft System Center Operations Manager SDK The SDK is bundled with the base product and is covered by the Microsoft System Center Operations Manager license.	Depending on your Microsoft System Center Operations Manager version; a subset of the SDK assembly files is required.
Microsoft .NET Framework	4 or later; full installation of the Windows Server feature. You can download the extended version of Microsoft .NET Framework 4 from the web site http://www.microsoft.com/en-us/download/details.aspx?id=17718. For installation instructions, see the Microsoft Windows Server documentation.

Auxiliary Software

Required Version, Notes

Microsoft System Center Operations Manager SDK

The SDK is bundled with the base product and is covered by the Microsoft System Center Operations Manager license.

Depending on your Microsoft System Center Operations Manager version; a subset of the SDK assembly files is required.

Microsoft .NET Framework

4 or later; full installation of the Windows Server feature.

You can download the extended version of Microsoft .NET Framework 4 from the web site http://www.microsoft.com/en-us/download/details.aspx?id=17718. For installation instructions, see the Microsoft Windows Server documentation.

For visual representation of metrics in OMi by using the bundled performance dashboard, the following OMi management packs must be installed:

The management packs are shipped with OMi.

Management Pack	Required Version
OMi Management Pack for Infrastructure	1.10 or later
OMi Management Pack for Microsoft Active Directory	1.00 or later
OMi Management Pack for Microsoft SQL Server	1.00 or later

Network Load Balancing for Microsoft SCOM

If you deploy multiple servers in a distributed Microsoft SCOM 2012 or later installation, Microsoft recommends to configure Network Load Balancing (NLB). NLB is a Windows Server feature that enables high availability for the Operations Manager Data Access service in your Microsoft SCOM environment. It achieves this by automatically redirecting clients to another management server if the connection to the Operations Manager Data Access service fails. For more information about NLB, see the Microsoft web site http://msdn.microsoft.com/en-us/library/bb742455.aspx. For instructions on how to install and configure NLB, see the Microsoft web site http://technet.microsoft.com/en-us/library/hh316108.aspx.

TCP/IP Ports

The following table lists the ports that OpsCx for Microsoft SCOM uses by default. In your Operations Connector environment, these ports may not be used by other software applications.

Port Number	Port Description
30005¹	Default port of Operations Connector policies of the REST Web Service Listener type Used for dispatching Microsoft SCOM events and metrics to the respective Operations Connector policies.
30030 or higher²	Default Microsoft SCOM event backward synchronization port Used for synchronizing the resolution state of events in the Microsoft SCOM instance with the state in Operations Manager i.

Port Number

Port Description

30005¹

Default port of Operations Connector policies of the REST Web Service Listener type

Used for dispatching Microsoft SCOM events and metrics to the respective Operations Connector policies.

30030 or higher²

Default Microsoft SCOM event backward synchronization port

Used for synchronizing the resolution state of events in the Microsoft SCOM instance with the state in Operations Manager i.

¹If you cannot ensure the default port is free, you can still change the port number while configuring OpsCx for Microsoft SCOM. Keep in mind that changing the port number includes mandatory actions also in Operations Connector.

²For the second and each additional integrated Microsoft SCOM instance, OpsCx for Microsoft SCOM uses an increased default port number. If the target port is occupied, the port number is further increased until a free port is found.

If Microsoft SCOM and Operations Connector communicate through a firewall, make sure the firewall rules allow connections through the listed ports.

Other Prerequisites and Requirements

The following is a list of additional prerequisites and the requirements you must consider before installing the product:

The Operations Connector and Microsoft SCOM host systems must be members of the same domain.
Previous versions of OpsCx for Microsoft SCOM may not be installed on the Operations Connector host.
To be able to configure and administer OpsCx for Microsoft SCOM, familiarize yourself with Operations Connector and its web interface. For example, you can learn how to import, activate, and reconfigure policies. For information on these and other relevant topics, see the Operations Connector User section.

Send Help Center feedback