liveupdate administrator users guide

Symantec LiveUpdate™Administrator 2.2 User'sGuide

Symantec LiveUpdate™Administrator 2.2 User's GuideThe software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version 2.0

Legal NoticeCopyright © 2008 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, LiveUpdate, Symantec LiveUpdate Administrator, andSymantec AntiVirus are trademarks or registered trademarks of Symantec Corporation orits affiliates in the U.S. and other countries. Other names may be trademarks of theirrespective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS ANDWARRANTIES, INCLUDING ANY IMPLIEDWARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTIONWITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGEWITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’sMaintenance Programs, you can visit ourWebsite at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomerswith a currentmaintenance agreementmay access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system



■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you tomaximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

SymantecEarlyWarningSolutions

These services remove the burdenofmanaging andmonitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trustedpartners. SymantecConsultingServices offer a varietyof prepackaged and customizable options that include assessment, design,implementation,monitoring, andmanagement capabilities. Each is focused onestablishing andmaintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Introducing the Symantec LiveUpdateAdministrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About the Symantec LiveUpdate Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9What's new in the Symantec LiveUpdate Administrator ... . . . . . . . . . . . . . . . . . . . 10What you can do with the Symantec LiveUpdate Administrator ... . . . . . . . . . 11Where to get more information about LiveUpdate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 Installing and using the Symantec LiveUpdateAdministrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Before you install .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13System requirements for the Symantec LiveUpdate

Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Installing the Symantec LiveUpdate Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . 16

Running the LiveUpdate Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Using a remote connection to the Symantec LiveUpdate

Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Managing updates with the Symantec LiveUpdate

Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Using the Symantec LiveUpdate Administrator Home page .... . . . . . . . 20

Post-installation tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Updating the Symantec LiveUpdate Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . . 23Uninstalling the Symantec LiveUpdate Administrator ... . . . . . . . . . . . . . . . . . . . . . 24

Chapter 3 Configuring the Symantec LiveUpdateAdministrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Configuring Symantec LiveUpdate Administrator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Updating the My Symantec Product Catalog .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using My Symantec Products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using coverage information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Configuring Source Servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Working with failover servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Working with distribution centers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Contents

Working with host files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Configuring Symantec LiveUpdate Administrator

preferences ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4 Managing download and distribution schedules . . . . . . . . . 37

Scheduling downloads .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Scheduling distribution .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Using the Activity Monitor ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Viewing request details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41About Download and Distribution status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 5 Managing updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Managing updates for Symantec products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Viewing update details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Deleting revisions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Locking and unlocking revisions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Testing updates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 6 Viewing events and managing users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

About the Symantec LiveUpdate Administrator Event Log .... . . . . . . . . . . . . . . . 53About user management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Roles ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Adding users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Contents8

Introducing the SymantecLiveUpdate Administrator

This chapter includes the following topics:

■ About the Symantec LiveUpdate Administrator

■ What's new in the Symantec LiveUpdate Administrator

■ What you can do with the Symantec LiveUpdate Administrator

■ Where to get more information about LiveUpdate

About the Symantec LiveUpdate AdministratorThe Symantec LiveUpdate Administrator is an enterprise Web application thatallows you tomanage Symantec updates onmultiple internal Central LiveUpdateservers, called Distribution Centers. Using the Symantec LiveUpdateAdministrator, you download updates to the Manage Updates folder, and thensend the updates to production distribution servers for LiveUpdate clients todownload, or to testing distribution centers, so that the updates can be testedbefore they are distributed to production.

You can download and distribute updates on schedule, allowing you to create alow maintenance, reliable system that can be set up once, and then runautomatically. Updates can also be manually downloaded and distributed asneeded.

Figure 1-1 illustrates a typical LiveUpdate Administrator environment.

1Chapter

Figure 1-1 Symantec LiveUpdate Administrator environment

SymantecSourceServer

SymantecLiveUpdateAdministrator

Production DistributionCenter

Testing DistributionCenter

Locations

Locations

1

2

3

1

2

3 LiveUpdateClients

Symantec updates are downloaded from an external Symantec site to an internalSymantec LiveUpdate Administrator server. From there, the updates can eitherbe sent immediately to a production distribution center to be downloaded byLiveUpdate clients, or sent to a testing center, so that the updates can be tested.Once the updates have passed your testing requirements, they are sent to theproduction center, on a schedule you determine.

What'snew in theSymantecLiveUpdateAdministratorThe Symantec LiveUpdateAdministrator includes the followingnew features andenhancements:

The Symantec LiveUpdate Administrator can manage up to100 distribution center locations for Symantec EndpointProtection 11.x content. These locations can be configuredwithin a single distribution center location, or can bedistributed over multiple distribution centers. This enablesusers with a large number of remote sites to manage anddistribute updates from a central location.

Improved scalability

Introducing the Symantec LiveUpdate AdministratorWhat's new in the Symantec LiveUpdate Administrator

10

Users can distribute only the updates that are needed in eachsite, which can reduce overhead and improve performance.

Ability to select a specificplatform for virusdefinitions

It is critical that security content is available for distributionas soon as it is sent to Symantec LiveUpdate servers. TheSymantec LiveUpdate Administrator provides improveddistribution over WAN and in environments with slow linespeeds, as well as for organizations with a large number ofremote sites.

Robust distributionperformance

The bandwidth throttling feature allows the user to managedistribution in environments that have both high and lowbandwidth networks. Bandwidth throttling makes optimaluse of bandwidth to avoid network traffic congestion.

Bandwidth throttling

What you can do with the Symantec LiveUpdateAdministrator

Using the Symantec LiveUpdate Administrator, you can set up and manageDownload and Distribution Centers, also called Central LiveUpdate Servers. TheDistribution and Download Centers can be either intranet HTTP, HTTPS, FTP, orUNC servers, or a directory on a standard file server. Once you have configuredyour production Distribution Centers, you can generate host files for LiveUpdateclients so that they send their LiveUpdate requests to the productionDistributionCenter, rather than to an external Symantec LiveUpdate site.

Where to get more information about LiveUpdateThe SymantecWeb site includes information on troubleshooting LiveUpdate andthe LiveUpdate Administration Utility, product updates, and knowledge basearticles.

On the Web, go to the following URL:


11Introducing the Symantec LiveUpdate AdministratorWhat you can do with the Symantec LiveUpdate Administrator

Introducing the Symantec LiveUpdate AdministratorWhere to get more information about LiveUpdate

12

Installing and using theSymantec LiveUpdateAdministrator


■ Before you install

■ System requirements for the Symantec LiveUpdate Administrator

■ Installing the Symantec LiveUpdate Administrator

■ Post-installation tasks

■ Updating the Symantec LiveUpdate Administrator

■ Uninstalling the Symantec LiveUpdate Administrator

Before you installBefore you install the Symantec LiveUpdate Administrator, you should becomefamiliar with where the setup program installs the software. Make sure that yourLiveUpdate clients are updated to the correct version for full compatibility, andthat your environment meets the system requirements.

The default location for installation is C:\Program Files\Symantec\LiveUpdateAdministrator.

Table 2-1 lists the installed components for the Symantec LiveUpdateAdministrator.

2Chapter

Table 2-1 Symantec LiveUpdate components

Install locationComponent name

<install path>\pgsqlPostgreSQL DBMS

<install path>\pgsql\dataDatabase

<install path>\tomcatTomcat servlet engine

<install path>\tomcat\webapps\luaLiveUpdate Administrator

Web application

Windows 2000, Windows 2003, and Windows WP:

