Hi Jon,
Thanks for the reply. We did open the case with Support. And, here is their reply:
=========================
As per our phone conversation, the duplicated or a server has two origin is
caused by the set up in your customer environment. Here is the reason, on your
secondary hub has Origin A, therefore the robots get discovery by
discovery_agent, net_connect and interfafce_traffic would have A as their
origin. However, you also manually changed the robot controller to have origin
B, this is how you end up with duplicated or a server with 2 origin in SLM
database.
The recommendation would be that to have the probe like net_connect deployed
to the robot to monitor the robots that has same origin.
======================
I do not think that it is related to Net_connect probe. Any idea on how other customer move forward on duplicate object at NIS when they change the origin in controller probe.
Cheers,