ruidc 0 Posted September 25, 2015 Share Posted September 25, 2015 We have a nightly scan scheduled job at 10pm and it is set to "Run task immediately if the time since its last execution exceeds specified interval" where I have set 24 hrs. My understanding of this setting is that if the computer was turned off Tuesday night before 10pm and then used Wednesday morning but again turned off before 10pm, that upon use Thursday morning the nightly scan should run. But this does not seem to be happening on multiple machines. Can someone confirm what is expected from this setting in this case or clarify how I can set up a schedule for a daily scan that would run on the Thursday login for the above scenario? Thanks (EAV v5) Link to comment Share on other sites More sharing options...
ESET Moderators TomasP 317 Posted September 25, 2015 ESET Moderators Share Posted September 25, 2015 Hi, please check whether the task has a "Last run" time recorded (so that it can compare to the time it was last run). Anyway, does using "As soon as possible" work for you? Link to comment Share on other sites More sharing options...
ruidc 0 Posted September 25, 2015 Author Share Posted September 25, 2015 I spotted it to the last run time, it was set to Monday evening - that's how i spotted this. I was avoiding the "As soon as possible" setting to avoid too-frequent scans, but that will be my fallback if we cannot get this setting to work as expected. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,090 Posted September 25, 2015 Administrators Share Posted September 25, 2015 I'd suggest trying out the latest Endpoint v6 and see if it makes a difference. Link to comment Share on other sites More sharing options...
ruidc 0 Posted September 25, 2015 Author Share Posted September 25, 2015 ah,no too many issues. v5 is still supported right? Link to comment Share on other sites More sharing options...
ESET Moderators TomasP 317 Posted September 25, 2015 ESET Moderators Share Posted September 25, 2015 It is, but as it is not the latest version, any new features or changes will be applied to the current (v6) version. What issues do you encounter with version 6? Link to comment Share on other sites More sharing options...
ruidc 0 Posted September 25, 2015 Author Share Posted September 25, 2015 Too many to list here. Can we get back to the original question? Link to comment Share on other sites More sharing options...
ESET Moderators TomasP 317 Posted September 25, 2015 ESET Moderators Share Posted September 25, 2015 Well, frankly, to answer the original question, it would be best to compare the behaviour to Endpoint v6 running on the same machine where the problem occurs with v5. Just so that we know whether it is something that has been fixed in the meantime; you don't need to keep running v6 permanently now. Link to comment Share on other sites More sharing options...
ruidc 0 Posted September 25, 2015 Author Share Posted September 25, 2015 I am not going to deploy v6 to test a problem with v5 - I was cleaning up the mess for weeks after I tried that last time. Even if it works with v6 how does that help me when I will NOT be rolling out v6?Can you advise if : 1. my understanding of how this setting is supposed to work is correct or correct me if not 2. achieving the desired behaviour is possible in v5 Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts