Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Gup Configuration

Created: 09 Oct 2012 • Updated: 09 Oct 2012 | 5 comments
SameerU's picture

Hi

We have SEPM server with SEP 11 RU6 MP2 installed and around 2500 clients reporting.

We have configured GUP in each location, but need to clear some doubts in regards with GUP configuration

1. What is the system requirements for GUP ?

2. Space needed on GUP to which for e.g about 50 - 100 clients are communicating ?

3. How many revisions to be kept in GUP ?

3. If a client is not communicated for a month, how the client would take the update and whether it would be incremental or full update ?

Regards

Sameer

Comments 5 CommentsJump to latest comment

Chetan Savade's picture

Hi SameerU,

Q.1. What is the system requirements for GUP ?

--> Go throught the following article

There is not any specific requirement however please go throught the best practice article.

http://www.symantec.com/business/support/index?pag...

2. Space needed on GUP to which for e.g about 50 - 100 clients are communicating ?

--> Group Update Provider: Sizing and Scaling Guidelines

http://www.symantec.com/business/support/index?pag...

3. How many revisions to be kept in GUP ?

--> By default SEP clients keep 3 revision.

3. If a client is not communicated for a month, how the client would take the update and whether it would be incremental or full update ?

--> It depends upon configuration, By default SEP clients try to contact GUP first & if GUP is not allowed then clients will try to contact SEPM.

About configuring rules for multiple Group Update Providers

http://www.symantec.com/docs/HOWTO55244

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

SMLatCST's picture

"Thumbs Up" to the above!  I've only got a couple of points to add...

  1. As Chetan mentioned, there aren't really any particular requirements for GUPs.  They are just normal SEP Clients that proxy content.  As such, they just need a bit of extra disk space (I'll come to that in a moment).
  2. The disk space used by the GUP function is configurable, and is set to 500MB by default.  You can change this as you see fit.
  3. A GUP only caches what has been requested of it, and doesn't really have any concept of definition revisions.  Whatever it does cache is automatically deleted after 3 days without use.  This effectively means everthing is deleted after 3 days, because whatever is cached on a GUP is redundant as soon as a new deifnition is available.
  4. As far as you last question goes, the duration a client is off does not affect how it gets updates.  It will still go through the GUP, etc.  It does affect what is downloads though, and this depends on how many definiton revisions your SEPM is retaining.  In your example, if using Symantec Best Practices, a machine that has been off for 30 days will request the full definitions from the GUP.

Please review the below articles on when delta definitions are used, and when full definitions are used.  I've also linked the Symanetc Best Practices on the recommended number of definiton revisions your SEPM would ideally retain.  I've left out the GUP recommendations as the others have already linked these.

http://www.symantec.com/docs/TECH131528

http://www.symantec.com/docs/TECH92225

http://www.symantec.com/docs/TECH92051

Sumit G's picture

Thumb up the above comments.

Find the attach link which can help to create the GUP

https://www-secure.symantec.com/connect/downloads/create-gup-symantec-can-help-conserve-bandwidth-clients-remote-location

Only that clients getting update from GUP which are available on assigned Group.

Every client getting the full update from Server/GUP even it pending update from long time.

Regards

Sumit G.

Sumit G's picture

Your requirement fulfill or not?

Regards

Sumit G.