Get the Latest Version of LiveUpdate Administrator for Symantec Products
Symantec products download updates from the Internet using a LiveUpdate client by default. Configuring and administering an LUA infrastructure adds several layers of complexity to the process of updating Symantec products.
download liveupdate administrator
LUA requires a very large amount of free disk space to function properly. Ensure there is enough available storage to house all content downloaded/distributed by LUA without running out of free space. Use the following guidelines when configuring an LUA server's disk(s):
LUA has a limited amount of memory and threads to handle scheduled tasks like downloading and distributing content, purging downloads and distributions, and database maintenance. These resources are also shared by built-in testing and production distribution centers. Use the following guidelines to ensure smooth operation of LUA's tasks:
LUA is an enterprise web application that lets you manage Symantec updates on an internal LiveUpdate (LU) server. LUA can be configured to download content for various products such as SEP, DCS, SMS, SPE, etc. LUA retrieves content from an external Symantec LU server to be published to Distribution Centers where clients can download from. Content can also be sent to a Testing Distribution Center before publishing so content can be vetted before being released to the entire environment.
How to download liveupdate administrator for endpoint protection
Liveupdate administrator installation and configuration guide
Download liveupdate administrator latest version 2.3.11
Liveupdate administrator best practices and system requirements
Troubleshooting liveupdate administrator issues and errors
Liveupdate administrator release notes and new fixes
Liveupdate administrator online help and documentation
Liveupdate administrator product catalog and components
Liveupdate administrator download schedule and status
Liveupdate administrator distribution center and testing center
Liveupdate administrator supported products and languages
Liveupdate administrator web application and server setup
Liveupdate administrator apache tomcat and postgresql services
Liveupdate administrator user interface and login credentials
Liveupdate administrator backup and restore procedures
Liveupdate administrator security and encryption settings
Liveupdate administrator proxy and firewall configuration
Liveupdate administrator logs and reports generation
Liveupdate administrator performance and optimization tips
Liveupdate administrator license agreement and terms of use
Download liveupdate administrator for data loss prevention
Download liveupdate administrator for mail security
Download liveupdate administrator for endpoint security complete
Download liveupdate administrator for symantec protection engine
Download liveupdate administrator for symantec messaging gateway
Download liveupdate administrator for windows server 2019
Download liveupdate administrator for linux operating system
Download liveupdate administrator for mac os x platform
Download liveupdate administrator for virtual machines and cloud environments
Download liveupdate administrator for mobile devices and tablets
Download liveupdate administrator from mybroadcom portal
Download liveupdate administrator from knowledge base article [^1^]
Download liveupdate administrator from techdocs website [^3^]
Download liveupdate administrator from symantec support site [^2^]
Download liveupdate administrator from third-party sources (not recommended)
Download liveupdate administrator free trial and demo version
Download liveupdate administrator patch and update files
Download liveupdate administrator offline installer and standalone package
Download liveupdate administrator alternative software and tools (not recommended)
Download liveupdate administrator user reviews and ratings
Scheduling DistributionAfter you've downloaded your updates, they can be sent to either a testing distribution server, or published to a production distribution server where they can be downloaded by your LiveUpdate clients. When you add a distribution schedule, you also select the products and components that you want to associate with the schedule. This list of products and components is compared with the updates in the Manage Updates folder. Any revisions that are not already published will then be published in the current distribution session.Note: The added products must also be added to the distribution center/s. This is accomplished through Configure > Distribution Centers, then edit an existing distribution center to add to the Product List.To add a new distribution schedule
What we believe is happening here is that in order for LiveUpdate to retrieve the updates you need, a catalog file and the update referenced in that catalog file both need to be retrieved. The catalog file gets downloaded first.. If for some reason the catalog file is available but the update is not, then this problem could occur. Typically these files would always be available at the same time.
We are looking at making a change so as not to report this as a problem, because if either of these are not availalbe, there really is no point in even offering the new update for download/distribution.
i have uploaded the log files to the site you given me in private message. Actually,i just setup the LUA server.i did a first time download and it failed. therefore i cant run the scheduled distribution at all.
Stay tuned for the solution to your download schedule failure problem. Note that the next schedule will resolve the download failure, but as I noted we are looking at eliminating this error in the next release.
Can i direct all my current SEP client to download updates from Liveupdate Administrator although the job which download virus definition always fails? According to Activity Monitor->Request details,some virus definitions were downloaded successfully,some skipped and 4 failed. Will SEP clients be updated with latest definition in this way? if yes,i will do so while waiting resolution from you. my concern is my network bandwidth..
Hi there,Wondering if somebody could explain something for me. I have taken over a project which involves 200 SEP clients and 1 SEPM server. The updates for the 3 areas of SEP (i.e AV+SW, Threat Protection etc) used to come via the SEPM server. This worked fine, however the updates which went to the clients were around 6mb after 1 or two days. Leaving for a substantial period of time would leave you with an update of around 60mb.As our users are coming over 3g cards (and associated data tarriffs) it is not acceptable to have these large updates. I am ONLY concerned with the Antivirus/AntiSpyware updates/module, therefore it seemed obvious to install a LiveUpdate Administrator Server (on the same SEPM box).I have installed the LiveUpdate Administrator server, choose the SEP v11 English product, and then selected to download and distribute only the parts for AV+SW (Followed a link from this forum). The LU server downloads updates once a day and distributes them to the production 'area' URL on the same box.I have then told my 200 clients to 'get' their updates from the LiveUpdate Server using the SEPM console. I have made a LiveUpdate Content Policy with just the area I am interested in (AV+SW) and also setup the LiveUpdate Policy for the clients to download no product updates etc.The clients have the latest policies, and download from the LU server. However, after 5 days of 'switch off' the client will sometimes download 1.4mb of data (AV+SW updates!) GREAT, but then over the next 5 days it will then ask to download about 60mb of information?! (I'm getting this size from the LiveUpdate window when it runs).My goal is to only get the AV and Spyware module 'updates' to the 200 SEP clients, and only the English 32bit files. Can somebody explain how LiveUpdate Administrator works with downloading from its upstream servers, and what it downloads? Also if somebody can explain how I can enable logging on the SEP clients to show more detail about the AV updates they have and what it is comparing too to receive an update of 60mb!I would 'expect' that the updates I need are only small (1mb) in size every week or so? I need to resolve this as our bills for mobile data will be through the roof! Can somebody assist with some information?Thanks in advance.
I am unable to allow the SEPM server to connect to Symantec LiveUpdate due to network restrictions so I've implemented an LAU server with the hop i could use it to download the required updatees and then use SEPM to distribute them to the clients.
I thought we had this working in that the LAU server is able to download the content and I seem to be able to configure SEPM to download them from LAU by configuring the site LiveUpdate settings to Use a specified internal LiveUpdate server and (after some experimentation) using the URL OF LAU:7070/clu-prod. I have LAU setup to not require and testing and once I run distibution the downloaedd content ends up in that folder... all good...
However when I run Download LiveUpdate Content I get a screen full of No updates found for.... messages, in the last few days of working on this issue (the system is currently in our Test/Dev enviroment not live) I have had the system download a few files but it isnt consistent and if I alter the settigns I get Error-4 so I'm fairly certain I am accessing the folder.
I'm also a little concerned that in all the efforts to get this working i have soemthing out of synch as on the home screen the Latest on Manager is showing 17/09/2018 despite me having cleared out the downloaded files a number of times, is theer a way to intitalise the system without tearing it down and deleting the SQL DB ?
Have you tried refreshing the download? Delete the 14.0 catalog selection, refresh the catalog select all 14.0 components. Setup in distribution source, refresh the download and distribution jobs. The restart the LUA tomcat and DB services?
This means that it will always retrieve the smallest and most efficient package possible. It will not download any unnecessary content. An LUA is designed to apply updates generally to a mixed environment. It will update itself on a schedule, and will download all content available at that time. An LUA downloading 32-bit and 64-bit windows definitions only may download 4-6 GB of data per month. The equivalent GUP is likely to download less than 500 MB.
LiveUpdate Administrator is a full application that runs on Microsoft IIS. It automates the download and distribution of security and client updates to it's own distribution web sites, or any other web server chosen to configure. It can provide content updates for non Windows SEP clients (e.g. SAVFL, SEP for Mac, SMSMSE, etc).
Note: If the client is pulling down content from LiveUpdate or LiveUpdate Administrator, please run LiveUpdate. If the client is pulling down content from the SEPM, the content will be automatically downloaded without any interaction. Until the content is delivered, the client UI may show with a warning due to missing content.
If you have already installed Citrix Workspace app for Windows, download and install the latest version of the app from the Citrix Downloads page. For information on the installation, see Install and Uninstall.
This error could also occur when downloading and updating with the Adobe Application Manager. The error can be bypassed by downloading the update separately from installing it. That is, save the updater file locally (on your computer) and then run it in a separate step.
After clicking Proceed to Download and then Download Now, click Save or Save As to save the file to your computer. After downloading, locate the patch file on your computer and double-click the file to run the update.
Enterprise Manager administrators must have the requisite privileges to use the Self Update feature. The Enterprise Manager Super Administrator must assign the following Self Update roles/privileges to these administrators:
The Software Library is a repository that stores software entities such as software patches, virtual appliance images, reference gold images, application software, and their associated directive scripts. In addition to storing them, it also enables you to maintain versions, maturity levels, and states of these software entities. In the context of applying updates, it is the "local store" that entities are downloaded to before deployment.