Sep definitions not updating
I have made no changed to any internet/firewall settings. 053" As per my screenshot, my console is showing the following: 2010-01-11 rev. As per above mentioned link, I have done the test with the below results: b. Run a packet capture and contact support for analysis Check Connectivity between SEP & SEPM: PASSED - 1.Do a Secars test to Test Connectivity between SEP and SEPM Testing Communication from an Endpoint Protection client to the Endpoint Protection Manager In Progress - 2.So it is basically a waiting game from here onwards then? It just concerns me the fact that some of our users are still getting the yellow icon.Can I please ask; are you also experiencing that only some of your workstations are experiencing this issue? Kind regards, mustekkzn All of the workstations that were previsouly managed in 2009 and are now getting updates with 12/31/09 rev 126 are not throwing any errors. I'm not sure why you get the yellow icon on the others.Get the sylinkmonitor logs to check the communication for any errors Sylink Watcher and Sylink Monitor - tools for real-time debugging of SPA 5.x and SEP 11.x DONE - Remove corrupt definitions 1.How to clear out corrupted definitions for a Symantec Endpoint Check if SEPM has Latest Definitions: DONE - 1.Symantec's work-around for right now is to leave the date on the file as 12/31/2009 and increment the rev #. I presume it would as this is how I noticed that there is a problem?(Please see attached screenshot) I just find it strange that not all my workstations are affected.
Traditional signature and heuristic file scanning engines form the backbone of Symantec’s security solutions; these engines use dozens of techniques to scan files for both known as well as unknown threats.
I only have the 14 workstations that seems be an issue.
Also, according to the below link, there is a patch out for this problem.
However, my clients show the green ball on the shield...
which I believe just means that the client is communicating with SEPM. but I would suspect that there is something wrong between the client and SEPM server.
Anyone else seen this happen and know how to fix it?