Endpoint Protection client connects to the wrong manager
Last Updated July 07, 2015
The Symantec Endpoint Protection client appears to connect to the wrong Symantec Endpoint Protection Manager (SEPM) server. The Sylink.xml file in the client folder shows one SEPM address, but the client tries to connect to a different SEPM.
It is possible in the SEPM console to configure different communication settings and Manager lists for each location. To find the setting in the console:
In the Clients section, click the Policies tab for the correct group.
Expand the "Location-specific Settings" and click the >> arrow to the right of "Communication Settings".
In the menu, the option is called "Use Group Communication Settings".
When the client is in a location with specific communication settings, it ignores the sylink.xml file and the Policy Manager List configured for the group. These settings are saved into the general policies file (serdef.dat) on the client instead of inside the main sylink.xml file (which normally indicates where the client should connect to).
Imported Document ID: TECH173364
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe