Video Screencast Help

How to push policies

Created: 04 Aug 2010 • Updated: 04 Aug 2010 | 3 comments


I have a problem with my Symantec Endpoint Manager 11.05, I created a new policy and my server takes a lot of time to push the policy to all the clients .
I'm new with Symantec Manager so please be nice with me :) .
Is there any button to select a client/group to receive quicker this policy.


Discussion Filed Under:

Comments 3 CommentsJump to latest comment

mclemson's picture

Wrong forum -- this is for a ticketing software.

But I'll help you out anyway.  If you right-click on the SEP system tray icon, there is an Update Policy button which will force the policy to update.  If your server is taking a long time to push the policy to clients, check the heartbeat setting -- I think this is under General Settings or General Communication Settings.  Click Clients on the left, Policies tab on the right, and then explore the blue links in the right pane.

Policies will be updated on heartbeat, and heartbeat defaults to 5 minutes.  How long are you seeing this take?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner

Alex Budar's picture

Thanks for your answer, if  you tell me where to move my discussion i'l do that . I selected a group with only one user (my computer)  and setup the heartbeat intarval at 1 minute  and still nothing . I am running with push mode and hartbeat was default 5 minutes and I changed it to 1 minute .

mclemson's picture

You should have new policies after 1 minute -- how do you know you aren't getting the new policy?

Can the agent see the server?  You should see the yellow SEP shield in the lower, right-hand corner and a green circle (indicating it can communicate with the SEPM) on the icon.

Is the client you're troubleshooting actually in the client group whose policy you're modifying?  You'll want to confirm this as simple as it sounds.

Are you using location awareness?  If so, it's possible that the client is using a policy different than you would expect.  Check the logs on the local client to determine if it's running in a location other than you expect.

Have you checked the agent logs?  You should see a line that says  "Applied new policy with serial number.." followed by a serial number/GUID.

Check to see which policy GUID is being used on the server for the group, then check to see what policy is being used on the client.  You can also check revisions, according to this KB here (which also has instructions for locating policy GUIDs on the server and the client):

Does this help?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner