Symantec endpoint protection unmanaged client not updating

03-Aug-2018 06:02

You can now also configure the number of days to keep delta merge files in conf.properties, with the value scm.delta.merge.delete.

Endpoint Status does not show Out-of-Date clients to Limited Administrators FIX ID: 3816777 Symptom: The Endpoint Status report does not display the appropriate data for out-of-date clients to Limited Administrators.

Large numbers of files in Sym Delta folders result in out of disk space issues FIX ID: 3872101 Symptom: Large number of files in Sym Delta folders result when the definition delta merge continuously fails.

symantec endpoint protection unmanaged client not updating-77symantec endpoint protection unmanaged client not updating-29

Solution: Changed to allow the user to set a total amount of maximum memory used by all GUP threads.The Managed Client is intended for use on LSU owned computers.Tasks, such as definition updates and scheduled scans, are setup automatically via LSU’s Endpoint Protection server. The Unmanaged Client is intended for personal computers and LSU owned computers that are normally located off-campus.Solution: Updated Java Live Update (JLU) to fix a logic error.SEPM does not update and other policy files as expected FIX ID: 3869825 Symptom: Symantec Endpoint Protection Manager does not publish policy files, such as profile.xml, which therefore do not update on the client.

Solution: Changed to allow the user to set a total amount of maximum memory used by all GUP threads.

The Managed Client is intended for use on LSU owned computers.

Tasks, such as definition updates and scheduled scans, are setup automatically via LSU’s Endpoint Protection server. The Unmanaged Client is intended for personal computers and LSU owned computers that are normally located off-campus.

Solution: Updated Java Live Update (JLU) to fix a logic error.

SEPM does not update and other policy files as expected FIX ID: 3869825 Symptom: Symantec Endpoint Protection Manager does not publish policy files, such as profile.xml, which therefore do not update on the client.

The maximum memory splits evenly between all threads (download and server).