Configure the Microsoft System Center Operations Manager (SCOM) connector instance to receive alerts and Operational Intelligence raw data from the SCOM server.

1. On the SCOM server, download the following files to a local computer.

   Version	SCOM path and library names
   SCOM 2012R2 or SCOM 2012	%ProgramFiles%\Microsoft System Center 2012 R2 or 2012\Operations Manager\Server\SDK Binaries Microsoft.EnterpriseManagement.Core.dll Microsoft.EnterpriseManagement.OperationsManager.dll Microsoft.EnterpriseManagement.Runtime.dll
   SCOM 2007	%ProgramFiles%\System Center Operations Manager 2007\SDK Binaries Microsoft.EnterpriseManagement.OperationsManager.Common.dll Microsoft.EnterpriseManagement.OperationsManager.dll Note: Do not append 2007 to the Microsoft.EnterpriseManagement.OperationsManager.Common.dll file.
   SCOM 2016	%ProgramFiles%\Microsoft System Center 2016\Operations Manager\Server\SDK Binaries Microsoft.EnterpriseManagement.Core.dll Microsoft.EnterpriseManagement.OperationsManager.dll Microsoft.EnterpriseManagement.Runtime.dll Note: The MID Server must be installed with .NET 4.6 or higher.
   SCOM 2019	%ProgramFiles%\Microsoft System Center 2019\Operations Manager\Server\SDK Binaries Microsoft.EnterpriseManagement.Core.dll Microsoft.EnterpriseManagement.OperationsManager.dll Microsoft.EnterpriseManagement.Runtime.dll Note: The MID Server must be installed with .NET 4.6 or higher.

   Note: A connection cannot be made to SCOM 2012 and SCOM 2007 from the same MID Server. To work with both SCOM 2012 and SCOM 2007 in your instance, do the following before uploading files to your instance:

   1. Append .2012 to the end of the Microsoft.EnterpriseManagement.OperationsManager.dll file found in the 2012 path.
   2. Append .2007 to the end of the Microsoft.EnterpriseManagement.OperationsManager.dll file found in the 2007 path.

   Using these modified filenames enables the relevant MID Server to load the applicable dll when both SCOM versions are deployed. Do not append 2007 to the Microsoft.EnterpriseManagement.OperationsManager.Common.dll file (for SCOM 2007).

   At any given time, you can define connectors of either SCOM 2007, SCOM 2012/2016, or SCOM2019. Since SCOM 2012 and SCOM 2016 use the same library files, they are able to work at the same time. Each SCOM connector can use the database of another connector, for metric support.

2. Navigate to MID Server > JAR Files.
3. Click New and add a separate record for the SCOM version for each of the DLL files that you downloaded from the SCOM server.
   1. In the Name field, specify the SCOM version and an identifier to make the name unique, for example 2012 1. If you are using SCOM 2016, specify 2012 as the version.
   2. Click the paper clip icon in the form header and then attach one of the appropriate DLL files that you downloaded.
   3. Click Submit.
