Can a centralized LiveUpdate Server be setup for Backup Exec to retrieve updates?

Article:TECH49553  |  Created: 2006-01-06  |  Updated: 2012-01-23  |  Article URL
Article Type
Technical Solution



Can a centralized internal LiveUpdate server be set up for Backup Exec to retrieve updates?


Backup Exec servers can be configured to pull updates from one centralized LiveUpdate server. For most releases of BE, either the legacy LiveUpdate Administration Utility 1.x (LUAU 1.x, sometimes referred to Luadmin) can be used, or the current LiveUpdate Administrator 2.x (LUA 2.x) server.  

LiveUpdate Administration Utility 1.x (LUAU 1.x)

The steps below provide information on how to configure the Backup Exec media server using LUAU 1.x:

Liveupdt.hst is the host file that controls the LiveUpdate operation on client computers. When a LiveUpdate client is installed, it is configured to use a Symantec LiveUpdate server. To direct LiveUpdate clients to retrieve updates from a Central LiveUpdate server instead, a new host file must be created using LuAdmin, and then distributed to each client computer on the network.

1.  A LiveUpdate Administration server will need to be setup somewhere in the environment by using the LiveUpdate Administration Utility. Please see the following link for more information:

2.  Start LuAdmin.

3.  In the LiveUpdate Administration Utility window, in the left pane, click Host File Editor.

4.  On the File menu, click Open.

5.  In the current directory, double-click SAMPLE.HST.
The 32-bit radio button is selected by default. LAN-based hosts are not available to 16-bit clients.

6.  Under Description, do the following:
     a.  Under Name, type the name to display when users connect to the internal server.
     b.  Under Country/Area, type the country in which the server is located.

7.  Under Login, do the following:
     a.  Under Name, type the user name that has access rights to the server. If this field is left blank, LiveUpdate attempts to connect using the user name logged on to the system.
     b.  Under Password, type the password that corresponds to the user name. If this field is left blank, LiveUpdate uses the password for the user who is logged on to the system.

8.  Under Connection, do the following:
     a.  Under Type, click LAN.
     b.  Under Directory, type the UNC path or DOS drive with the full path to the server directory that contains the LiveUpdate package. Modem support has been removed from LiveUpdate, although the option for it remains on the user interface. Do not use a UNC location for Windows NT clients and servers. If you use a scheduling utility, LiveUpdate cannot connect to a UNC location unless the LiveUpdate files reside in a shared resource on the Windows NT server that all users are authorized to access (a NULL share). To use the download and security enhancements in LiveUpdate 1.6x and 1.7x, use LiveUpdate Administration Utility version or later. Download the latest version of LuAdmin (luau.exe) and supporting documentation from the Symantec Web site at the following URL:

9.  On the File menu, click Save As.

10.  Save the customized file as Liveupdt.hst.

11.  After creating the host file, copy it to the LiveUpdate directories on the client computers. The default LiveUpdate directory is \Program Files\Symantec\LiveUpdate.


LiveUpdate Administrator 2.x (LUA 2.x)

For environments with LiveUpdate Administrator 2.x (LUA 2.x), please follow the instructions in Exporting Client Settings for Windows and Java LiveUpdate Clients from the LiveUpdate Administrator 2.x  to import a hosts file that will redirect the LiveUpdate client on the Backup Exec server to the internal source.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices