Symptoms: Location Switching may intermittently fail when it relies on DNS Lookup as a criteria within Location Awareness. Solution: Added the client group name to external system-client logging to allow Splunk to operate properly.Ĭlients do not switch locations when using DNS Lookup criteria with Location Awarenessįix ID: ESCRT-1710, ESCRT-1773, ESCRT-1801 Symptoms: Because some of the policy numbers received from Symantec Endpoint Protection Manager by Splunk begin with the same four digits, Splunk shows the clients in the wrong groups. Non-uniqueness of 4-digit policy numbers causes issues with Splunk Solution: Added type conversion to the SQL statement to prevent this performance issue.

0100 (schema version 14.2.0.2), you see excessive CPU utilization on the SQL Server when Application Learning is enabled.

Symptoms: After you upgrade from Symantec Endpoint Protection. New fixes SQL Server experiences performance issues after an upgrade to 14.2 MP1

You can also download client-only patches through Symantec Endpoint Protection 14.2 RU1 MP1 client-only patches. For details, see Download the latest version of Endpoint Protection. This information supplements the information found in the Release Notes.ĭownload the full release through MySymantec. This document lists the new fixes and component versions in Symantec Endpoint Protection (SEP) 14.2 RU1 MP1 (14.2.1.1).

Sepm 14.2