Protection Engine for Network Attached Storage

 Hello,

I am evaluating Symantec AntiVirus 5.2 for Network Attached Storage (NAS) on a Windows 2008 x64 server, and while the install seemed fine, liveupdate doesn't detect any product except itself. In the liveupdate log file, I see that the local mirror is contacted, downloads succeed,

7/15/2011, 14:57:37 GMT -> Check for updates to:  Product: LiveUpdate, Version: 3.3.0.101, Language: English.  Mini-TRI file name: liveupdate_3.3.0.101_english_livetri.zip

but no mention of the NAS product. Any hints?

Hey,

can you post the liveupdt.log content? What is the command line it uses when launching the JLU?

As a workaround, you can try installing the rapid release defs (i guess you are just testing in a lab/demo environment) as described here:

http://98.129.119.164/connect/fr/blogs/scan-engine-server-2008-64-bit-intelligent-updater-shadowing

 Hello - log attached.

The update files are served by a local iis server. I can manually update, of course, but part of my evaluation is to see if liveupdate runs..

Attachment(s)

liveupdatelog_0.txt   296 KB 1 version

Hi,

this looks like the normal liveupdate log file, not java liveupdate - do you have any other symc product installed on the same system?

search your hdd for "liveupdt.log"

Scan Engine uses Java LiveUpdate which does not work in the same way as the regular live update you may be used to that you see with Symantec Endpoint protection. In the Scan Engine interface under system you should be able to see the liveupdate status and defintions that are used by the Scan Engine if they are current defintions Java LiveUpdate is working.

Problem solved - after some serious struggle and the assistance of a Symantec employee over Webex (which doesn't speak well of the usability of this product)

1. Java Liveupdate (it was present on the system because Endpoint protection installed it) is not used, the Scan Engine runs its own copy, which is also a java app, thus my confusion.

2. The config file must be saved encrypted by the java editor (java -classpath jlu.jar ConfigEditor), the plain text version will be read, but the update will fail.

3. The update server's cache (the one available at http://address:7070) was not complete, but the updater log was not very helpful, it simply exited with success and "no updates available".

Java Liveupdate is not used by Endpoint Security, that uses Liveupdate. The config file does not need to be encrypted, but it can be if you are using a proxy and do not want your username and password saved in a plaintext file.