A Symantec product was configured to receive its updates from an internal LiveUpdate server that is no longer in use. Though this server no longer exists on the network, the Symantec product continues to look for updates from it and thus never receives new content. Attempts to manually edit the settings.liveupdate file have proven unsuccessful. How can this be corrected?
On a Windows computer, settings.liveupdate file contains only host entries on the internal network:
The Windows's computer's log.liveupdate shows repeated attempts to access only this decommissioned internal server, never the Internet LiveUpdate servers.
09.03.2011, 11:39:33 GMT -> EVENT - SERVER SELECTION FAILED EVENT - LiveUpdate failed to connect to server \\OLDLUAUSERVER at path \\OLDLUAUSERVER\LU via a LAN connection. The server connection attempt failed with a return code of 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
09.03.2011, 11:39:33 GMT -> EVENT - SESSION END FAILED EVENT - The LiveUpdate session ran in Express Mode. LiveUpdate found 0 updates available, of which 0 were installed and 0 failed to install. The LiveUpdate session exited with a return code of 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
Similar entries are seen in the corresponding files of a computer that uses Java LiveUpdate.
The management component of many Symantec products can configure their clients to use a different LiveUpdate server. For example, the LiveUpdate Policy settings configured in the Symantec Endpoint Protection Manager (SEPM) can direct the managed SEP clients to retrieve updates from the SEPM, the Internet LiveUpdate servers, or an internal location.
If it is not possible to change the configuration from the manager (for instance, in the case of an unmanaged SEP client) then administrators may re-configure individual computers to use Internet LiveUpdate source servers by downloading the attached Settings.Hosts.LiveUpdate file (for Windows LiveUpdate) or liveupdt.hst (for products that use Java LiveUpdate) and placing it in a particular directory. The default Internet-only settings contained in the file will automatically be integrated into the computer's LiveUpdate settings the next time LiveUpdate is run.
For products that use Windows LiveUpdate (Symantec AntiVirus, Symantec Endpoint Protection 11, Symantec Mail Security for Microsoft Exchange, etc)
Save the attached Settings.Hosts.LiveUpdate into the directory where the computer's settings.liveupdate file is located. Depending on the version of Windows used: this will either be
- C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate
- C:\Documents and Settings\All Users\Symantec\LiveUpdate
For Products that Use Java LiveUpdate (SAV for Linux, Symantec Mail Security for Domino Multi-Platform Edition, etc)
The liveupdt.hst file should be saved into the client's working directory, which by default should be /tmp.
The next time LiveUpdate runs, the new Internet-only configuration in the attached file will be processed and all LiveUpdate attempts will be made from Internet sources. (On computers that use Windows LiveUpdate, LiveUpdate may be manually run by typing luall.exe from Start, Run.)
Imported Document Id
Settings.Hosts.LiveUpdate file which will automatically be processed and configure all Symantec products on a Windows computer to use Internet LiveUpdate servers
Settings.Hosts.LiveUpdate (1007.0 B)
Liveupdt.hst file which will automatically be processed and configure all Symantec products that use Java LiveUpdate to use Internet LiveUpdate servers
liveupdt.hst (784.0 B)