Animated sex chat bot - Symantec endpoint protection client not updating gup

This is a scenario where some people could believe that the environment would act in a full peer-to-peer fashion.

Since the controls are in place to insure that definitions originate from a SEPM to the GUP this will not occur.

A freshly installed client will take a few hundred megabytes to get updated to the latest definition set.

Since differential updates are normally small, in an environment where all the traffic is on the same local LAN as the SEPM, it almost is never beneficial to use GUPs in this scenario.

While some bandwidth could be recovered by putting a GUP on each subnet, the management of a large-scale GUP environment in a local LAN will likely take more time and effort than any nominal bandwidth savings.

Can all clients be defined as a Group Update Provider?

Recently we had a customer ask if all systems could be GUPs.

In theory all clients in an environment can act as a GUP. What it is going to do is require all clients to reserve more hard drive space because they will all save separate definitions to be available to any possible peers.

In this scenario none of the agents will actually communicate with another GUP since a GUP can only retrieve updates from a SEPM.If you have an environment where you have a separate Live Update in your environment, the GUPs will not request definitions from this system.Depending on how clients are chosen to be GUPs, the antivirus team will need to be aware of any system decommissions.On a subnet over a WAN link, you would have a single client retrieving definitions from the SEPM.This is the same whether you have ten clients over the remote WAN link or two hundred.If the GUP does not have a definition it will reach out to its defined SEP Manager and download the correct update.

Tags: , ,