SEP 12.1 clients not updating
Created: 13 Feb 2012 | 7 comments
Hi
I have a number of clients that are connected to a Symantec Endpoint Protection Manager that are not downloading updates from the server. The error message that I am getting is:
Downloaded new content update from the management server failed.
Remote file path: http://192.0.1.22:8014/content/{55DE35DC-862A-44c9-8A2B-3EF451665D0A}/120211002/xdelta120210002.dax
If i navigate to the link, I can download the file. Also if I perform a manual update from the internet, I am able to update the client without any problems.
This does not happen on all clients, just a few.
Also, at another site, I am having similar problems, however the difference with those machines are is that they are configured to download updates directly from the internet. These machines are configured to use a local proxy server that does not need any authentication. Again, if I do a manual update, it works ok. No entry in the logs refering to any updates attempted or failures. This does not affect all machines, just a few.
Any ideas?
Thanks,
Sam.
Discussion Filed Under:
Comments
If they are then, you may
If they are then, you may have to work on these articles below:
Symantec Endpoint Protection Manager 12.1 Communication Troubleshooting
http://www.symantec.com/docs/TECH160964
Symantec Endpoint Protection: LiveUpdate Troubleshooting Flowchart
http://www.symantec.com/docs/TECH95790
Thanks In Advance...
Ashish Sharma
If the suggestion has helped to solve your problem, please mark the post as a solution
can you pass on the sylink
can you pass on the sylink log?
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
I have attached the sylink
I have attached the sylink log files from two clients that are experiencing problems.
The file 'Client non proxy updates from server' is the client that has the error
Downloaded new content update from the management server failed.
from the client log which is
from the client log which is not updated, it is in process for downloading the ddefinition.
didn't the client update?
can you collect for longer time?
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
Hi, Can you please check
Hi,
Can you please check your proxy configuration its block any limitation
or
check your network firwall also.
New sylink file
Thanks for the help so far.
I have attached a new sylink file from the server that isn’t downloading updates from the management server.
On this particular machine, the firewall is disabled, and allowing all communication through. I have also explicitly defined in the live update policy to not go through a proxy, and connect directly to the server. I can navigate to the zip file that it is trying to download it using ie and it can download just fine. Most other clients don’t seem to have an issue in downloading the updates either.
In regards to the clients which are downloading their updates from the internet, the machine that I was collecting logs for decided to start working. I am currently collecting logs from another machine that is experiencing the same issue. This machine does not have a firewall enabled (the rules are set to allow everything), and it is configured to go through a proxy. This machine is using the same proxy as other clients which do not have issues in updating. Its dns and gateway setting are the same as other funtioning clients too.
I am currently collecing sylink logs for this machine now. Maybe by the process of observing it in action will cause it to behave differently and work.
Many Thanks,
Sam.
Having some success
I think some of my misbehaving clients are bound to the Heisenberg uncertainty principle. As soon as I start collecting logs, they start to work. However they are only the clients which download updates from the internet and not the management server. I will go though these clients one by one and get them to start logging and they should come in line.
However not eveything is so rosy. Some of my clients that are getting updates from the management server are still failing with the errors stated above. Again, most clients are working fine, just some of them fail to update.
Would you like to reply?
Login or Register to post your comment.