This guide provides information on the process performed when the Symantec Endpoint Protection (SEP) client checks in with the Symantec Endpoint Protection Manager (SEPM).
1. SEP client reads sylink.xml to determine first available SEPM according to priority.
2. SEP client connects to SEPM.
3. SEP client performs an HTTP GET of index.dat from the SEPM and compares it against the client copy for any deltas.
4. SEP client performs an HTTP GET request to obtain URLs to download files.
5. SEP client uploads log files to SEPM.
6. SEP client uploads LAN sensors and learned application logs to SEPM.
7. SEP client disconnects from SEPM.
When there are no new client-side logs to upload to the management server, or policy or content to download from the server, the size of the Symantec Endpoint Protection client heartbeat is between 3KB and 5KB. When all client protection technologies are enabled and the maximum level of client logging is enabled (with the exception of packet-level firewall logging, which is not recommended in production environments), the size of a typical heartbeat is between 200 KB and 300 KB.