<App_data_path>\All Users\Symantec\LiveUpdateAdministrator\Downloads

For example, C:\Documents and Settings\AllUsers\Symantec\LiveUpdate Administrator\Downloads

Windows Vista and Windows 2008:

<App_data_path>\ProgramData\Symantec\LiveUpdateAdministrator\Downloads

Manage Updates folder

System requirements for the Symantec LiveUpdateAdministrator

This section includes system requirements for the main Symantec LiveUpdateAdministrator components.

The installer package is approximately 50MB. This does not include the JRE thatis required for the Symantec LiveUpdateAdministrator to function. The installedsize is approximately 107 MB, which includes the JRE.

The system requirements for the Symantec LiveUpdate Administrator are asfollows:

Installing and using the Symantec LiveUpdate AdministratorSystem requirements for the Symantec LiveUpdate Administrator

14

Windows2000Server orAdvancedServerwithService Pack4 or higher

Windows2003Server orAdvancedServerwithService Pack2 or higher

Windows XP Professional with Service Pack 3

Windows Vista with Service Pack 0 or higher

Windows 2008 Server

Java™ Runtime Environment (JRE) 1.6

Internet Explorer 6.0, Internet Explorer 7.0, Firefox 3.0/3.1

TCP/IP network protocol

Software

150 MB hard disk space for the Symantec LiveUpdateAdministrator, the JRE, and third-party tools.

5 GB hard disk space for theManageUpdates folder and forthe temporary download folder, \TempDownload. Updatesare copied to the TempDownload folder prior to theirdistribution.

Hardware

Note:Windows XP 64 is not supported.

Symantec recommends using either IIS or Apache Server for hosting yourdistribution center locations. Please refer to your operating system'sdocumentation for additional information.

To install the Symantec LiveUpdate Administrator, you must log on as a poweruser with Administrator privileges. You must be able to create new local users,and to create new services.

Bydefault, the followingports areusedby theSymantecLiveUpdateAdministrator.

Used by the Symantec LiveUpdate Administrator.7070

Used by Tomcat for shutdown commands. While the Symantec LiveUpdateAdministrator will work if this port is closed, Tomcat shutdown operationswill not.

7071

Used by PostgreSQL database.7072

If these ports are being used by other applications at the time you install theSymantec LiveUpdateAdministrator, youwill be prompted to enter alternate portnumbers that the Symantec LiveUpdate Administrator can use.

15Installing and using the Symantec LiveUpdate AdministratorSystem requirements for the Symantec LiveUpdate Administrator

If a firewall is enabled for IP packets sent from the Symantec LiveUpdateAdministrator system, destination IP ports such as HTTP (80), HTTPS(443), andFTP(23), should be allowed for communication. The Symantec LiveUpdateAdministrator communicates with the Distribution Centers using these ports.

Problems may occur while using a Terminal Service for installation. You shouldinstall the Symantec LiveUpdate Administrator directly from the console.

Note: Ensure that MSVCR71.DLL is in the C:\Windows\system32 folder. You cancopy this file from C:\Program Files\Java\jdk1.6.0_0X\bin if it is not present. TheTomcat service may not load if this file is not present in the system32 folder.

Installing the Symantec LiveUpdate AdministratorWhenyou install the Symantec LiveUpdateAdministrator (setup.exe), theApacheTomcat 5.5 and PostgreSQL database 8.2.9 applications are also installed. TheLUA Apache Tomcat and LUA PostgreSQL services for the Symantec LiveUpdateAdministrator are installed and started so that the Symantec LiveUpdateAdministrator is ready to use once the installation has completed. Both servicesare set to run automatically.

If AutoRun is enabled, the setup programwill run automatically. Otherwise, locateand run setup.exe in the root folder on the CD.

To install the Symantec LiveUpdate Administrator

1 Run setup.exe, and then follow the on-screen instructions.

2 If the setup detects that the JRE has not been installed, you will be promptedto download and install it. The installation of the JRE is not controlled by theLiveUpdate Administrator installer. You can install the LiveUpdateAdministrator once the JRE is installed.

You can install the Java Runtime Environment from the Support folder onthe LUA_CD, or download it from www.java.sun.com/.

3 In the Destination Folder window, do one of the following:

■ ClickNext to select the default locations for the installed files folder andthe folder where you want to download updates.

■ Click Change to change the location of the installation file folder or theManage Updates folder.

The default installation folder location is C:\ProgramFiles\Symantec\LiveUpdateAdministrator\.Tomcat, thePostgreSQLdatabase,

Installing and using the Symantec LiveUpdate AdministratorInstalling the Symantec LiveUpdate Administrator

16

LiveUpdate Administrator files, and the documentation are installed to thisfolder.

The default Manage Updates folder is C:\Documents and Settings\AllUsers\Application Data\Symantec\LiveUpdate Administrator\DownloadsforWindows 2000,Windows 2003, andWindows XP. The default location forWindowsVista andWindows 2008 is C:\ProgramData\Symantec\LiveUpdateAdministrator\Downloads. This location cannot be changed after installation.

4 At the Symantec Administrator User Setup window, type your username,password, confirm password, and email address, and then click Next.

5 Click Install.

If any or all of the default ports are currently being used, you are prompted.You can then specify alternate ports for the LiveUpdate Administrator touse. You must restart the LiveUpdate Administrator services after stoppingthe programs that are using these ports. It is not necessary to stop the serviceif you use a port other than the default.

6 Click Finish when the installation is complete.

Running the LiveUpdate AdministratorThe LiveUpdate Administrator setup program adds a shortcut in the Programsmenu under Symantec LiveUpdate Administrator > LiveUpdate Administrator.The installation also adds a shortcut to the desktop.

If youhave installed theLiveUpdateAdministrator onWindows2003with InternetExplorer version 6.0, you may need to add the URL for the LiveUpdateAdministrator to your list of trusted sites.

To run the LiveUpdate Administrator

1 Do one of the following:

■ Click Start, and go to Programs>Symantec LiveUpdateAdministrator,and then click LiveUpdateAdministrator.

17Installing and using the Symantec LiveUpdate AdministratorInstalling the Symantec LiveUpdate Administrator

■ Double-click the LiveUpdate Administrator icon on the desktop.

2 On the Symantec LiveUpdate Administrator window, enter your user nameand password and click LogOn.

If you forget your password, you can request that a temporary password besent to the email address that you specified during installation. Use thistemporary password to sign in to LiveUpdate Administrator. After you signin, you will be prompted to reset your password. For security, the temporarypassword is valid only for a limited time.

Note:The LiveUpdateAdministrator user interface is best viewed using 1024x 768 screen resolution.

Using a remote connection to the Symantec LiveUpdate AdministratorYou can connect to the Symantec LiveUpdate Administrator (LUA) computerremotely. To connect, use the following command structure:

http://Hostname_of_LUA_computer:7070/lua

or

http://IP_address_of_LUA_computer:7070/lua

If you have specified a different port number during installation, use that portnumber instead of 7070.

Managing updates with the Symantec LiveUpdate AdministratorUsing the Symantec LiveUpdate Administrator, you can create a list of Symantecproducts that are used in your environment, designate a source server (optional)to download updates from, and create Download and Distribution centers. Youcan also schedule updates for automatic downloading and distribution. You candefine the types of updates that you want to download, and whether or not theyneed to be tested before they are distributed.

Figure 2-1 illustrates the LiveUpdateAdministrator homepage, where you accessthe options for configuring and managing the LiveUpdate Administrator.


18

