Configure the SCOM connector instance The SCOM connector instance requires configuration prior to receiving alerts from the Microsoft System Center Operations Manager (SCOM). Before you beginBefore starting this procedure, verify: The MID Server resides in the same domain as the SCOM server. The MID Server uses the same time zone as the SCOM server. The MID Server is running on Windows. The MID Server has .NET framework version 3.5. If Bi-directional is selected, ensure that: PowerShell version 3.0 is installed on Windows. As Windows authentication is used by the connector to access the SCOM API, the MID Server service should be running with a user having read-and-write access to the SCOM API. Do this by ensuring that the correct credentials are used: In the local services, right-click the MID Server service and select Properties. In the Log On tab, ensure that This account is selected with the details of the user in the Windows domain having access to the SCOM API. Role required: evt_mgmt_admin About this taskIf you want to receive SCOM alerts, you can obtain the redistributable SCOM files from your SCOM application, add them to the MID Server, and then configure a SCOM connector instance. Procedure On the SCOM server, download the following files to a local computer. Version and locationSCOM path and library names SCOM 2012R2 or SCOM 2012 or SCOM 2016 %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. Note: To work with both SCOM 2012 and SCOM 2007 in your instance, before uploading the following files to your instance, append .2012 to the end of the filename Microsoft.EnterpriseManagement.OperationsManager.dll that is found in the 2012 path and append .2007 to the end of the filename Microsoft.EnterpriseManagement.OperationsManager.dll that is found in the 2007 path. This enables the 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). Navigate to MID Server > JAR Files. Click New and add a separate record for the SCOM version for each of the DLL files that you downloaded from the SCOM server. 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 2007, specify 2007 as the version. For SCOM 2012, specify 2012 as the version. Click the paper clip icon in the form header and then attach one of the appropriate DLL files that you downloaded. Click Submit. Repeat step 3, creating a separate record for each of the remaining DLL files, ensuring that you have a unique identifier after the SCOM version for each file that you attach, for example 2012 2. Navigate to Event Management > Connectors > Connector Instances. Click New and create a connector instance with the following details: Field Value Name Specify a unique name for the SCOM connector instance. Mandatory. Host IP Specify the SCOM IP address. Mandatory. Credential In the Credentials form, click New and create the required credentials. Save the credentials using a unique and recognizable name, for example, SCOMOPS. Mandatory. Schedule (seconds) The frequency in seconds that the system checks for new events from SCOM Operations. Description Type a description for the use of the SCOM event collection instance. Connector definition The vendor and protocol used to gather events from the external event source. Select the SCOM connector definition. Mandatory. Last error message The last error message is automatically updated. Active Select this option only after running a successful test. Last run time The last run time value is automatically updated. Last run status The last run time status is automatically updated. 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. The Last bi-directional status option displays only when this option is selected.Note: This feature is not supported on a MID Server that is installed in a directory that has a space in its path. Last bi-directional status The value of this field is automatically populated. The status values are: None - A valid connection has not yet been established. Success - A successful connection was established. Error - A connection was established. However the external event source was not updated. Last error message Last error message received by the connector. If the test connector fails, an error message is displayed in this field. MID Servers (MID Server for Connectors section) Specify the MID Server that must run the SCOM connector instance. If not specified, an available MID Server that has a matching IP range is used. Right-click the form header and select Save. Use network tools such as Ping to verify that the SCOM server is running and the IP address matches the value in the Host IP field. Right-click the form header and select Save. In the Connector Instance Values section, specify other optional SCOM values. metric_chunk_size Default value 5000. scom_date_format Default format M/d/yyyy/ h:mm:ss a scom_initial_sync_in_days Default value 7 scom_version It is mandatory to specify the SCOM version, either 2007 or 2012. Note: If you are working with SCOM 2016, specify 2012 for the scom_version parameter. Right-click the form header and select Save. Click Test connector to verify the connection between the MID Server and the connector. If the test fails, follow the instructions on the page to correct the problem and then run another test. Tip: Use a network tool, such as ping, to verify that the SCOM server is running and the IP address matches the value in the Host IP field. After a successful test, select the Active check box and then click Update. ExampleIf bi-directional is configured, the bi-directional exchange of values to-and-from the external event source is enabled. These scenarios describe the out of the box bi-directional functionality for SCOM connectors: When an alert is resolved in SCOM, it is auto-closed in ServiceNow. However, it is updated irrespective of the bi-directional feature because during each collection cycle, all alert changes are updated. When an alert is manually closed in ServiceNow, it is auto-closed in SCOM. If the alert state is changed to Reopen, SCOM is also updated. When an incident is created and associated to an alert in ServiceNow, SCOM receives the incident number as a ticket ID. However, the state of the incident is not available on SCOM. Therefore when the incident is resolved in ServiceNow, SCOM is not updated as the incident number remains the same. When the alert is associated with a new incident, the new incident number is updated in SCOM.