Symantec endpoint protection client not updating from the server

Can all clients be defined as a Group Update Provider?

The GUP technology in SEP allows administrators to designate client systems within the environment to distribute client definitions in a peer fashion.

In an environment where a GUP is configured, clients designated to use GUPs will reach out on port 2967/TCP to see if there is a definition update available.

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.

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.Things you need to be aware of when using Group Update Providers The most important thing to understand is that GUPs only work with Windows clients.Linux and OSX clients will not use the GUP functionality at all.We have run into scenarios where SEP administrators have configured remote client desktops as GUPs.A few months later it was discovered that these systems have been decommissioned and replaced.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.

Tags: , ,