Figure 2-1 LiveUpdate Administrator home page

Configurationsettings Scheduling

Updatemanagement

Usermanagement

Recentactivities

Currentcriticalevents

The following icons are used by the Symantec LiveUpdate Administrator to assistyou in determining if all updates are scheduled for download and distribution,and to indicate when more information is available:

Displays detailed information about the item.

Displays that all products in the My Symantec Product list are covered inDistribution, Download schedules, and centers.

Displays that some of the products in the My Symantec Product list arecovered in Distribution, Download schedules, and centers.

Displays that none of the products in the My Symantec Product list arecovered by Distribution, Download schedules, and centers.

See “Understanding My Symantec Products Overview” on page 22.


Using the Symantec LiveUpdate Administrator Home pageUsing the Symantec LiveUpdate Administrator Home page you can check thestatus of LiveUpdateAdministrator download and distribution requests, view theEvent Log, and view system statistics. Using Quick Links, you can create a newdistribution center, new download center, or create a new distribution schedule.

TheMySymantec Products CoverageOverviewbox lets you know if your productsare covered in download and distribution schedules, and if they are included in adistribution center profile. Depending upon your configuration settings, productcoverage can be full, partial, or none.

Note: The inactivity time-out for the LiveUpdate Administrator is 120 minutes,after which you will need to log back on.

Viewing Download and Distribution activitiesTheDownload andDistributionRecentActivity box displays the tenmost currentrequests. This information is refreshed every 60 seconds for download activityand every 15 seconds for distribution activity. The following information isavailable:

Mode of the request, either Manual or Automatic. If the request isAutomatic (scheduled), then the name of the schedule appears.

Task

Type of the request, Download or Distribution.Type

The time the request was started.Started

The time when the status of the request was updated.Last Change

The status of the request.Status

The percentage completed.%

To view the details for a specific request, click on the ellipses button to the rightof the % column.

You can view a full list of requests by clicking the full request report link. Thiswill take you to the Download & Distribute/Activity Monitor page.

Events on the Activity Monitor page can be filtered by type, status and time. Youcan sort the events by type, when the event was started, changed, or by eventstatus.

See “Using the Activity Monitor” on page 40.

See “About Download and Distribution status” on page 41.


20

Viewing Event Log activityThe Event Log Recent Activity box displays the tenmost recent events generatedby the LiveUpdateAdministrator. This information is refreshed every 15 seconds.The following events are reported:

Events are generated by the following LiveUpdate Administratormodules: Download, Distribute, Login/Log Off, User, server, and SiteList.

Type

The user who generated the event.User

The possible values for Severity are Informational and Critical.Severity

When the event was generated.Created

You can view a full list of all events, including descriptions, by clicking the eventreport link. This will take you to the Event Log where you can filter events byevent type, users, and severity. You can also designate a specific date or a rangeof dates for the report. The Event Log can be exported to a comma separated file.Events can also be deleted by the Administrator.

See “About the Symantec LiveUpdate Administrator Event Log” on page 53.

Viewing System StatisticsSystem Statistics lets you know the amount of space that is being used by theLiveUpdate Administrator and its databases.

Indicates the amount of available disk space in MB on the localhard drive, where the Manage Updates folder and the SymantecLiveUpdate Administrator are installed.

Free Disk Space

Indicates the space in MB used by the LiveUpdate Administratordatabase.

Used by database

Indicates the space in MB used by the update database.Used by updates

Using Quick LinksQuick Links are links to where you can add a new Distribution Center, DownloadSchedule, or Distribution Schedule. You can also access these pages by clickingon theConfigure/DistributionCenters andDownload&Distribute/Schedules tabs.


Understanding My Symantec Products OverviewCoverage indicateswhether all of the products in your Site List have been assignedto distribution centers and have been associated with distribution and downloadschedules. The amount of coverage is indicated as follows:

All products and components have been assigned to distribution centersand associated with download and distribution schedules.

Some products or components have been assigned to distribution centersand associated with download and distribution schedules.

No products or components have been assigned to distribution centersand associated with download and distribution schedules.

Coverage information is provided for the following components:

■ Distribution Center Coverage indicates whether or not the products in yourSite List are included in aDistributionCenter profile. The coverage is calculatedusing only Product Distribution centers. Testing centers are not used tocalculate coverage.

■ Download Schedule Coverage indicates that the products in your Site List areassociated with defined Download schedules.

■ Distribution Schedule Coverage indicates whether or not all products in yourSite List are associatedwith a distribution schedule. The coverage is calculatedusing only Product Distribution centers. Testing centers are not used tocalculate coverage.

TheProduct CoverageDetails link takes you to theMySymantecProductswindow.To view coverage information for each product, click on the + sign to expand theproduct information.

Post-installation tasksAfter installation, you should do the following tasks:

■ Add the products for which you will be downloading updates.To add products to theMySymantec Products list, click the Configure tab, andon the My Symantec Products window, click Add New Products.See “Using My Symantec Products” on page 25.

■ Configure Source Servers (optional).By default, updates are downloaded from one of the Symantec LiveUpdateserversathttp://liveupdate.symantecliveupdate.com.However, youcan identify

Installing and using the Symantec LiveUpdate AdministratorPost-installation tasks

22

and configure one or more local servers from which clients can downloadupdates, and designate servers that can be used in case they fail.To add a new source server, click the Configure tab, click Source Servers, andthen click Add.See “Configuring Source Servers” on page 26.

■ Configure the Distribution Centers that you want to use for distributingupdates.By default, two Distribution Centers are created during installation of theLiveUpdate Administrator, a Testing Distribution Center and a ProductionDistribution Center. When updates have been tested, they can be then bemarked as "passed" and then sent to the production distribution center, usinga schedule you have determined.You can create a list of products that are associated with the distributioncenter. All locations in the distribution center will be in sync with the productupdates of products configured in the list.For example, if you would like to download only the virus definitions for allof your Symantec products, you can select the products, and then specify theVirus Definitions component.See “Working with distribution centers” on page 30.

■ Export the client settingshost file, Settings.Hosts.LiveUpdate, usedbyWindowsLiveUpdate clients to downloadupdates from theDistributionCenter, or exporta liveupdt.hst file, used by Java LiveUpdate clients.To generate a host file, on the Configure tab, click Client Settings, and thenselect the Distribution Center that you want your LiveUpdate clients to use.Click Export Window Settings to export the Settings.Host.LiveUpdate file, orclick Export Java Settings to create the Java LiveUpdate client file.You then copy the file to the \Program Files\Symantec\LiveUpdate directoryon the LiveUpdate client computers. When the LiveUpdate client runs, it willuse the host file for information on where to download updates.See “Working with host files” on page 32.

Updating the Symantec LiveUpdate AdministratorThe Symantec LiveUpdate Administrator can update itself.

To update the Symantec LiveUpdate Administrator

1 Launch the Symantec LiveUpdate Administrator.

2 In the Symantec LiveUpdate Administrator Home page, on right-hand sideof the title bar, click LiveUpdate.

3 On the Confirm Update page, click ConfirmUpdate.

23Installing and using the Symantec LiveUpdate AdministratorUpdating the Symantec LiveUpdate Administrator

Uninstalling the Symantec LiveUpdate AdministratorYou can uninstall the Symantec LiveUpdate Administrator using Add/RemovePrograms in the Control Panel

Installing and using the Symantec LiveUpdate AdministratorUninstalling the Symantec LiveUpdate Administrator

24

Configuring the SymantecLiveUpdate Administrator


■ Configuring Symantec LiveUpdate Administrator

