Symantec managed clients not updating

How to clear out corrupted definitions for a Symantec Endpoint Check if SEPM has Latest Definitions: DONE - 1.Open SEPM-If this process displays any errors like return code 4 or the liveupdate does not complete then follow this document to uninstall liveupdate and reinstall liveupdate and re-register SEPM with liveupdate: Regards, Pradeep Jhala Hi Pradeep Thank you for your post.You use the APIs if you do not have access to Symantec Endpoint Protection Manager.This document is intended for developers who want to write applications that interact with Symantec Endpoint Protection Manager.Sends a command from Symantec Endpoint Protection Manager to add Symantec Endpoint Protection clients to (or remove them from) network quarantine.A system administrator account is required for this REST API. Possible values are Cent Os, Debian, Fedora, Mac OSX, Oracle, OSX, Red Hat, SUSE, Ubuntu, Win10, Win2K, Win7, Win8, Win81, Win Emb7, Win Emb8, Win Emb81, Win Fundamental, Win NT, Win2K3, Win2K8, Win2K8R2, Win2K12, Win2K12R2, Win2K16, Win Vista, Win XP, Win XPEmb, Win XPProf64The list of OS to filter.

Symantec's work-around for right now is to leave the date on the file as 12/31/2009 and increment the rev #. I presume it would as this is how I noticed that there is a problem?

(Please see attached screenshot) I just find it strange that not all my workstations are affected.

I only have the 14 workstations that seems be an issue.

All APIs exposed by Symantec Endpoint Protection Manager carry authentication tokens and other privileged data.

To ensure the confidentiality of the data, the REST APIs are only available over a secure connection.

Leave a Reply