SCOM Connector and 2019 Compatibility

SJMarty
Kilo Explorer

‎04-08-2020 05:45 AM

Hello,

I found this article stating how to configure the SCOM Connector for the New York release of ServiceNow and it does not list SCOM 2019 as supported.

This article lists SCOM 2019 as supported but is for the Orlando release of ServiceNow.

I have two questions...

  1. Is the SCOM Connector fully compatible with the New York release of ServiceNow?
  2. I've been advised that bi-directional support does not work with SCOM 2019 and the Orlando release of ServiceNow due to API changes in SCOM 2019.  Is this accurate?

Thank you!

0 Helpfuls
  • 1,283 Views
12 REPLIES 12

Ryan Zulli
ServiceNow Employee
ServiceNow Employee
In response to Derek28

‎02-03-2021 07:48 AM

yes - and in Quebec its now OOB (meaning the SCOM javascript is properly updated)

 

mahesh_80
Tera Contributor

‎02-22-2021 08:12 PM

Hello Ryan

You mentioned "backporting the connector from Orlando to NY should work", can you please tell me what is required to do it?

 

0 Helpfuls

Ryan Zulli
ServiceNow Employee
ServiceNow Employee
In response to mahesh_80

‎02-23-2021 06:46 AM

Hi - Are you looking specifically for bi-directional functionality? If so, make that one slight adjust in the post above and that'll fix the issue.  If you do not need bi-directional functionality, then the connector works as is.

Thanks!

 
0 Helpfuls

mahesh_80
Tera Contributor

‎02-23-2021 07:06 PM

Hi Ryan

I am not looking for bi-directional.

We just import into servicenow. When trying to establish the connectioni am getting an error "Connection test failed: Credentials not found, id: 949a5e4035f90200939cbc2cec39476e"

I have created a windows credential and the service account has admin right for SCOM.

We are on NewYork and trying to connect to SCOM 2019.

Thank you.

0 Helpfuls

Rahul Priyadars
Giga Sage
Giga Sage
In response to mahesh_80

‎02-23-2021 07:19 PM

  1. Click Test connector to verify the connection between the MID Server and the connector.
  2. If the test fails, correct the problem by following the instructions issued by the error and then run another test.
     Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to SCOM.

I hope these pre-requisites are fulfilled.

  • The MID Server is running with a user that has local admin permissions to enable the MID Server to run PowerShell.
  • The MID Server user has read access to the SCOM API.
  • 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.
  • 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.

 

Regards

RP

 

0 Helpfuls