Configuring Symantec LiveUpdate AdministratorBy using the Configure pages, you can add and manage the products for whichyou want LiveUpdate to download updates. You can also add and manage thesource servers anddistribution centers, andmodify general Symantec LiveUpdateAdministrator settings.

Updating the My Symantec Product CatalogIf your Symantec product does not appear in the list of available products, youmayneed to update the Symantec Product Catalog. Thiswill populate the listwiththe latest available products, which you can then add to your Site List.

To update the Symantec Product Catalog

◆ On the left pane in the My Symantec Products window, under My SymantecProducts Tasks, click Update Symantec Product Catalog.

Using My Symantec ProductsYou can delete and add the products that LiveUpdate downloads updates for. Youcan also view the coverage details for each product.


3Chapter

To add a product to the product list

1 On the My Symantec Products window, click AddNewProducts.

2 Under Product line, select the name of the product that youwant to add fromthe list.

3 UnderAll Products, select the version and language for the product. To selectall versions and languages, check All Products.

4 Click OK.

If your Symantec product is not listed, you will need to update the SymantecProduct Catalog.

See “Updating the My Symantec Product Catalog” on page 25.

To add more products to the product list, perform steps 1 - 4.

To delete a product from the product list

1 On theMy Symantec Products window, click the box next to the product thatyou want to delete from the product list.

2 Click Delete Selected Products.

3 Click ConfirmDelete to delete the product.

Using coverage informationYou can use the information in the Download Schedule, Distribution Schedule,and Distribution Center Coverage columns to determine whether all of yourSymantec products and components are included in distribution and downloadschedules, and are a part of a distribution center. Depending upon how you haveconfigured your product updates for downloading and distribution, coverage canbe full, some, or none.

Configuring Source ServersWhen you install the Symantec LiveUpdate Administrator, the SymantecLiveUpdate server at http://liveupdate.symantecliveupdate.com is added bydefault. You can optionally add additional source servers.

You can designate a list of failover servers that will be used in cases where theprimary server is not available. The Symantec LiveUpdate Administrator will tryto connect to these servers in the order inwhich they appear in the user interface.Whenyoudownloadupdates, theSymantecLiveUpdateAdministratorwill attemptto download from the source server. If the server is not available, the SymantecLiveUpdate Administratorwill attempt to download from the failover server. The

Configuring the Symantec LiveUpdate AdministratorConfiguring Symantec LiveUpdate Administrator

26

number of times that theSymantec LiveUpdateAdministrator attempts to connectis configurable through the Preferences option.

When you configure a server to be used by the Symantec LiveUpdateAdministrator, you will need the following information:

Enter a unique name for the server.Source server name

Enter a number from1 to 5 to denote the priority of the server. 1 is the highest.TheSymantecLiveUpdateAdministratorwill downloadupdates fromthe serverwith the highest priority if updates with the same timestamp are available onall source servers.

Priority

The URL which is used to connect to the server. The Symantec LiveUpdateAdministrator will validate this entry.

Hostname/IP address

The root directory on the serverwhere downloading anddistributingwill occur.Root directory

Used for authentication. If necessary, enter the domain name(domain\username). For example, enterprise\Firstname_Lastname.

Login id

Used for authentication.Password

Used for authentication.Confirm password

Select one of the following:

■ HTTP

■ HTTPS

■ FTP

■ UNC

Protocol

The default ports are:

■ HTTP: 80

■ HTTPS: 443

■ FTP: 21

Port information is not required for UNC.

Port (if other than default)

Check this if you use a proxy server.Use proxy

The URL that is used to connect to the server. The Symantec LiveUpdateAdministrator validates this entry.

Proxy hostname/IP address

Used for authentication. If necessary, enter the domain name(domain\username). For example, enterprise\Firstname_Lastname.

Proxy login id

Used for authentication.Proxy password

Used for authentication.Confirm proxy password

27Configuring the Symantec LiveUpdate AdministratorConfiguring Symantec LiveUpdate Administrator

Select one of the following:

■ HTTP

■ HTTPS

■ FTP

■ UNC

Proxy protocol

The default ports are:

■ HTTP: 80

■ HTTPS: 443

■ FTP: 21

Port information is not required for UNC.

Port (if other than default)

To add a Source Server

1 In the Configure tab, under Source Servers, click Add.

2 In the New Source Server window, enter the information for the server.


■ To save the new source server, click OK.

■ To save the new source server, and add a failover server for the new sourceserver, click Save andAdd Failover.

■ Click Cancel to cancel adding a new server.

To edit a Source Server

1 In the Configure tab, under Source Servers, select the server you want todelete, then click Edit.

2 When you have finished editing the information for the server, do one of thefollowing:

■ Click OK to save your changes.

■ Click Apply to save the changes and continue editing.

■ Click Test to test the server connection.

To delete a Source Server

1 In the Configure tab, under Source Servers, select the server you want todelete, then click Delete.

2 Click Cancel to cancel the deletion.

3 Click ConfirmDelete to delete the language from the site list.


28

To reset to factory defaults

1 In the Configure tab, under Source Servers, in the left pane, click Reset tofactory defaults.


■ Click Cancel to cancel resetting to the Symantec defaults.

■ Click Confirm reset to confirm resetting to the Symantec defaults.

The source and failover servers will be removed.

Working with failover serversAfailover server is usedwhena connection to the source server fails. TheSymantecLiveUpdate Administrator will then attempt to download from a failover serverthat you designate. If that connection also fails, the Symantec LiveUpdateAdministrator will retry downloading from the source server. The SymantecLiveUpdate Administrator will make three attempts by default. You can changethe number of times the Symantec LiveUpdateAdministrator attempts to connectin the Configure/Preferences/Server Connection option.

See “Configuring Symantec LiveUpdate Administrator preferences” on page 33.

To add a failover server

1 Select the source server that you want to associate with a failover server bydoing one of the following:

■ In the Configure/Source Servers window, on the left pane, click AddFailoverServer. Then, in the drop down list, select the source server thatyou want to add a failover server for.

■ In right pane, under Source Servers, click on the server that you want toadd a failover server for, and then click Add.

■ If you are in the process of adding a newSource Server, in theNewSourceServer window, click Add next to the Failover Servers box.

2 Enter the information for the server.


■ Click OK to add the failover server.

■ ClickSaveandAddAnother to continue addingadditional failover servers.

■ Click Cancel to cancel the addition of the failover server.


To change the order of a failover server

1 On the Source Servers window, click the name of the source server, and thenclick Edit.

2 Click the name of the failover server that you want to move, and then clickMoveUp orMoveDown.

To promote a failover server to primary server

1 Click Configure > Source Servers.

2 In the Source Servers list, click the name of the Source Server to which thefailover server belongs, and then click Edit.

3 On the Edit Source Server window, in the Failover Servers box, click on thefailover server that you want to promote, and then click Primary.

4 Click Confirmmakeprimary. This will promote the failover server to be theprimary Source Server. The previous primary Source Server will become anew failover server.

Working with distribution centersA Distribution Center is a single server (Central LiveUpdate Server) or a servergroup where updates are distributed together. Each Distribution Center is listedby the name of the Distribution Center and its type, either Production or Testing.Updates that need to be tested are first distributed to a testing center. Once theupdateshavepassed testing, you then release themfordistributiononaproductionserver. Updates that don't require any testing can be distributed directly to aproduction server. TheSymantec LiveUpdateAdministrator installs both adefaultproduction center and a default testing center.

