symantec endpoint protection manager support

The problem has been confirmed to be Windows XP-only (though that may include Server 2003). When the system has been updated properly in the client user interface for Proactive Threat Protection the definition versions will be Wednesday, Jr12 Until the content is delivered, the client UI may show with a warning due to missing content. If the client is pulling down content from the SEPM, the content will be automatically downloaded without any interaction. Note: If the client is pulling down content from LiveUpdate or LiveUpdate Administrator, please run LiveUpdate. Delete the latest content directory (should be 20120711.011).Navigate to the Symantec Endpoint Protection definition directory: C:Documents and SettingsAll UsersApplication DataSymantecSymantec Endpoint ProtectionCurrentVersionDataDefinitionsBASHDefs.Start computer in safe mode (do not use safe mode with networking).On affected client machines running Symantec Endpoint Protection 12.1 Open the Symantec Endpoint Protection Manager.To work around the issue please follow these steps on the impacted machines.įor Enterprise customers, make sure you have updated to the latest virus definitions on the Symantec Endpoint Protection Manager(SEPM) Symantec has posted updated signatures which resolve the issue to the public LiveUpdate production servers. They have also provided a KB article that includes a solution for affected customers. Symantec has acknowledged and summarized the issue in a blog post. Norton 2010, 2011, or 2012 consumer security product.

Symantec Endpoint Protection.cloud (SEP.cloud).

Symantec Endpoint Protection (SEP) 12.1.

Symantec Endpoint Protection Small Business Edition (SEP SBE) 12.1.

Following the detection and investigation, the SONAR signatures were found to be at fault and rolled back to a previous version.īased on our analysis, the problem is isolated to Windows XP machines running: They also explained the quality assurance steps taken to review signature updates.

The issue first cropped up in the Symantec forums where more information was gathered and Symantec was able to reproduce the problem.

Symantec endpoint protection manager support