FerdinandG 3 Posted August 24, 2020 Share Posted August 24, 2020 Hi, I created an on-demand in depth scan task and set a weekly trigger on it. The task starts every Saturday at 00.00 AM. My goal is to run an in depth scan to computers that still powered on over the weekend. However, on Monday morning, I notice that there are computers start to run the task, although those computers were turned off during the weekend and powered on on Monday morning. Can I define the range/expiration of the trigger, let say 24 hours, so for clients who did not receive the trigger in 24 hours after the defined schedule (in this case the clients are off during the weekend) will not triggered to do the scan on Monday morning? Thanks Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted August 24, 2020 Administrators Share Posted August 24, 2020 Did you schedule a weekly scan and select to run at the next scheduled time if the task could not run? Link to comment Share on other sites More sharing options...
FerdinandG 3 Posted August 24, 2020 Author Share Posted August 24, 2020 Hi Marcos, I created the task and the trigger from Tasks menu on ESMC ver 7.2, but I could not find the settings for skipped task in there. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted August 24, 2020 Administrators Share Posted August 24, 2020 I was referring to Scheduler settings in a policy. However, I don't see a reason why it would not work with client tasks as well and I'd expect the scan to not start on Monday if "Invode ASAP if event missed" is not checked. Link to comment Share on other sites More sharing options...
FerdinandG 3 Posted August 24, 2020 Author Share Posted August 24, 2020 I just read about Time Based Criteria in Throttling setting. Is this something that I can also use to set the range when the task is allowed to run? Link to comment Share on other sites More sharing options...
Recommended Posts