stop symantec endpoint protection from starting

Symptoms: Clients that have upgraded to Symantec Endpoint Protection 14.2 do not appear correctly in Symantec Endpoint Protection Manager. Solution: Fixed an issue with duplicate entries in LiveUpdate Content policy during Replication.Ĭlients are showing as offline in SEPM after upgrading to SEP 14.2 If unmanaged, ccSvcHst.exe CPU usage is normal. Symptoms: ccSvcHst.exe causes high CPU usage on managed Symantec Endpoint Protection clients. Solution: Fixed the stored procedure used for this API command so that it checks the user name and domain name in the query.ĬcSVCHst.exe causes high CPU usage only on managed SEP clients

Symptoms: The GetComputers API command unexpectedly lets you put different users on the same physical computer into different groups, which then apply different policies in Symantec Endpoint Protection Manager. Solution: Updated the drivers to let this traffic correctly pass through the firewall.ĪPI command returns inaccurate computer data for clients in user mode Symptoms: The Endpoint Protection firewall sometimes does not allow traffic based on the application name. New fixes Firewall does not recognize traffic by application name This information supplements the information found in the Release Notes.

This document lists the new fixes and component versions in Symantec Endpoint Protection (SEP) 14.2 MP1.

Stop symantec endpoint protection from starting