Endpoint Protection

I am migrating from the SAV10 for SEP 11.00, my network has 450 computers, I am configuring an internal live update. My question is: I use the pull mode for how many minutes?

By default the heart beat interval is set to 5 mins.
The choice of the time interval depends upon the bandwidth in your network.
If we are refrerring to a normal envirionmnet i with not more over head on the network  i  will continue with the default .

Symantec Endpoint Protection Client configuration changes for performance optimization

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007102311173048

Hi Andre,
>>Ultimately, any communication is initialized by the Client!<<
Changing the Heartbeat Interval will increase or decrease your chances of reaching the client with a new Command or changed policy in a longer or shorter Time-Period.
To reach the client fast can be important in a situation of a Virus Outbreak, to move the clients into a Group with Higher Security Settings.
To have the Interval higher can have a pocitive affect on your Network Bandwidth.
Keep this in mind when changing the Heartbeat.

This KB may help you:
Title: 'Top 10 Symantec Best Practices - Deploying Symantec Endpoint Protection Architecture'
Document ID: 2009012721190648
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009012721190648?Open&seg=ent

You may set the value depending on your network

In my personal opinion its necessary for a client to keep talking to the manager all the time and increase the network traffic

client talk to manager for 2 things, 1 ) virus updates 2 ) policy , sends log whenever they talk
If your manager is configured to get liveupdate once in a day then clients need to talk just once for LU
How often do u change your policies
in my case its very rare that you change policy.
servers groups will remain with same policy, say DC.
 MOre the time set , less the traffice in network

Hope this helps to decide ;) 

Basically, you can use following formula to calculate the lowest heartbeat interval recommended (depending on SEPM hardware specs of course):

#CLIENTS / 1000 = X minutes
where the result is the heartbeat (e.g. 1000 clients => 1 minute)

But I set it at least on 2 minutes in small environments up to 15 - 20 minutes in the larger ones, not that the amount of data sent by a SEP client is no more than a few KB when it connects that often. Also, make sure that SEPM stores enough content updates to minimize the size of the update (it guarantees SEPM can create a delta suitable for the client).

Hi
decide what ever you want on your interval heartbeat it depend on the to communicate the client into SEPM server, to share you my experienced, I have a remote site with 250 clients before all of that clients are aquiring an update simultaneously from the management server with the 5 mins interval but suddenly I notice that my network utilizing high network bandwidth so I decide to increase my heartbeat to 8 hours and dedicate a Group update provided to save my network bandwidth, Believe me it works.