You can also add your own production and testing distribution centers. You cancopy or edit the information for each distribution center and delete distributioncenters. Once you've created a distribution center, you define a list of productsfor that distribution center. The product list applies to the entire distributioncenter. You can select an entire product line, or only add specific components,such as software updates or virus definitions. Once you've created your productlist, it is displayed on the Distribution Center details page. The product list isdisplayed, along with details for the selected components.

Note: If you are setting up a remote distribution center using IIS 6 andHTTP, youmay need to enable WebDAV to accept PUT requests. Otherwise, you may see astatus message that the server is unreachable.


30

Coverage information is displayed at the product level to indicate if all componentswere selected.


You can also define multiple servers, called locations. Updates are distributed toall locations in a distribution center. Once an update has been distributed to alocation, it is not distributed again. Symantec recommends using either ISS orApache for distribution center locations. Please refer to your operating system'sdocumentation for additional information.

If you are using an UNC share location server, and the user is an account on aremote system, ensure that the user has read/write access to the named share.The login id for a UNC location server should be in the formatcomputername\username, where computername is the name of the computerwhere the UNC share resides.

Note: Symantec recommends using no more than ten locations, based uponminimum system requirements.

You can enable bandwidth throttling for each location. This lets you managedistribution in environments that have both high and low bandwidth networks.You can enable bandwidth to consume 50 to 90 percent of resources. The defaultis 80 percent. In addition to enabling bandwidth throttling for specific locations,you can enable it for all location servers under Configure > Preferences.

Once you've created a distribution center, you must generate aSettings.Hosts.LiveUpdate host file forWindows clients, or a liveupdt.hst file forJavaLiveUpdate clients. This allowsyourLiveUpdate client computers todownloadupdates from the distribution center.

See “Working with host files” on page 32.

To add a new distribution center

1 On the Configure tab, Distribution Centers window, click Add.

2 Enter the following information for the distribution center:

Enter a unique name for this distribution centerDistribution center name

Select either Production or Testing from the dropdown menu.

Distribution center type

Enter a meaningful description that will help youidentify this distribution center.

Description


3 To specify a location, in the Locations box, click Add.

A distribution center must have at least one location.

4 In the New location server window, enter the information for the server.

5 Click Save to save the new location, or Save and add another to continueadding new locations, or click Cancel to cancel adding a new location.

6 In the Edit Distribution Center window, add products to this distributioncenter by clicking Add next to the Product List box.

7 Select the products you want to add, and then click OK.

You can add all products, or expand a product and select specific components,such as Virus Definitions.

8 In the Edit Distribution Center window, click OK to save the changes andleave this window, or Apply to continuing editing the Distribution Center.

To delete a distribution center

1 On the Configure tab, Distribution Centers window, select the distributioncenter you want to delete, and then click Delete.

2 Click ConfirmDelete to finish deleting the distribution center.

To delete a location

1 On the Configure tab, Distribution Centers window, select the distributioncenterwhose Location List contains the location youwant to delete, and thenclick Edit.

2 On theEditDistributionCenterwindow, select the location youwant to delete,and then click Delete.

3 Click ConfirmDelete to finish deleting the location.

Working with host filesWhen a LiveUpdate client is installed, it is configured to use a SymantecLiveUpdate server. To direct LiveUpdate clients to retrieve updates from aDistribution server instead, youmust generate a new client settings host file andthen distribute it to each client computer on the network. When the clientcomputer runs LiveUpdate, it will connect to the server that you've designated inthe host file and download the updates from that location.

You must copy the client settings host file to the LiveUpdate installation folderon the client computer. By default, LiveUpdate is installed to C:\ProgramFiles\Symantec\LiveUpdate.


32

To generate a host file for Windows LiveUpdate clients

1 Click the Configure tab, and then click Client Settings.

2 Select the distribution center that you want to create a host file for, and thenclick ExportWindows Settings.

3 Click Save.

4 Select the location to save the file, and then click Save.

The file for Windows clients should be saved as Settings.Hosts.LiveUpdate.

Do not use a UNC location for Windows NT clients and servers. If you use ascheduling utility, LiveUpdate can't connect to a UNC location unless theLiveUpdate files reside in a shared resource on the Windows NT server thatall users are authorized to access (a NULL share).

To generate a host file for Java LiveUpdate clients

1 Click the Configure tab, and then click Client Settings.

2 Select the distribution center that you want to create a host file for, and thenclick Export Java Settings.

3 Click Save.

4 Select the location to save the file, and then click Save.

The file for Java LiveUpdate clients should be saved as liveupdt.hst.

Configuring Symantec LiveUpdate Administrator preferencesYou can configure the Symantec LiveUpdate Administrator display andenvironment settings, set logging modes, and event thresholds.

You can also set schedules and rules for purging older updates, both in theManageUpdates folder and in Distribution Centers. When you download updates fromSymantec, they are copied to the Manage Updates location that you specifiedduring installation. By default, the location is C:\Documents And Settings\AllUsers\Application Data\Symantec\LiveUpdate Administrator\Downloads.LiveUpdate distributes updates to your Distribution Centers, where they remainuntil you remove them.You canpurge old updates fromyourDistributionCentersto free disk space. By default, updates inDistribution Centerswill be purged daily.However, you can change this setting to never purge updates automatically, orto purge themmonthly or weekly.

All updates in theManage Updates folder, except for the latest five revisions, areset to be purgedweekly by default. However, you can specify rules for theManageUpdates folder purge to determine which updates to delete, based upon the ageof the revision or when the updates were initially downloaded. For example, you


can purge updates older than 10 revisions back, or purge updates that weredownloaded more than 10 days back.

Note: A purge will not delete the latest revision even if it satisfies the purge rule.For example, a revision may be more than 10 days old, but it will not be deletedif it is the latest revision.

You can enable bandwidth throttling for all locations. Bandwidth throttling letsyou manage the amount of network resources that are used during distribution.You can also enable bandwidth throttling for specific locations.

See “Working with distribution centers” on page 30.

By default, HTTP Delete is disabled in Web servers and you will need to enablethe HTTP Delete operation. The default Distribution Centers that ship with theLiveUpdate Administrator already have theDelete operation enabled. If you havecreatednewDistributionCenters, thenyouwill need to add theDelete functionalityby implementing doDelete in the servlet.

For IIS servers, the IUSR_<computer> Windows account must have Modifypermission on the Central LiveUpdate (CLU) Web Application folder. If you haveconfigured otherWindows accounts for the CLUWebApplication, theymust alsohave Modify permission on the folder for HTTP DELETE to work.

You can specify the number of times that the Symantec LiveUpdateAdministratorattempts a server connection.Whenyou initiate adownloadordistribution request,the Symantec LiveUpdate Administrator attempts to connect to the server thatyouhave designated. If the Symantec LiveUpdateAdministrator cannot establisha connection to the server, then it assume the server is not available. You canspecify a timeout period of 10 to 60 seconds. The default is 30.

The number of times that the Symantec LiveUpdate Administrator attempts aconnection is determined by the value in theRetry field. By default, it will attemptto connect 3 times, however you can set the Retry counter from 2 to 5 times.

You can also set the amount of time that the Symantec LiveUpdateAdministratorwaits between connection attempts. Using the Interval setting, you can set theSymantec LiveUpdate Administrator to wait from 5 to 60 seconds betweenattempts. The default is 15 seconds.

The Email Server is used by Symantec LiveUpdate Administrator passwordrecovery. You can specify the SMTP server that the Symantec LiveUpdateAdministrator should connect towhen sending email to users. This server handlesall outgoing emails. TheFromAddress is usedwhensendingemail about temporarypasswords.


