The OpsMgr Connector has found multiple primary relationships in Active Directory for management group %1. The primary relationship to %2 has been ignored and treated as a secondary relationship; %3 is the accepted primary. To address this issue, you can add an exclusion to the Active Directory assignment rule for the incorrect primary relationship.
The OpsMgr Connector has found a duplicate record for %1 in it's configuration for management group %2. The duplicate record ...
The OpsMgr Connector has found a duplicate record for %1 in its configuration for management group %2. The duplicate record ...
The OpsMgr Connector has found both an Agent and a Server Management Group with the name '%1'. The Server Management Group ...
The OpsMgr Connector has found both an Agent and a Server Management Group with the name '%1'. The Server Management Group ...
The OpsMgr Connector has found multiple primary relationships in Active Directory for management group %1. The primary relationship ...
The OpsMgr Connector has found multiple primary relationships in Active Directory for management group %1. The primary relationship ...
The OpsMgr Connector has received a bad packet from the device at %1. The first bytes in the packet are in the binary data ...
The OpsMgr Connector has received a bad packet from the device at %1. The first bytes in the packet are in the binary data ...
The OpsMgr Connector has received an oversized package from IP %1. OpsMgr prevents large packages from being delivered to ...