Endpoint Protection clients do not fail over or load balance to other managers
Last Updated March 19, 2019
Once a Symantec Endpoint Protection (SEP) 14.2 client successfully connects to a Symantec Endpoint Protection Manager (SEPM), it doesn't attempt to communicate with other SEPMs even if it can no longer communicate with that SEPM. This happens after updating the server certificate on a manager in the environment. This commonly happens after updating the server certificate on a SEPM.
The SEP 14.2 client uses a new communications module that doesn't contain logic to move to another manager in the event of a certificate based communications failure. Instead, the client continues to attempt to communicate with the last manager it successfully connected to.