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.
TEM managed clients should receive updates automatically from the server.
If a client is not receiving updates automatically, follow this process.
Depending on the mixture of operating systems within your environment, this is important to know.
If you are trying to schedule updates to occur only at certain time periods through the day, this can only be achieved by using a Live Update server. Group Update Providers work by requesting definitions from the SEPM directly.
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.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.If the GUP does not have a definition it will reach out to its defined SEP Manager and download the correct update.On the next heartbeat interval the client will then download the definition from the GUP.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.