How to change the embedded Symantec Scan Engine to update from an internal server
search cancel

How to change the embedded Symantec Scan Engine to update from an internal server

book

Article ID: 177245

calendar_today

Updated On:

Products

Protection Engine for Cloud Services Scan Engine AntiVirus for Caching AntiVirus for Messaging Protection Engine for NAS

Issue/Introduction



Symptoms
With IM Manager 8.1, Symantec has embedded the Symantec Scan Engine for use during file transfers. It may be necessary to change the server that the Symantec Scan Engine obtains updates from.

 

Resolution

The liveupdate.conf file contains the parameters for JavaLiveUpdate (JLU) to retrieve patches and virus definitions from Symantec.

By default, JLU is configured to use HTTP connections to retrieve the files from liveupdate.symantecliveupdate.com .

There are two ways to configure the liveupdate.conf file to retrieve definitions from an Internal LiveUpdate Admin server:

  1. Specify an internal FTP server.
  2. Use an existing liveupdt.hst file to specify an internal LiveUpdate HTTP server.



To specify an Internal LiveUpdate FTP server:

  1. Replace the entire contents of the C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\liveupdate.conf file with the following :

    protocol=ftp
    host=myserver.mydomain.com
    packagedir=/myLUADMINdirectory/mydefs
    login=myusername
    password=mypassword
    workdir=/tmp
    logfile=/tmp/liveupdt.log
  2. Modify the host= entry to point to your internal FTP server.
  3. Modify the packagedir= to point to the file location on your internal FTP server.
  4. Change the login= and password= settings to the login and password for your internal FTP server.

    The full content of a default liveupdate.conf file is included below if required to overwrite changes.

      ############################################################
      # #
      # livepdate.conf - Symantec LiveUpdate configuration file #
      # #
      # This file is used to configure the settings used by #
      # LiveUpdate #
      # #
      ############################################################

      hosts/0/url=http://liveupdate.symantecliveupdate.com:80
      hosts/1/url=http://liveupdate.symantec.com:80
      hosts/2/login:ENC=b3effdd10d982d2c7339c9604c67c34c
      hosts/2/password:ENC=18d2e2d4c1445548f8a5ef124ed20bfd
      hosts/2/url=ftp://update.symantec.com/opt/content/onramp
      logfile=C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\liveupdt.log
      maxPackageContentSize=734003200
      maxPackageSize=734003200
      maxTriFileSize=10485760
      maxZipFileSize=614400
      workdir=C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\Downloads



Use an existing liveupdt.hst file to specify an Internal LiveUpdate HTTP server :

  1. Use FTP in ASCII mode to transfer the existing liveupdt.hst file to the /<Symantec base directory>/LiveUpdate directory. This replaces the existing liveupdt.hst file.
  2. Replace the entire contents of the /etc/liveupdate.conf file with the following:

    hostfile=/<Symantec base directory>/LiveUpdate/liveupdt.hst
    workdir=/tmp
    logfile=/tmp/LiveUpdate.log
  3. Change the hostfile= setting to point to the .hst file on the server. Use the full path.


For information on configuring LUAdmin, read the document How to configure the LiveUpdate Administration Utility .