Since the GUP is essentially a SEP client with the additional GUP role, it must also be able to access the SEPM through the client management port. The only method to update both content and policies on a client is through a SEPM. This port is configurable within the product. Depending on the version of SEPM used in your environment, the default client management port is either 8014 or 443. If the SEP clients you need to update using a GUP are not able to connect to the HTTP/S ports used by the SEPM for client management, consider another method of updating clients. Clients still need network connectivity to a SEPM to perform the heartbeat process, which updates their policies and informs them when new content is available from the GUP. GUPs can be used to supplement or replace a SEPM for distributing content updates to SEP clients, but cannot be used to update policies or manage clients.

Other hardware and software limitations of the GUP.

Total physical hard disk space available on the GUP.

Enabling GUP on a SEPM server should be avoided.Ĭonsider the following before using GUPs as part of the overall content updating scheme in an environment:

SEP clients working as GUP should be installed with the same version as the SEPM. Other SEP clients can be configured to use the GUP for definition and content updates using LiveUpdate policies from the Symantec Endpoint Protection Manager (SEPM). When a SEP client is assigned the GUP role, it acts as a caching HTTP proxy, storing both delta and full revisions of SEP content. The GUP role can be assigned to any SEP client.

Sep broadcom