SEPM Servers Hearbeat...

[Migration User]

What is the actual meant of Heartbeat. Also what we can do after we know it.

[Migration User]

The SEP client heartbeat interval is normally controlled by communications policies set at the Symantec Endpoint Protection Manager (SEPM). In certain situations, the SEP client will decrease its heartbeat interval to a value between 0 and 60 seconds. The purpose of this accelerated heartbeat is to ensure that critical updates and content are delivered to clients in as timely a manner as possible. Once the client is able to download the content update or package requested, the client will then re-apply the heartbeat interval configured at the SEPM level. It is not possible to configure clients' Accelerated Heartbeat intervals Check the pk comment https://www-secure.symantec.com/connect/forums/heart-beat-1 Answer of both queries

[Migration User]

See below articles

Symantec Endpoint Protection: The Heartbeat Process

http://www.symantec.com/docs/TECH191617

see mithun articles

Symantec Endpoint Protection : The Heartbeat Process

https://www-secure.symantec.com/connect/articles/symantec-endpoint-protection-heartbeat-process

[ℬrίαη]

Simply put, the heartbeat setting determines how often the client checks in to the SEPM to grab content updates, update policy, upload logs, etc. It's simply a check in setting.

[Migration User]

So thats mean that we can check SEP Heartbeat and SEPM Servers Heartbeat. Then where is located the Heartbeat interval logs.

[Migration User]

You need to enable sylink debugging logs

Enable sylink debugging for Endpoint Protection clients

http://www.symantec.com/business/support/index?page=content&id=TECH104758

[ℬrίαη]

Unless you enable sylink debugging there is no log generated.

[Migration User]

Hi James ,

Chekc the attachment same is attached. Request to please provide the details about the Heartbeat.

Attachment(s)

Sylilnk.7z   9 KB 1 version

[Migration User]

<IndexHeartbeatProc>Set Heartbeat Result= 2
04/06 10:16:58 [3636] <IndexHeartbeatProc>Sylink Comm.Flags: 'Connection Failed' = 0, 'Using Backup Sylink' = 0, 'Using Location Config' = 0
04/06 10:16:58 [3636] Use new configuration
04/06 10:16:58 [3636] HEARTBEAT: Check Point Complete
04/06 10:16:58 [3636] <IndexHeartbeatProc>Done, Heartbeat=7200seconds
04/06 10:16:58 [3636] </CSyLink::IndexHeartbeatProc()>

[Migration User]

It Means in every 7200 Seconds client is taking update content or policy update from SEPM.

So what exact miliseconds is okay for communicaiton to the clients.

In that means every system's having there own HeartbeatProc....

[Migration User]

You can check your heartbeat setting.

Open the SEPM console.

Click "Clients".

Select "Policies" tab

Click "Communication settings from Settings".

Check Heartbeat Interval.

[ℬrίαη]

Heartbeat is two hours.

All clients will check in to the SEPM every two hours to check for updates, any policy changes, upload logs, etc.