How to force definitions update on the client side?
Updated: 21 May 2010 | 6 comments
This issue has been solved. See solution.
Some of our laptops stay offline for weeks. Usually i connect them to the network once a month to get all updates (Windows Updates, definitions). And they tend to stay not updated for a very long time, hours or so. I can select them in the Manager and issue the Update Content command, but that doesnt seem to improve updating speed. Connection is the Pull mode with 1 hour heartbeat. I'm looking for an option to force an update, maybe client-side, so i won't need to keep tem on my desk until they finally manage to update.
discussion Filed Under:
Comments
Did you hide the client Icon in the bottom right of the taskbar from the clients?
If you didn't, and you set the permissions in the SEPM to allow them to download the definnitions, need to check exactly where that is, they should be able to Right-Click and "update policy".
No intervention required by you... As long as they are aware and responsible enough to do so.
I use location awareness for remote laptops that are disconnected for long periods of time.
The exact settings really depend on your environment. If you can setup a SEPM in the DMZ it is the best solution as you still have management and reporting of the remote laptops at all times.
Office location
- Server management list that points to SEPM
- Pull mode with 4 hour checkins
- liveupdate points to default management server or GUP
Remote location with DMZ SEPM
- Server management list that points to a DMZ SEPM
- liveupdate points to symantec update servers or (dmz liveupdate server)
- Sometimes use continuous updates
Remote location
- Communication disabled to SEPM (no Server management list)
- liveupdate points to symantec update servers
- Sometimes also have liveupdate scheduled silently via a scheduled task
The problem seems to be with only one old Toshiba Tecra M2 laptop we have. Others will eventually update after some time. This one wasnt updating. I have tried updating the policy on the client side and also issuing "Update Content" commands via SEPM. That didnt do the trick. But when i tried to issue "Update Content and Scan" command suddenly it started to update. Strange, but this will do as a workaround for now. This laptop (or maybe its drivers/software) was causing problems with older Symantec Corporate Editions too.
you can also use the command "smc -updateconfig" in a script to force the client to heartbeat.
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
>you can also use the command
>you can also use the command "smc -updateconfig" in a script to force the client to heartbeat.
What do you mean by script? If i try to type this command in command prompt on a client, it doesnt recognize it.
>you can also use the command
>you can also use the command "smc -updateconfig" in a script to force the client to heartbeat.
What do you mean by script? If i try to type this command in command prompt on a client, it doesnt recognize it.
Hi,
You have to run it from SEP installation folder. Other option is to add that folder to PATH= so it will work from anywhere.
- Jukka
Would you like to reply?
Login or Register to post your comment.