Symantec endpoint protection clients not updating from sepm


This tells any SEP Client with anywhere in its hostname, to start acting as a GUP and add itself to the Multiple GUP List.

Once added, any SEP Client using that Multiple GUP list, will pick a GUP in its own subnet, and start relaying content requests through that GUP.

These can be defined by hostname or IP address only, and are best suited for remote sites that may have a relatively small number of SEP Clients spread over multiple subnets.

Each step is described in more detail further down.There is obviously more administrative overhead in using this option, but may be of use if you want the versatility of adding a single criterion to identify a variety of machines without having to rename them (which involve reboots).You can choose between the presence or absence of a registry key, key name, or a match on a key value.As we can see in the above picture, there is an optional section for adding the details of a Backup GUP.This is defined in the same way as a Single GUP, by using the IP address or hostname, and is used in the event that one of the SEP Clients identified in the Multiple GUP List is not available in the clients local subnet.As mentioned earlier, you must ensure your intended GUP receives the policy telling it to act as a GUP.

You must have an account to comment. Please register or login here!