4. Repeat step 3, creating a separate record for each of the remaining DLL files. Ensure that you have a unique identifier after the SCOM version for each file that you attach, for example 2012 2.
5. Navigate to Event Management > Integrations > Connector Instances.
6. Click New and create a connector instance with the following details:

   Field	Value
   Name	Unique name for the SCOM connector instance.
   Description	Description for the use of the SCOM event collection instance.
   Active	Select this option only after running a successful test.
   Connector definition	The vendor and protocol used to gather events from the external event source. Select the SCOM connector definition.
   Host IP	Specify the SCOM IP address.
   Credential	Select Windows credentials. Note: When configuring Windows credentials, ensure that the MID Servers you specify match the MID Servers specified in the MID Servers for Connectors section on the Connector Instance form.
   Event collection last run time	The last event collection run time value updates automatically.
   Last event collection status	The last event collection run time status updates automatically.
   Event collection schedule (seconds)	The frequency in seconds that the system checks for new events from SCOM Operations.
   Bi-directional	Select to invoke the bi-directional option. This option enables the bi-directional exchange of values to-and-from the external event source. There is default implementation for SCOM. The Last bi-directional status option displays only when this option is selected.
   Last bi-directional status	The value of this field populates automatically.
   Last error message	The last error message field is automatically updated. This message is the last error message received by the connector. If the test connector fails, an error message is displayed in this field.
   Metrics collection	Select to enable the collection of Operational Intelligence.
   Metrics collection last run time	The last run time of the metrics collection scheduled job. This option displays only when the Metrics collection option is selected.
   Last metrics collection status	Status of the Operational Intelligence collection activity. The value of this field populates automatically. This option displays only when the Metrics collection option is selected.
   Metrics collection schedule (seconds)	The time, in seconds, to repeat the Operational Intelligence collection scheduled job. This option displays only when the Metrics collection option is selected.
   Metrics database host	The IP address or the host name of the metrics database host. This option displays only when the Metrics collection option is selected.
   Connect using a named instance	When selected, the connection is made using the specified named instance. Otherwise, the connection is made using the specified port. This option displays only when the Metrics collection option is selected.
   Metrics database port	The port used by the metrics database. The connection is made using JDBC. Default port number 1,433. This option displays only when the Metrics collection option is selected. However, if Connect using a named instance is selected, this option no longer displays.
   Metrics database named instance	The metrics database instance name. This option displays only when the Metrics collection option is selected.
   Database login with Windows authentication	Perform database login with the credentials of the logged-on user defined on the MID Server service. This option displays only when the Metrics collection option is selected.
   Metrics database credential	Credentials for the metric database. Use JDBC credentials for the local database user. This option displays only when the Metrics collection option is selected. However, if Database login with Windows authentication is selected, this option no longer displays.
   MID Servers (MID Server for Connectors section)	Optional. Specify one or more MID Servers that are up and valid. If the first is down, the next MID Server is used; if that MID Server is not available, the next is selected, and so on. MID Servers sort according to the order that their details were entered into the MID Server for Connectors section. The port requirement from the MID Server to the SCOM server is 5724 to be fixed. If the specified MID Server is in a cluster, it may not be selected and another available MID Server is selected in its place. Ensure that the specified MID Servers match the MID Servers specified on the Windows Credentials page, as the connector uses Windows credentials to access MID Servers. If no MID Server is specified, an available MID Server that has a matching IP range is used.

7. Right-click the form header and select Save.
   The connector instance values are added to the form and the parameters that are relevant to the connector appear.
8. In the Connector Instance Values section, you can edit the values of the mandatory SCOM parameters.
   1. login_with_windows_authentication Default value: false.
      Set to true to enable SCOM event collection and the bi-directional exchange of event values to work with Windows authentication.

      When invoking this value, ensure that you do the following on the MID Server:

      1. Navigate to the list of local services, right-click the MID Server service, and select Properties.
      2. In the Log On tab, ensure that This account is selected with the details of the user in the Windows domain with read access to the SCOM database.
   2. metric_chunk_size Default value 50000.
   3. scom_date_format Default format M/d/yyyy/ h:mm:ss a
      If you receive an event whose date is in a different format, modify this value to match the format of the incoming event. If you do not, the event does not process correctly.

      For example, if an event arrives on June 27, 2019 at 11:25 AM with a listed date of 2019/06/27/ 11:25:00 a, modify the scom_date_format value to yyyy/M/d/ h:mm:ss a to match the format of the received event.

      In scom_date_format, a represents AM, and p represents PM.

   4. scom_initial_sync_in_days Default value 7.
   5. scom_version It is mandatory to specify the SCOM version, select from 2016, 2012, or 2007.
9. Right-click the form header and select Save.
10. Restart the MID Server service to copy the files.
11. Click Test connector to verify the connection between the MID Server and the connector.
12. If the test fails, correct the problem by following the instructions issued by the error and then run another test.
    Note: Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to SCOM.
13. After a successful test, select the Active check box and then click Update.
    Note:

    The default binding rules that contain SCOM as the external source, that applies to IT alerts and Operational Intelligence raw data, are the following SCOM Management Packs:

    • All OS Management Packs
    • MS SQL Server
    • IIS