Updates for Symantec Security Information Manager (SSIM) 4.x and/or the SSIM Event Collectors may be provided internally on a network by the current LiveUpdate Administrator 2.3.x (LUA 2.3.x) server. This article provides details on how to update SSIM and/or the SSIM Event Collectors using the current LUA 2.3.x.
LiveUpdate Administrator 220.127.116.11 or newer is required to successfully retrieve LiveUpdate content for the SSIM Event Collectors. To download the latest verison of LUA 2.3.x, please visit What is the latest version of Symantec LiveUpdate Administrator 2.x (LUA 2.x)?
Please review the documents in provided for LiveUpdate Administrator for requirements to install the server. At the time of this document the information is available here
Install the latest available LiveUpdate Administrator 2.3.x and make a note of where the download and distributed packages are placed. You can change these paths if required.
One you have installed LUA 2.3.x you will have to create a "download and distribution" schedule for SSIM 4.5, 4.6, 4.7,4.8 and collectors.
Configure LiveUpdate Administrator 2.3x for SSIM and SSIM Collectors only
Note: Before you create the Java LiveUpdate configuration for SSIM and off box collectors open browser and type in the URL for the distribuition center. You should see a list of files in this directory. If you do not see a list of files, the download or distribution might have failed or was not correctly set up, the names on these files will contain the name of the collector update.
Setup the Java LiveUpdate configuration on the SSIM 4.x or any offbox Event Agent/Collector
To create the Java LiveUpdate configuration:
To setup the Java LiveUpdate configuration
If you have more than one LiveUpdate Administration Distribution Center configured, you may set up additional Hosts within the configuration.
Important Note: LiveUpdate Administrator uses Apache Tomcat as a webserver. If you install LUA 2.x on a computer with IIS running or the Symantec Endpoint Protection Manager (SEPM), you might run into conflicts with resources and ports. This document was tested on a machine without IIS, a SEPM or the SEP database.