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

How to set LiveUpdate cache settings for clients from a central location?

Created: 02 Jul 2012 • Updated: 02 Jul 2012 | 4 comments
This issue has been solved. See solution.

I've searched this forum and found some articles relating to this questions, but none of the actually answer it.

Is it possible to centrally control the client cache size for LiveUpdate? I need to be able to set a policy of some sort and apply it to all my servers.

Comments 4 CommentsJump to latest comment

Swapnil khare's picture

Do you have GUP Configured in the network ?

If you dont have it configured , please do so you can configure Cache through this for Liveupdate

Maximum disk cache size allowed for downloading updates The maximum disk space to use on the Group Update Providers for storing content updates.

The unreserved disk space is kept to the limits as content updates are downloaded. Once the limit is reached, the Group Update Provider continues to serve the clients, but only for the existing content.

http://www.symantec.com/business/support/index?page=content&id=TECH96419

See option Maximum Disk cache size allowed for downloading updates .....

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

PolishPaul's picture

Isn't this value for the GUP itself, not the clients? I tried experimenting with this earlier and the client settings did not change.

John Q.'s picture

It cannot be set up using SEPM policies, because LiveUpdate cache is configured locally in settings.liveupdate file (within "C:\ProgramData\Symantec\LiveUpdate" or "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate" folder).

If you edit this file, you will notice a line related to cache size:

PREFERENCES\CACHE_LIMIT=10485760

You just need to change it. If you want to apply such change widely, I would suggest you to use settings.merge.liveupdate file, containing only the line related to cache limit with proper value, and to drop it on all your machines (using a script or 3rd party management tool):
http://www.symantec.com/docs/TECH106109

Please remember to mark the proper comment as SOLUTION:
 - to identify threads that do not require further assistance
 - to let other visitors know how to fix such issue

SOLUTION
PolishPaul's picture

Excellent! As much as i searched i could not find that article!

Follow up question - is there a way to automate clearing the cache?