no signature update via ERA

I installed the nod32 antivirus business edition beta on our era test server.
The systems ran the new era beta too. Result: no chance to get signature update.
The client ist downloading some files - VERY slow - and at the last step called 1/2 it fails. I then switched the client to you productive era system (running 3.1.15). same problem.
Then I setup the internet update connection via our proxy and all went fine. I know switched back to internal era beta update and I will see what happens if the next signature update arrives.

regards
mike

 

The beta uses some modules that are newer than those on the update servers and thus can update only from specific pre-release update servers.

 

Thank you for the explanation.

 

So I can't test the new nod32 beta with the new RA beta?
Any chance to get the RA beta connection to the "pre-release update servers"?

I can't understand why two new released beta's are not playing togehter...

 

I installed the beta (NOD32 AV BE 4.2.22) on my personal machine for testing. It's reporting into RAS 3.1.11. At first I wasn't getting updates, but I went into the advanced settings of the beta client (AV-->Update-->Advanced update Setup) and turned on "Enable pre-release updates" and that seems to have fixed it.

Hope that helps.

 

that works - great
where did you find this information - in any beta document by eset?

regards
mike

 

In ERA4, it's possible to enable download of pre-release updates in the ERA setup - Advanced - Update server group -> Pre-release update servers. However, this is not recommended as ERA would distribute pre-release module updates to all clients updating from it which is probably not desired in corporate networks with production systems.

 

Thanxxx - parameter changed
Only testclients with nod32 beta will connect to this server, no productive clients.

 

Actually I just guessed. Luckily, it was my first guess.