34

To configure Symantec LiveUpdate Administrator settings

1 Click the Configure tab, and then click Preferences.

2 Click Update to save your changes.

To restore the settings to the defaults, click Reset ToDefaults.

Maximum rows per page.

The number of rows that are displayed. The default is 25.

Display

Temporary Directory

This is the location where the Symantec LiveUpdate Administrator copies updatesprior to distribution. The default location is C:\TempDownload.

Environment Variables

How often

Select how often you want to purge older updates. The options are:Never/Daily/Weekly/Monthly. The default is Weekly, with the purge set to run onSunday at 12 AM.

Purge updates in ManageUpdates folder

Rule

Older than xx reversions back (1-10). The default is 5.

Retrieved more than xx days back (1-31). The default is 10.

How often

Select how often you want to purge older updates. The options are:Never/Daily/Weekly/Monthly. The default is Daily, with the purge set to run at 12:30AM.

Purgeupdates inDistributionCenters

Enable bandwidth throttling

Bandwidth throttling is disabled by default. To apply bandwidth throttling to alllocations, click Apply to all location servers.

Bandwidth throttling consumption

When enabled, the default is 80%. You can set bandwidth throttling from 50 to 90percent.

Bandwidth Throttling

Minimum password length

The default length is 8 characters.

Login Security

Debug Mode

Off by default. Turn this on only if instructed to by Technical Support.

Logging

Event threshold

INFORMATIONAL (default) or CRITICAL.


Timeout: The default is 30 seconds.

Retry: The default is 3 times.

Retry Interval (seconds): The default is 5.

Server Connection

SMTP Server Name: The default is SMTP Server

From Address: The default is [email protected]

Email Server

To restore default configuration settings

1 Click Configure > Settings.

2 On the Configure Application Settings window, click Reset ToDefaults.

3 Click Confirm.


36

Managing download anddistribution schedules


■ Scheduling downloads

■ Scheduling distribution

■ Using the Activity Monitor

■ About Download and Distribution status

Scheduling downloadsYou can configure the Symantec LiveUpdate Administrator to download updatesautomatically. You specify how often you want to run LiveUpdate and for whichproducts you want to download updates for. You can also run manual downloadanddistribution requests, and view theActivityMonitor, which lists the SymantecLiveUpdate Administrator download and distribution requests.

You can select to download updates for all products and components, or you canfine tune downloads so that only virus definitions, or software updates, or othercomponents, will be downloaded. For example, if you are running Symantec ClientSecurity, you may wish to set up a schedule that will download virus definitionsdaily, and another schedule that will check for software updates on a weekly ormonthly basis.

4Chapter

To create a new download schedule

1 On the Download & Distribute tab, in the Schedules window, click AddDownload.

2 In the Add Download Schedule box, enter the following:

A descriptive name for this schedule.Distribution schedule name

Enabled or DisabledStatus

Enter a description for this schedule.Description

3 In the Select Products box, click Add.

4 Select the products and components that you want to add to this schedule.To expand the product list, click on the plus sign (+), and then select specificcomponents. Or, check All Products to add all products and components tothe download schedule.

5 Click Add.

6 Select the test status that you want to assign to the schedule.

By default, the test status is set to Skip Test. Set the status to Must Test totest the updates before you distribute them.

7 In the Select Schedule box, set the download schedule.

8 Click OK to save the schedule, or click Cancel to cancel this action.

Note: If you select a product and language, and download updates for that product,and then select another language to downloadupdates for, youmay see amessagethat no new updates are available for that language for download/distribution.However, contentwill be downloaded for that language the next time that updatesare available.

To run a manual download request that is based on an existing schedule

◆ In the right pane, under Schedules, select an existing Download Schedule,and then click RunNow.

To run a new manual download request

1 In the left pane, under Scheduling Tasks, clickManual DownloadRequest.

2 In the Manual Download Request - Step 1 of 2 window, select the productsyou want to add to this request by clicking Add.

Managing download and distribution schedulesScheduling downloads

38

3 In the Select products to be addedwindow, select the product or componentsyou want to add and then click OK.

4 Select the test status for this download request: SkipTest orMustTest. Thedefault is Skip Test.

5 Click Next.

6 In the Manual Download Request - Step 2 of 2 window, select the updatesthat you want to download. You can select all products and components, oryou can select specific components such as Software Updates or VirusDefinitions.

7 Click Next to start the download request.

To delete a download schedule

1 On theDownload&Distribute/Schedules list, click theboxnext to the schedulethat you want to delete.

2 Click Delete.

3 ClickConfirmDelete to finish deleting the schedule or clickCancel to cancelthe deletion.

Scheduling distributionAfter you've downloaded your updates, they can be sent to either a testingdistribution server, or to a production distribution server where they can bedownloaded by your LiveUpdate clients.

Whenyouaddadistribution schedule, youalso select theproducts andcomponentsthat youwant to associatewith the schedule. This list of products and componentsis compared with the updates in the Manage Updates folder. Any revisions thatare not already distributed will then be distributed in the current session.

To add a new distribution schedule

1 On the Download & Distribute tab, in the Schedules window, click AddDistribution.

2 In the Add Distribution Schedule box, enter the following:

■ Distribution Schedule name

■ Status, either Enabled or Disabled

■ Description

3 Click Add to select the products and components for which updates will bedistributed.

39Managing download and distribution schedulesScheduling distribution

4 Select the products and components that you want to add to this schedule.To expand the product list, click on the plus sign (+), and then select specificcomponents. Or, check All Products to add all products and components tothe distribution schedule.

5 Click Add.

6 In the Distribute Content To box, select the distribution center type, Testing,Production, or both. Then, select the Distribution Centers. You can select allDistribution Centers, or a subset of the centers.

7 Select a distribution schedule.

8 Click OK to save the schedule or click Cancel to cancel this action.

To run a manual distribution request based on an existing schedule

◆ In the right pane, under Schedules, select an existing Distribution Schedule,and then click RunNow.

To run a new manual distribution request

1 In the left pane, under SchedulingTasks, clickManualDistributionRequest.

2 In the Manual Distribution Request Step 1 of 2 window, click Add to selectthe products that you want to distribution with this request.

3 In the Select products to be added window, select the products or thecomponents, then click OK.

4 In theManualDistributionRequest Step 1 of 2window, select theDistributionCenter Type: All, All Production Centers, or All Testing Centers.

5 Select the Distribution Center: All, or Subset.

6 Click Next.

7 In the Manual Distribution Request Step 2 of 2 window, select the updatesthat you want to distribute, and then click Next.

Using the Activity MonitorYou can view the details of all download and distribution requests in the ActivityMonitor.

For each request, the following information is available:

The description of the request. If it is a scheduled request, the nameof the request is displayed. Otherwise, the descriptionwill beManual.

Task

The type of the request, either Distribution or Download.Type

Managing download and distribution schedulesUsing the Activity Monitor

40

The date and time when the request was started.Started

The date and time that the request was last changed.Last Change

The status of the update.Status

Percentage of completion%

You can filter activities by using the Show Filters icon to the right of the Activitybox. Activities can be filtered by Type, Status, and by Time, either by the StartTime or by the when the last change occurred.

Viewing request detailsYou can view details for specific requests. Request details include informationabout the status of the request, whether or not the update needs to be tested, thetotal size of the update, the time the request was started, and the product andcomponent for which the update was downloaded. The name of the update file isalso displayed.

To view request details

◆ Click on the ellipses button that appears to the right of the% column for therequest you want to view.

