Symantec endpoint protection client not updating definitions

During this time while they thought a GUP was being used, all clients at this remote site were actually updating definition directly from the SEPM.

Related Content: Take Your SEP Reporting to the Next Level with SOLVE Brent M.

These updates occur roughly three times a day on average.

While in the field we have seen clients use GUPs in different ways, the purpose of the GUPs was to reduce bandwidth requirements.

Since the controls are in place to insure that definitions originate from a SEPM to the GUP this will not occur.For sites with a very small number of clients, it is unlikely that a GUP would be needed.Depending on how you publish definitions within your environment, something else to consider is the difference between cheap and expensive bandwidth.If the client is not able to download the definition from the GUP due to the amount of time it takes or if the GUP is unavailable, it will then default to pulling definitions from the SEPM.This is to insure that definitions are available to the client even if GUPs are unavailable. To understand the bandwidth savings of using a GUP it is important to understand the amount of traffic generated by definitions updates.

Search for symantec endpoint protection client not updating definitions:

symantec endpoint protection client not updating definitions-87symantec endpoint protection client not updating definitions-3symantec endpoint protection client not updating definitions-18symantec endpoint protection client not updating definitions-71

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “symantec endpoint protection client not updating definitions”