Strange update behaviour

Hello all,
Yesterday night I observed a strange behaviour of NOD32 update scheduler.
I have 2 different PC. Before I start both PC, :

PC 1 had update 2940
PC 2 had update 2941

Both PC were off till at least 6 hours...


When I started at the same time both PC, PC 2 were updated with 2942 and PC 1 with 2941...

After half an hour, I decided to manualy update PC1 to 2942 because I saw in scheduling configuration that update was to be performed every hour...

So my to questions :

1) Why, at startup, PC 1 was updated from 2940 to 2941 (and not 2940 to 2942, as for PC 2) ? What is ESET strategy regarding update ?

2) Why possibility to update at session login (see User Guide) is unchecked by default ?


Regards

 

Hi, was it really at <the same time> (I think starting update)? Eg, PC 1 was updated at 01:43 and pc 2 at 01:48. During these 5 minutes update could be released on the server.

 

Hi,

Yes it is a possibility... There is probably about 2 minutes delay between my 2 PC end of startup and Nod32 sig files updates... I will check at home, on log event to see is that can be the reason...

Well, now about period in schedule table : don't you thing 60 min could be reduce to 10 min for example ?

In the other hand, what is probability to be infected with a threat, in a range of one hour before updating the very last definition file, if the PC is up to date with the previous ?

Regards

 

Yes, you can reduce period of update, but I think it isn't so much important for peronal computer, for server is better set up shorter period for better protection.

There is some possibility to be infected, but I think it is very small chance. Only if you download unknow file and run it (eg. Win32/Wipacha.A, Win32/KillWin.NAG can cause corruption of your computer during few seconds).

 

Back to home, this is my update :
Initial state :
Labtop : 12/03/2008 : release 2940
PC : 12/03/2008 : release 2940
At 13:00
Both were in fact with 2940 !!!


Final state yersterday after startup :

Labtop updated from 2940 to 2941 at 18:21:59
------------------------------------------------
12/03/2008 18:21:59 Noyau Base des signatures correctement mise à jour vers la version 2941 (20080312).
------------------------------------------------
PC updated from 2940 to 2942 at 18:21:43

Note that both PC are synchronized so no clock problems !!!

So why my PC first updated with 2942 and my Labtop
, updated later with 2941



Note that today both are with 2945 (at 18:20)

Sorry but something is strange !!!
Thanks in advance for informations

 

It looks like both computers updated in the same minute. If a newer update was release at about that time, it would take some time for the update files to propagate to all update servers.

 

Yes Marcos you are right... Probably both PC did not get update files on the same server... That's why both PC did not get the same release because of propagation delay...

Regards

 

jup, i get a notify on my laptop a bit before my gaming rig
so it might take upto a 10min to get all the updates servers mirrored