
This means that clients will still need network connectivity to a SEPM in order to perform the heartbeat process, which updates their policies, and informs them when new content is available to download 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.

Because of these changes, it is highly recommended that both the SEPM and SEP clients are running the latest available version of SEPM/SEP. In order to take advantages of these changes, both the SEPM and the SEP clients will need to be running SEP 11.0 MR3 or newer. There have been significant changes to both the GUP architecture and the content delta process over the development cycle of the SEP product. The total physical hard disk space available on the GUPĭetermining Worst Case Scenarios for bandwidth and storage usage There are several considerations that need to be made before utilizing GUPs are part of the overall content updating scheme in an environment: Other SEP clients can be configured to utilize the GUP for definition and content updates via LiveUpdate policiy from the Symantec Endpoint Protection Manager (SEPM).

When assigned the GUP role, a SEP client will act as a caching HTTP proxy - storing both delta and full revisions of SEP content. The GUP role can be assigned to any SEP client.
