Video Screencast Help

Purpose of Run Command - Update Content on Clients

Created: 13 Jun 2013 | 7 comments

What is the purpose of having the ability to right-click on a client and run the "Update Content" command.  If the clients are set to automatically update their content, then what would manually running this do anything differently?

Operating Systems:

Comments 7 CommentsJump to latest comment

Rafeeq's picture

Yes

this is running it remote from the console only

client will communicate with sepm using heartbeats

its called pull mode or push mode ( push mode wil have constant connection )

if your clients are in pull mode say after an interval of 8 hours

but you want to immediately push out a policy or definition. you will use this command so that you dont have to wait.

Brɨan's picture

Using this command forces a LiveUpdate session. The client will update from a Symantec LU server.

The client initiates communication to the SEPM based on the heartbeat so when the client checks in, it will receive the update content command and begin a LiveUpdate session.

See this thread and specifically the post by sandra.g, which explains it:

https://www-secure.symantec.com/connect/forums/upd...

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Mithun Sanghavi's picture

Hello,

On managed clients, the commands that you run override the commands that the user runs. The order in which commands and actions are processed on the client computer differs from command to command. Regardless of where the command is initiated, commands and actions are processed in the same way.

When running a "Update Content" command from SEPM, it initiates a forceful command to the client via heartbeat and stating a Liveupdate session.

Updates content- 

Updates content on clients by initiating a LiveUpdate session on the client computers. The clients receive the latest content from Symantec LiveUpdate.

See Configuring the LiveUpdate download schedule for Symantec Endpoint Protection Manager.

Check these Articles:

About commands that you can run on client computers

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

Symantec Endpoint Protection: The Heartbeat Process

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

Running commands on the client computer from the console

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

Hope that helps!!

Mithun Sanghavi
Associate Security Architect

MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

technical_specialist's picture

If the clients are set to automatically update their content, then what would manually running this do anything differently?

Purpose of Run Command is that you need initiate the Update on Immediate Base. Automatically Update their content is base on Heart Beat interval Time Schedule.

When you have make any of the modification in Policy and you applied on client on urgent on that time Run - Update Content will more helpful.

ed16's picture

Correct me if I'm wrong, but when executing the Update command, the clients don't receive the update immmediately.  They receive it on the next heartbeat, which is when they would have automatically received it anyway.

It sounds like the only difference is getting the client to go to the Internet to Symantec to get the definitions, as opposed to internally receiving them via our SEPM.  Are there cases where the clients fail to successfully download the definitions from the SEPM, but then are able to successfully apply them directly from Symantec?  What would be the difference?  A corrupted definiton should be a corruption definition.  Why would changing the source of your definitions fix that?

Brɨan's picture

On heartbeat in, they would receive the command and would execute it shortly after.

There could be multiple reasons. If you enable sylink logging and review the log file, it will give you more info as to what could be wrong. The Liveupdate.log file will also show the potential source of the problem.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Rafeeq's picture

the updated cmd will initiate the liveupate session on the client and it will go to internet for update not from SEPM.

Heartbeat will get the updates from SEPM.