Product Limitations

This section describes known limitations in OpsCx for Microsoft SCOM 3.02 (Operations Connector for Microsoft SCOM).

General Limitations

• Operations Connector requirement for support of Microsoft SCOM in IPv6 environment:

  Operations Connector for Microsoft SCOM supports remote Microsoft SCOM instances running in a pure IPv6 environment. Certain parts of the Operations Connector, however, do not support IPv6. Because Operations Connector for Microsoft SCOM must be installed on the same host as Operations Connector, this means that the Operations Connector host must be configured in a dual IP stack (IPv4 and IPv6) environment to support such Microsoft SCOM setup.

• Multiple instances of Operations Connector for Microsoft SCOM cannot be configured as product connectors in the same Microsoft System Center Operations Manager (Microsoft SCOM) instance:

  Operations Connector for Microsoft SCOM is a subscription-based product connector. A subscription filter defines which events (alerts) the connector collects. When an alert is generated, it is compared against all active connector subscriptions, but only the first matching subscribed connector receives the alert. To ensure that Operations Connector for Microsoft SCOM receive alerts, do not configure other product connectors in parallel with it. Operations Connector for Microsoft SCOM is by default configured to collect all alerts from Microsoft SCOM.

• Subscription changes may not take effect immediately:

  In a distributed environment, after changing a subscription in a Microsoft SCOM instance, the change may not take effect immediately on all Microsoft SCOM hosts. To verify that the change is complete, check the operating system Event Viewer tool for a corresponding notification event: in the Event Viewer GUI, navigate to Event Viewer (local) > Applications and Services Logs > Operations Manager. If such event is logged, it indicates that the change is complete and Operations Connector for Microsoft SCOM is already receiving alerts according to the changed subscription.

• Operations Connector for Microsoft SCOM requires Microsoft SCOM administrative privileges to access data in a Microsoft SCOM instance:

  Microsoft SCOM requires administrative privileges for all product connectors that communicate with it. The user account that Operations Connector for Microsoft SCOM uses to connect to a Microsoft SCOM instance must be a member of an Active Directory group that has the Operations Manager Administrators user role assigned.

  If you add the connection user account to a less privileged user role in Microsoft SCOM, Operations Connector for Microsoft SCOM will not be authorized to collect data.

Event Integration Limitations

• Microsoft SCOM may not forward all alerts to Operations Connector for Microsoft SCOM:

  If the value of the Microsoft SCOM setting TierTimeDifferenceThreshold is set too low, not all alerts might be forwarded to Operations Connector for Microsoft SCOM. The value of this setting defines the delay (in seconds) between alert retrievals from the database. The minimum value for the setting is 1.

  Additionally, alerts with a repeat count of more than 10,000 are sometimes not dispatched from Microsoft SCOM.

• When alerts get closed in Microsoft SCOM backward synchronization is also triggered:

  Operations Manager i invokes backward synchronization of the alert resolution state to the Microsoft SCOM instance (through Ops Connector for Microsoft SCOM) regardless of where the alert gets closed. Such synchronization is unnecessary when you close the alert in Microsoft SCOM.

Metric Integration Limitations

• Collected metrics are limited by the supported Microsoft SCOM management packs

  Operations Connector for Microsoft SCOM can forward only metrics that are related to the objects defined in the topology synchronization package for the supported Microsoft SCOM management packs. Other metrics might not be visible in Operations Manager i, but are still added to the database of Operations Agent.