Symantec endpoint protection managed client not updating email dating mail ru ukraine 2016
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.
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.
In some environments client communication will go over the WAN while Internet traffic will traverse through a cheaper local ISP.
In this scenario one serious discussion should be if it is better engineered to have all clients retrieve their definitions directly through the Internet to Symantec’s public Live Update servers.
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.
If a client is not receiving updates automatically, follow this process.
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.
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.
The GUP technology in SEP allows administrators to designate client systems within the environment to distribute client definitions in a peer fashion.