Endpoint Protection

Hi,

to face some requirements in our company, I'm trying to use LUA (Version: 2.2.2.9) to provide updates to some specific clients.

What I'm concerned about is the size of the VDF LUA server download from Symantec. Every update it downaload 3GB, having as product only SESC Virus Definition (both 32 adn 64 bit )

Is that normal or some misconfiguration taking place?

Can you help?

Thansk

Please Clear corrupted definitions

How to clear out corrupted definitions for a Symantec Endpoint Protection client manually

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

Check this same thread

http://www.symantec.com/connect/forums/why-have-liveupdate-virus-def-downloads-increased-size-starting-jan-2010

Hello,

First of All, I would request you to make sure you are running the Latest version of LUA 2.3.1.

The newer LUA 2.3.1 is on the DVD of the newly released SEP 12.1 RU1 MP1.   You can also get a copy by getting in touch with Tech Support.

Secondly, check this Article:

Managing LiveUpdate Administrator 2.x Space Usage

https://www-secure.symantec.com/connect/articles/managing-liveupdate-administrator-2x-space-usage

LiveUpdate Administrator 2.x: What product selections are needed for specific versions of Symantec Endpoint Protection? (http://www.symantec.com/docs/TECH139618)

and these Threads:

https://www-secure.symantec.com/connect/forums/sepm-folder-clu-prod-taking-all-my-disk-space

https://www-secure.symantec.com/connect/forums/liveupdate-packet-size-reaching-1gb

Secondly in case, if you have the SEPM and LUA installed on the same server, check this Article:

LiveUpdate Administrator 2.x and Symantec Endpoint Protection Manager on the Same Physical Server

Hope that helps!!!

Check this artical

How Big are Current Symantec Endpoint Protection Definitions?

https://www-secure.symantec.com/connect/articles/how-big-are-current-symantec-endpoint-protection-definitions

Hi Mirparx,

"Thumbs up" to the advice, above!

Do you still need assistance with this question?  The thread is currently marked "needs solution."