This socket exception is usually caused by a certificate mismatch, as if the rogue sensor depending from ePO server A was trying to report to ePO server B:
The problem was related to:
In Rogue System Detection 4.5.0:Policy > General > My Default ---> the server name was set to the other ePO server (main).
That was the cause of the certificate mismatch.
But now how should I proceed.
Is it possible to have one ePO server to manage all the sensors.
Or should each ePO server manage their sensor. ---> How can they see if the rogue detected workstation resides in the other ePO server?
Hi mathr601 just deploy sensors as you need for each ePO server and then go to Menu->Configuration->Server Settings->Detected System Compliance->Edit and add any other ePO server names you are using under "Other ePO Servers" at the bottom of the page.
Repeat this in any other ePO server and so any computer managed by any of these servers won't be detected as a rogue system
Thanks for the fast answers.
I will test it thoroughly.
Do I have to register the servers in a crisscross pattern?
Or I just need to go in the "Registered Servers" of the main ePO server and register the secondary(ies) servers?
As far as I know you don't need to register other ePO servers when using RSD but only specify their names at "Other ePO Servers"