Symantec endpoint not updating

23 Jan

So, in order to find the broken SEP clients in my company – about 14,000 computers in various locations around the country – I turned to Powershell and the . The results were both very surprising and disconcerting. Hundreds of our computers were out of date and not reporting this to the SEP Manager. If a computer get’s a corrupt policy, chances are the Symantec Management Client (SMC) service will stop and refuse to restart. When this happens, the component of SEP responsible for updating definitions and reporting out of date definitions stops working. The issue causing the update issue may be resolved by the improved processing and enhanced features available in a software version later than what is running.Most common reasons for update failure: What you need: 1) Latest Certified Definitions from Symantec.

symantec endpoint not updating-29symantec endpoint not updating-56symantec endpoint not updating-41symantec endpoint not updating-44

Until Symantec come up with, I have a manual solution.

After few minutes , it will automatically push the definition to SEPM console and it will be distributed to clients in few minutes, All of my clients (100 ) took about 20 minutes to update.

Posted: 12/12/2013 in Symantec Tags: Definition update, Definition update problem, Live Update, Not updating virus-definitions, SEP, SEPM, SEPM definitions not updating, Symantec, Symantec Endpoint Protection, Symantec Endpoint Protection Manager, virus-definition update problem If you have encountered SEP virus-definition update problem on SEPM recently (late 2013) and if this is a large enterprise’s production system which keeps about 30 definition revisions, the reason is most probably the max.

I wish this saves a few hours of you SEP experts/admins.

If you’ve ever administered clients running Symantec Endpoint Protection 11 (SEP), you know how woefully inadequate the SEP management interface is for determining the health of your clients.