IBM integrations

Known issues

At the time of release, several known issues were reported that you should be aware of when running the probe.

This section covers the following known issues:

The probe cannot be run as a Windows service
The probe cannot be run as a Windows service. As an alternative, you can use a Netcool/OMNIbus process agent (PA) to manage the probe. Process agents can be run as Windows services.
Tally mismatch for repeat alerts
The ObjectServer uses the Tally field to keep track of the number of times that an alert occurs. This enables it to deduplicate repeated alerts in the Netcool/OMNIbus active event list but still track the number of times a particular alert has occurred.
Connector name subscriptions
With the Probe for Microsoft SCOM 2007 and Probe for Microsoft SCOM 2007 R2 it was possible to create multiple connectors with duplicate settings. This is not possible with the Probe for Microsoft SCOM 2016.
Known issues with automatic event acknowledgement
There are a number of issues which can occur when configuring automatic event acknowledgement. To resolve some of the more common issues, use the below information.
AntiXssLibrary error
When an alert is triggered in Microsoft SCOM 2016 by shutting down a monitored windows service the probe will receive the following error:
East Asian locale settings
A defect in Microsoft .NET Framework 3.5 causes problems with event processing when the probe is using East Asian character encoding and the volume of event data reaches 2GB.
Summary field gets truncated
Summary field values that exceed 255 characters are truncated.
Upgrading from the SCOM 2007 R2 probe to the SCOM 2016 probe
CommandPort: returns 'unknown command' to operations received from telnet if a backspace was issued with the command
The probe will return unknown command to all operations issued using telnet if there is a backspace issued in the command.

Parent topic: Microsoft System Center Operations Manager 2016