Queue Tasks for Offline Computers

72 votes

The ability to queue up tasks to be completed for computers that are currently offline so that next time they're turned on they run. At present only able to run tasks on active machines, however this isn't optimal with many users being online at random intervals (i.e. Laptops) it's difficult to get some done.

Under consideration Automation Suggested by: Ryan M (09 Feb, '21) • Upvoted: 05 Apr • Comments: 5

Comments: 5

27 Aug, '21
AC_Martin
Yeah!
By doing this we no longer have to run tasks repeatedly to include clients that were offline during previous runs.
19 May, '22
20100
It is a must have and I cannot believe it is not working! It is available for Patch management, so should be for tasks.
With machine all over the world, only those on line are picked up.
We should not have to create copies of a task with different time schedule (somehow we always miss some!) and at the moment we cannot even say to run a task every hour (we would add a check in the script to ensure it does run again if it has already!)
All machines needs to get tasks activated as soon as they are online
20 Sep, '22
Donato
Agree this is a pretty important feature. How else can I guarantee all systems in an org get a task I want run.
22 Jun, '23
Zack B
I agree. Anyone looking for a temporary workaround:

1. Create a CF (Custom Field) with the "Contexts" set to "System".
2. Insert the CF within your script as both an Input and Output custom variable.
a. Input checks the current value of the CF.
b. Output sets/updates the value of the CF.
3. Have your script check the Value of the CF (Input Variable) and use if/elif/else statements to either run what you are trying to accomplish or to exit the script.
4. At the end of your script, set/update the Value of the CF (using Output Variable).
5. Create a Workflow with the trigger "System Back Online".
6. Have the first condition check the Agent Group. (Assuming you have Laptops in it's own Agent Group within your Organizational config).
7. Answer:
a. Pass = Create condition to check the CF.
b. Fail = End Workflow. (Don't continue guide.)
8. Answer:
a. Pass = End Workflow.
b. Fail = Run Script

1-8a runs on the server and 8b on Host. ie Doesn't tax host unless it needs to.
01 Mar
John
This really needs to be put in place