Video Screencast Help

Agents not updating

Created: 10 Jun 2014 | 6 comments

I have two sites in Thailand that are not installing agents as scheduled.  The details of the task are  Status: "Task Never Started" Next Run: "Not Scheduled".  I have checked to be sure the agents have a repeating schedule.  I turned the policy off and back on to no avail.  I checked the client logs and a repeated entry of "Failed to convert next run time system time to variant time" seems to be a regular occurence.  The agents have downloaded OK, but are not installing.  Yeah, I can install manually, but I have far too many clients to do this on.

Does anyone have any ideas?


Operating Systems:

Comments 6 CommentsJump to latest comment

JBroniec's picture

I would recommend examining the policies targeting the agent installation.  Also, ensure that either the scheduled installation option is used or the Run Once ASAP option is used.  

Lastly, ensure there aren't multiple targeted policies driving agent installation (i.e. my Thailand laptop is a member of "New Computer Agent Deployment Policy"  and "Thailand Agent Deployment Policy".

Hope that helps. 

jms97's picture

Thanks for the advice.  We have all clients set up identically globally.  It is just about 100 Thailand computers that are experiencing the issue.  I will try the run once as well to see if that helps, however all advice I had been given was to uncheck run once because if it failed the first time, there was no option to try again.

Again, thanks!

sergei Z's picture

jms97, could you please provide the complete set of agent log files and the policy XML from any failing agent?

Policy XML is in "Client Policies" folder.


sergei zjaikin, senior principal software engineer, symantec

jms97's picture

I will look into that and get those over.  Where is the "Client Policies" folder?

jms97's picture

I just found the folder, please ignore the previous question.

JoeVan's picture

jms97, try cloning the agent update policy in question and targeting just those machines.  It probably is related to the schedule combined with the agents thinking they have already run the policy.  Cloing the policy will cause them to treat it as a new policy again.

Joe VanHollebeke
Systems Engineer