SCOM Connector and 2019 Compatibility

[SJMarty]

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!

[mahesh_80]

Hi RP

I am getting the above error when I click on "Test Connector" 

I have verified the credential (test credential and it was "successful")

Regarding pre-requisites

• The MID Server is running with a user that has local admin permissions to enable the MID Server to run PowerShell -- Yes
• The MID Server user has read access to the SCOM API. (I am using a server that has full admin access to SCOM server, is there anything specific to be done for accessing SCOM API (one the scom side or in servicenow). I am nor sure about settings in SCOM.
• The MID Server resides in the same domain as the SCOM server -Yes
• The MID Server uses the same time zone as the SCOM server - Yes
• The MID Server is running on Windows. - yes
• The MID Server has .NET framework version 3.5 -Yes
• 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 - Yes  

Thank you

Mahesh

[Rahul Priyadars]

from Mid Server are you able to reach SCOM env?

Regards

RP

[mahesh_80]

Yes. The mid server is in the same domain as SCOM