About Download and Distribution statusYou can find out the status of your download and distribution requests in theActivity Monitor and by viewing the details of the request. The status that isdisplayed can help you determine if your request was successful, or help you totroubleshoot a problem.

The following types of status are displayed:

■ Download request status

■ Distribution request status

■ Download update status

■ Distribution update status

The following describes the possible status of download requests:

DescriptionStatus

The download request has been created.CREATED

41Managing download and distribution schedulesAbout Download and Distribution status

DescriptionStatus

The download request is complete.COMPLETE

The download request has failed.FAILURE

The download request is in the process of being cancelled.CANCELLING

The download request is cancelled.CANCELLED

Download from source server is started.RETRIEVING

The download request to the temporary directory iscomplete. Updates are beingmoved to theManageUpdatesfolder and the database is being updated.

COMMITTING

The following describes the possible status of distribution requests:

DescriptionStatus

The distribution request has been created.CREATED

The distribution request is complete.COMPLETE

The distribution request has failed.FAILURE

The distribution request is cancelled.CANCELLED

The following describes the possible status of download update requests:

DescriptionStatus

The request is successful, but an update for one of theproducts listed in the product catalog was not found on thesource server.

The product catalog contains the list of updates applicablefor a given product.

NOT_FOUND

There are three reasons for this status:

■ Updates were previously downloaded and will not bedownloaded again.

■ After beingdownloaded, anupdatewasdeleted fromthetemporary directory.

■ The size of the update differs from the size listed in thecatalog.

SKIPPED

The product catalog and updates have already beendownloaded and will not be downloaded again.

EXIST

Managing download and distribution schedulesAbout Download and Distribution status

42

DescriptionStatus

The download is in progress.IN_PROGRESS

The download is complete.DOWNLOADED

The downloaded content has been moved to the ManageUpdates folder.

COMPLETE

The download has failed.FAILED

The downloaded update or one if its associated files hasfailed validation.

CORRUPT

The update is about to be downloaded.CREATED

The following describes the possible status of distribution update requests:

DescriptionStatus

The update was not found in the Manage Updates folder.FILENOTFOUND

The update could not be copied to the temporary directory.COPYFAIL

The upload failed or there was no space available.TRANSFERFAIL

The upload is pending and not yet started.CREATED

Generic failure.FAILED

The file is being skipped because it is a part of anotherupdate request and will be uploaded at that time.

SKIPPED

The file has already been uploaded during a previousdistribution request.

ALREADY_PRESENT

_ON_SERVER

The file is not available in the temporary directory.TEMP_FILE_

NOT_FOUND

The update or its associated catalog file has failed.CORRUPT

43Managing download and distribution schedulesAbout Download and Distribution status

Managing download and distribution schedulesAbout Download and Distribution status

44

Managing updates


■ Managing updates for Symantec products

■ Testing updates

Managing updates for Symantec productsManage Updates is where you can manage all of the Symantec updates for theproducts you have selected inMy Symantec Products. You can view, approve, anddelete updates.

If you haven't added any products toMy Symantec Products, youwill see an errormessage, and you are prompted to create a list of your Symantec products.

See “Using My Symantec Products” on page 25.

The default location for the product updates is C:\Documents and Settings\AllUsers\Application Data\Symantec\LiveUpdate Administrator\Downloads. Thelocation cannot be changed after you've installed the Symantec LiveUpdateAdministrator.

You can view the contents of the download folder using either the list view or thedetails view. The list view displays all of the current downloaded updates anddefinitions for all products. Updates from older revisions are not displayed.However, you can use the detail view to view older updates.

Updates are listed by Product/Component name, Test Status, Criticality andDistribution Coverage. You can filter the view by product name, test status (state),and within a range of dates.

You can filter or search for updates by Update Name, Criticality, Type, or FileName. You can also show only updates for a specific product, or for updates basedon criticality or by the date that the update was downloaded.

5Chapter

Criticality is used to designate the urgency of the update. Product/Component isthe name and component name for which updates will be downloaded.

The possible criticality values are as follows:

Reserved for the most critical updates such as vulnerabilities orCategory 5 outbreak content.

Critical

All product updates that represent patches to address defects andsecurity updates.

Recommended

New features and product enhancements.Optional

When you expand the Product / Component list, you can view the followinginformation for each product update:

The actual server-side nameof the update package that is retrieved.It is always a ZIP file, although the .zip extension is not always used.

File Name

This indicates the test status of the update. The following states arepossible:

■ Corrupt

■ Failed

■ Faulty

■ Not required

■ Passed

■ Pending

■ Retest

■ Unknown

■ Untested

Test Status

This indicates if the current revision is distributed to all DistributionCenters. Three values are possible:

■ Revision is distributed to all Distribution Centers

■ Revision is distributed to some of the Distribution Centers

■ Revision is not distributed to any of the Distribution Centers.

DistributionCoverage


Details about a specific update component can be viewedby clicking on the ellipsesbutton that appears to the right of the Distribution Coverage column.

Managing updatesManaging updates for Symantec products

46

Viewing update detailsThe Update Details window displays the revision details and the distributionstatus for specific product component.

The following information is displayed in the Revision Details box:

The name of the component.Name

Possible values are Critical, Recommended, and Optional.Criticality

Type refers to the data type of the update. For example, Content orFixtool.

Type

The name of the update package that is retrieved.File Name

Indicates the size of the compressed file on the server in bytes. Thisnumber is translated into KB and is displayed on the LiveUpdatewizard to indicate to the user the size of the selected LiveUpdatepackage.

Size

Indicates whether a reboot is required after installing the update.Reboot Required

Type refers to the data type of the update. Possible values are as follows:

SecurityResponseupdates forvirusdefinitions, IntrusionPreventionand Detection signatures, spam definitions, crimeware definitionsand so on.

Content

Product updates that contain fixes for defects.Patch

Product updates for configuration files.Setting

Product updates that are for messaging onlyInformation

Product updates for Help content.Help

Manuals andotherdocumentationgenerallydelivered inPDF format.Documentation

Helpful hints.Tip

Stand-alone fix tools to address product errors not addressedthrough product updates or patches.

Fixtool

The Distribution Status box displays the following information:

The name of the Distribution Center.Distribution Center

The distribution center type, either Production or Testing.Center Type

47Managing updatesManaging updates for Symantec products

The update revision that was distributed to the distribution center.If a revision has been locked, then a padlock appears to the left ofthe date.

DistributionRevision

If a revision has been locked to the distribution center, then theUnlock button appears. If the revision has not been locked, then theLock To button appears.

Locked/Unlock To

If a locked revision is not the most current, then a warning willappear.

Locked warning

Deleting revisionsYou can delete the revision from theManage Updates folder. All updates and TRIfiles are deleted. If you delete the current revision, any older revisions still in thefolder will become the current revision and will be downloaded during the nextdownload event. Locked revisions cannot be deleted.

To delete an update revision

1 In the Manage Update window, expand the Product / Component list.

2 Select the revision you want to delete.

3 Click Delete.

Locking and unlocking revisionsYou can lock anupdate revision to a specific distribution center.When the revisionis locked, new revisions will be downloaded, but they will not be available to thatdistribution center. A padlock will appear next to the distributed revision in theDistribution Status list.

To lock a revision

1 In the Manage Updates window, expand the Product/Component list.

2 Click the ellipses button to the right of the Distribution Coverage column forthe update you want to lock.

3 In the Update Details window, in the Distribution Status box, select theDistribution Center you want to lock, and then click Lock To.

