Why is scan started before update?

Discussion in 'ESET NOD32 Antivirus' started by RobJanssen, Aug 13, 2012.

Thread Status:
Not open for further replies.
  1. RobJanssen

    RobJanssen Registered Member

    Joined:
    Jul 15, 2011
    Posts:
    55
    We use NOD32 4.2.76.1
    This weekend I decided to scan all workstations to be sure there is no virus that crept in at a time it was not yet detected by the signatures.
    So I powered on all workstations by wake-on-LAN, waited half an hour so that everyone has the uptodate signatures, and started a "scan" task form the remote administrator.
    This went fine. However, there are always workstations that are not responding to the wake-on-LAN (config error, laptop which is away, etc).
    The task is still there so when these workstations are switched on, the scan will start.

    HOWEVER, the scan is already started using the signatures present on the workstation from the last time it was on the network, and the update takes place during/after the scan.

    WHY? Why is the scanner not waiting for the signature update before it starts working on the scan job? This seems so much safer...
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    You can delay the scan task so that the chances it will be run after an update will be higher, depending on how much it will be delayed. I've suggested our product managers an improvement in this regard for future versions of Endpoint.
     
  3. RobJanssen

    RobJanssen Registered Member

    Joined:
    Jul 15, 2011
    Posts:
    55
    Ok, thanks!

    I think I can delay the task only to an absolute point in time, not a time relative to the startup of the system. It is not very useful for the mentioned purpose because not all systems are logged in at the same time. There are now still some (laptop) systems that have not connected after I installed the task in the weekend, and they will start scanning as soon as they receive the task, which probably is when the owner comes back from holidays. By then they are scanning with really old signatures.

    It would be nice if the scan would start "30 minutes after boot" for example, or dependent on the update event ("start scan after updating", more or less like the system critical files scan that is started after the update.
     
Thread Status:
Not open for further replies.