RA 2.0.107 Released

ESET.ch Mailing List * May 21 2008
--------------------------------------------------------------------

In this issue:

1.) ESET NOD32 Antivirus & ESET Smart Security v3.0.657 released
2.) ESET Remote Administrator v2.0.107 released


(c)2008, Idiosyn Security GmbH, Bern, Switzerland - www.eset.ch
---------------------------------------------------------------------

[English]

1.) ESET NOD32 Antivirus & ESET Smart Security v3.0.657 released

The English version 3.0.657 of both ESET NOD32 Antivirus and ESET Smart Security 3.0.657 has been released today.

To upgrade to this newer release, you will have to download the full installer.

v3.0.657 addresses the following issues:

* Fixed problem causing system instability on Microsoft Windows
Server platform
* Improved stability for users when using Microsoft Windows Mail
* Fixed issue with deleting emails from a server using POP3 protocol
* Fixed incompatibility with PC Translator software
* Fixed issue with incorrect message statistics in Antispam module


2.) ESET Remote Administrator v2.0.107 released

This build fixes a number of issues and offers product enhancements:

Updates:
o added capability of a mirror for NOD32 v2 clients
o global logs level filtering (advanced settings)
o updater errors with text information (in server log)
o updated configuration template

Fixed issues:
o incorrect formatting in OS application log
o problem in configuration template is now fixed
o copying the license key from a network drive in setup
[FONT=&quot]o few other minor bugs are fixed[/FONT]

 

When I select "create mirrored update files for Nod32 version2" YES and then select my 2 English components save and reset the server, netstat -na shows nothing on port 8081.

By default nod32 2.7 used port 8081 and 3.0 uses 2221. Does this new option require me to reconfigure my 2.7 clients to use port 2221?

 

You need to point your v2 clients to the same location as you point your v3 clients.

e.g. if you point your v3 clients at http://<server_name>:8090/ (default), then do the same for your v2 clients.

Once you've done this for all v2 clients, you can turn off the old mirror.

I've done that, and it's working fine. Even XMON is pointing to the new mirror and updating no problem.

 

Correction. What the boys and girls at ESET haven't told us, is if you want to point your v2 clients at your RA 2.0.x mirror, you need to configure the update path on the v2 clients and set it to "http://<server_name>:<mirror_port>/nod32v2/" as opposed to what your v3 clients are currently set to.

If you point your v2 clients at the same URL as your v3 clients, they will report they are updating no problem. However when I looked at XMON a few moments ago it said it was behind with the defs by 2 days, even though the update module has been successfully updating. The problem was it was not looking at the nod32v2 folder - something ESET haven't told us to do.

Well done ESET, well done!