4 In the Manage Updates - Add Lock window, select the revision you want tolock, and then click OK.

5 In the Manage Updates - Confirm Add Lock window, click OK.

To unlock a revision

◆ In the Manage Update details window, click Unlock.

Managing updatesManaging updates for Symantec products

48

Testing updatesWhen you create a download schedule or run a manual download request, youmust set the testing status of the updates that you download. Updates can bemarked as either Skip Test or Must Test. Updates that do not have to be testedcan be sent directly to a production distribution center and are available forimmediate downloading.

Each downloaded update has an associated testing state. The testing state letsyou know whether the update has been tested and what stage the update is in.There are six possible testing states:

The update has not been tested, butmust be tested before it canbe distributed to a production distribution center. This contenthas not yet been placed to a testing distribution server.

Untested

The update has been successfully tested and is ready to be sentto a production distribution center.

Passed

The update has failed testing. This update cannot be distributedto a production distribution center.

Failed

The update does not require testing prior to being distributedto a production distribution center.

Test Not Required

The update initially passed testing, and was distributed to aproduction distribution center, but was later found to haveproblems.

Faulty

Theupdate that has been found to be faulty, or has failed testing,and you would like to retest it.

Retest

You can view the test status of downloaded updates in Manage Updates. Updatesthat have beenmarkedUntested can be sent to a testing distribution center, wherethey can then be distributed for further testing. After you've completed testingthe updates, you can thenmark themasPassed or Failed. Passedupdates can thenbe sent to production distribution centers. Failed updated can be resent to thetesting distribution center for further testing and the status changed to Retest.

Updates that you distribute to production distribution centers are either markedas Skip Test or Passed. If you find any issues with the updates after they've beendistributed to a production center, you can mark them as Faulty and send themback to a testing center for further testing (the status is changed to Retest).

Only updates that are marked as Passed or Skip Test can be sent to a productiondistributioncenter. TheSymantecLiveUpdateAdministratorwill not allowupdatesmarked Test Failed or Faulty to be sent to any production distribution center.

49Managing updatesTesting updates

Updates that are marked Untested will not be automatically sent to a productiondistribution center, but you can send them to a testing distribution center.

Note:Someupdate components are shared betweenproducts. If youhave specifiedthat updates for a particular product must be tested, any shared componentupdateswill automatically be set toMust Test, andwill display a status ofUntestedwhen they are downloaded.

Figure 5-1 shows a testing flow with the possible outcomes.

Figure 5-1 Symantec LiveUpdate Administrator testing flow

If you set the status of an update to Must Test, but have not yet tested it, theLiveUpdateAdministrator sets the testing state toUntested. Otherwise, the statusis set to Testing Not Required.

If the update state isUntested, the LiveUpdateAdministratorwill send the updateto the appropriate testing distribution center. This can happen automatically,based upon a schedule that you determine, or you can distribute the update fortesting manually.

Once you have completed testing the update, you set the status to Test Passed orTest Failed. Updates marked as Test Passed will then be available to productiondistribution centers.

If the update has failed, you can retest the update, delete the update, or simplyleave it in the Manage Updates folder.

Managing updatesTesting updates

50

If you have distributed an update to a production distribution center, and laterdetermine that it is problematic, you can mark the update Test Faulty. This willprevent future operations fromdistributing the update to production distributioncenters.

51Managing updatesTesting updates

Managing updatesTesting updates

52

Viewing events andmanaging users


■ About the Symantec LiveUpdate Administrator Event Log

■ About user management

About theSymantec LiveUpdateAdministrator EventLog

The Symantec LiveUpdate Administrator Event Log lets you view informationabout events generated by the Symantec LiveUpdateAdministrator. You can filterevents by event type, users, and severity. You can also designate a specific dateor a range of dates for the report and export the report to a comma separated file.Events can also be deleted from the log.

The following information is available in the Event Log:

The date and time when the event was generated.Created

The module that generated the event. The possible values are:Download, Schedule, Distribute, Log on/Log off, Server, andCatalog/Site List.

Event Type

The severity of the event.Severity

The user who generated the event.

For purge events, the LiveUpdate Administrator uses LUA Startup toinitiate the process. This name will appear in the list of users.

User

6Chapter

The description of the event.Description

You can change how events are logged.

See “Configuring Symantec LiveUpdate Administrator preferences” on page 33.

About user managementThe Symantec LiveUpdate Administrator Manage Users page is where you addand modify Symantec LiveUpdate Administrator users. You can log off any userthat is currently logged onto the system. You can also send an email to SymantecLiveUpdate Administrator users, and view user details.

The Manage Users window displays the following information:

The login name of the user.User

Required.First Name

Required.Last Name

A user can be an Administrator or a User.Role(s)

Displays the login status of the user.Status

To send an email to a user, click the envelope icon to the right of the Status column.To view and edit the details for a user, click the ellipses icon to the right of theenvelope icon.

RolesThe are two user roles in the Symantec LiveUpdateAdministrator, Administratorand User. The Administrator role has complete access to the system. The Userrole restricts users to the following activities:

■ Manual download

■ Manual distribution

■ Change status of updates in Manage Updates

■ Change profile

For the rest of the modules, Users have Read Only access.

Adding usersTo add a new user, you will need the following information:

Viewing events and managing usersAbout user management

54

Must be at least four characters long.User name

Must be at least eight characters long.Password

RequiredFirst name

RequiredLast name

RequiredEmail address

Administrator or User.Role

To add a user

1 On the Manage Users window, click Add.

2 Enter the information for the new user.

3 Click OK to save the new user, or ClearAll to clear the form.

To delete a user

◆ Check the box next to the user's name, and then click Delete.

To force a user to log off

◆ Check the box next to the user's name, and then click Force LogOff.

55Viewing events and managing usersAbout user management

Viewing events and managing usersAbout user management

56

AActivity Monitor

request details 40viewing 40

Bbandwidth throttling 10

enabling 31enabling for all locations 33

Ccatalog 42Configuration settings 33coverage 22

about 26criticality values 45

Ddata types 47Distribution

running a manual request 40scheduling 39

Distribution Centersadding 30purging updates in 33

Downloaddeleting schedule for 39running a manual request 38scheduling 37

EEmail Server 33environment variables

setting 33Event Log

about 53and Recent Activity 21

Ffailover servers

configuring 29promoting 29

HHTTP Delete 34

IIUSR account permission 34

LLiveUpdate Administrator

configuring 25home page 20installing 16Quick Links 21requesting a temporary password for 17system requirements 13

LiveUpdate client host file. See client settingsliveupdt.hst 32locations 31

and UNC share servers 31LUA Startup

in Event Log user list 53

MManage Updates

using 45viewing details of 47

Manage Updates folderpurging 33

My Symantec Productsabout 25adding 25coverage overview 22deleting 25tasks 25

Index

Pproduct catalog 42purging

rules for 33updates 33

RRecent Activity

viewing 20reports 53revisions

deleting fromManage Updates 48locking and unlocking 48

SSettings.Hosts.LiveUpdate 32Source servers

configuring 26default 26failover servers 26resetting to factory defaults 29

statusdistribution 41download 41

Symantec Product Catalogupdating 25

System Statistics 21

Ttesting

states 49updates 49

Uupdates

default download location 45users

forcing log off 54managing 54roles of 54

Index58

liveupdate administrator users guide

Documents

usersapplication

programdatasymantecliveupdate

symantec liveupdate

symantec liveupdate

symantec liveupdate

liveupdate

low bandwidth

java liveupdate