Configuring Symantec Mail Security for Domino to Update from an internal LiveUpdate Administrator 2.x Server

book

Article ID: 157662

calendar_today

Updated On:

Products

Mail Security for Domino

Issue/Introduction

The Symantec Mail Security for Domino server has no access to Internet LiveUpdate source servers.  How to configure this Symantec Mail Security for Domino server to update from an internal source?

 

Resolution

Introduction

It is possible for Symantec Mail Security for Domino and Symantec Mail Security for Domino Multi-platform Edition to retrieve Client Updates and Content Updates from an internal location within the corporate environment using LiveUpdate Administrator 2.x (LUA 2.x).  It is also possible to update using the legacy LiveUpdate Administration Utility 1.x (LUAU 1.x) if this tool is still in use.

Note that realtime Brightmail Antispam updates (sometimes called "Premium AntiSpam" or PAS updates) cannot be supplied by LUA 2.x or LUAU 1.x.

See Installing and Configuring LiveUpdate Administrator (LUA) for details on how to establish an LUA 2.x server in the environment, if one does not already exist.  Be sure that the latest available release of LUA 2.x is in use.

 

Configuring LiveUpdate Administrator 2.x

Once LUA is installed, access its GUI and add the exact version of Symantec Mail Security for Domino that is in use.  Different content is available for Symantec Mail Security for Domino 8.0 and Symantec Mail Security for Domino 8.1.  LUA will not be able to downlaod the updates necessary for your Symantec Mail Security for Domino if the incorrect version is selected.

Associate the Symantec Mail Security for Domino product with the internal Distribution Center (DC) from which it will retrieve its updates.

Configure a download and distribution schedule for the product within LUA 2.x.  Admins may choose to download both Content Update and Client Updates, or just a portion of the available new content.  Once configured and a scheule set, new content will be downloaded automatically by LUA 2.x and distributed to the desired internal location. 

Below is an illustration of how Symantec Mail Security for Domino Multi-platform Edition 3.2 appears in the LUA GUI, when correctly associated with a DC, and all client and content updates are scheduled for downlaod and distribution.

 
 
Configuring SMSDOM

Symantec Mail Security for Domino uses Java LiveUpdate (JLU) to retrieve and apply new definitions and other updates.  JLU can be configured to retrieve materials from the Distribution Center either through manual configuration or through the use of a liveupdt.hst file. 

Manually Configuring the liveupdate.conf file

Java LiveUpdate operation is controlled by settings in the /etc/liveupdate.conf file. By default, an HTTP connection is made to the Symantec server. You can change the settings to point to an internal LiveUpdate server using either an FTP or HTTP protocol connection.

To configure an internal LiveUpdate server to use a FTP protocol connection

1 For safety, make a backup copy of the following file:

/etc/liveupdate.conf

2 Make the following changes to the liveupdate.conf file:

  • Change the protocol= line to protocol= ftp for an FTP connection.
  • Change the host= line from liveupdate.symantec.com to your internal LiveUpdate Administrator server's Distribution Center.
  • Change the login= and password= settings to the login and password for your FTP server.

Do not make changes to any other lines in the file.

 

To configure an internal LiveUpdate server to use a HTTP protocol connection

1 For safety, make a backup copy of the following file:

/etc/liveupdate.conf

2 Make the following changes to the liveupdate.conf file:

  • Change the protocol setting to protocol=http.
  • Change the host= line from liveupdate.symantec.com to your internal LiveUpdate Administrator server's Distribution Center.

Do not make changes to any other lines in the file.

 

Configuring an internal LiveUpdate server to use a host file

You can configure liveupdate.conf to use a host (.hst) file that is created by the LUA 2.x server or LUAU 1.x utility.  You can continue using an existing liveupdt.hst file from an earlier installation  with some modifications, or you can create a new host file.

The liveupdt.hst file is created from LUA's Client Setting screen.  Be sure to export Java Settings, not Windows.  

 

 

 

The liveupdt.hst file is then copied to each SMSDOM server and liveupdate.conf altered to reference that file.

To configure an internal LiveUpdate server to use an existing liveupdt.hst file, add the following line to the /etc/liveupdate.conf file:

hostfile=<full path to the .hst file on the server>

If the hostfile= parameter is included in liveupdate.conf, all other lines are ignored and data from the .hst file is used instead.

 


Attachments