Notes

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======Symantec Endpoint Protection======

=====12.1=====
====Tech Notes====
[[http://www.symantec.com/docs/HOWTO53168|About Symantec Endpoint Protection product guide locations]] \\
[[http://www.symantec.com/docs/TECH195029|Third-party security software removal support in Symantec Endpoint Protection 12.1.2 and later]] \\

=====Notes=====

====File System Auto-Protect does not scan inside archives====
The File System Auto-Protect functionality does not scan inside archives. \\
This also can't be enabled (at least not on version 12.1). \\

Sources: \\
[[http://www.symantec.com/connect/ideas/check-threats-inside-compressed-files-option-auto-protect|Symantec Connect - Check for threats inside compressed files option in auto-protect]] \\
[[http://www.symantec.com/connect/forums/auto-protect-not-catching-malware-manual-scan-does|Symantec Connect - Auto-protect not catching malware, manual scan does]] \\
[[http://www.symantec.com/connect/forums/autoprotect-do-not-scan-files-archives|Symantec Connect - autoprotect do not scan files in archives]] \\

====DefWatch Quick Scan====
The scan that runs after the definition files have been updated.
Can be disabled.

Source: [[http://www.symantec.com/business/support/index?page=content&id=TECH101323|Symantec KB - Disabling the Quick Scan that runs after virus definitions update in Symantec AntiVirus 10.0 and Symantec Client Security 3.0]] \\

====SRTSP64.SYS high CPU usage====
A system with SEP is fully utilizing one CPU core with the System process.

Closer examination with Process Explorer reveals that the CPU time is spent on SRTSP64.SYS.

This is a known issue with SEP 12.1 RU1 - 12.1 RU4 MP1b.

Workaround: Disable "Rescan cache when new definitions load" at the Auto Protect File Cache settings in SEP.

Source: [[http://www.symantec.com/connect/forums/srtsp64sys-cpu-usage-high|Symantec Connect - srtsp64.sys cpu usage high]] \\