starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 23:15:57 +03:00

scripts #309

New issue

Open

opened 2026-03-02 02:15:19 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 02:15:19 +03:00

Owner

Originally created by @renbanford on GitHub (May 12, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/497

When scheduling tasks, scripts and checks (Whether using the bulk schedule tools, under the agent details or via automation policies), it would be nice to have a "skip if offline" option (Similar to Kaseya), which allows you to skip machines that are not currently reporting in/offline. It may also be pertinent to also skip running the associated task/script on machines which are in maintenance mode, if this option were to be selected.

Originally created by @renbanford on GitHub (May 12, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/497 When scheduling tasks, scripts and checks (Whether using the bulk schedule tools, under the agent details or via automation policies), it would be nice to have a "skip if offline" option (Similar to Kaseya), which allows you to skip machines that are not currently reporting in/offline. It may also be pertinent to also skip running the associated task/script on machines which are in maintenance mode, if this option were to be selected.

kerem added the

enhancement

label

2026-03-02 02:15:19 +03:00

kerem commented

2026-03-02 02:15:20 +03:00

Author

Owner

@wh1te909 commented on GitHub (May 12, 2021):

this is already happening, scripts and commands are fire and forget so if the agent is offline it's not gonna get it anyway
only thing i could add would be to skip online agents in maintenance mode

@wh1te909 commented on GitHub (May 12, 2021): this is already happening, scripts and commands are fire and forget so if the agent is offline it's not gonna get it anyway only thing i could add would be to skip online agents in maintenance mode

kerem commented

2026-03-02 02:15:20 +03:00

Author

Owner

@renbanford commented on GitHub (May 13, 2021):

The "fire and forget" option doesn't appear when scheduling a task:

I was thinking possibly to be able to have a regular, scheduled task skipped when a machine is offline/in maintenance mode?

@renbanford commented on GitHub (May 13, 2021): The "fire and forget" option doesn't appear when scheduling a task: ![image](https://user-images.githubusercontent.com/12677339/118078028-a5366980-b3f8-11eb-9fa5-e48d9855406b.png) I was thinking possibly to be able to have a regular, scheduled task skipped when a machine is offline/in maintenance mode?

kerem commented

2026-03-02 02:15:20 +03:00

Author

Owner

@wh1te909 commented on GitHub (May 13, 2021):

"add automated task" you can think of a web wrapper around the windows task scheduler.

create a task and then look in task scheduler on the agent and you'll see the task created. obviously if the computer is turned off then the task wont run.

and if the agent is "offline" meaning the computer is turned on but has no internet, the task will attempt to run and fail. the way it works is agent just stores the task id, and when it's time to run it reaches out to the rmm with the task id. rmm queries database for that id, and sends back to the agent all the info like the script, timeout etc. so without this info the agent cannot run the task and so it will simply return without running.

so basically if an agent is offline its not going to be able to run anything anyway. hopefully that clears up what i meant by fire and forget. same thing with running bulk commands, scripts etc. rmm will just fire and forget to all the agents you selected. if the agent is not responding the rmm doesn't care it will just skip it and move on to the next

so only option i see is adding a "skip if in maintenance mode"

@wh1te909 commented on GitHub (May 13, 2021): "add automated task" you can think of a web wrapper around the windows task scheduler. create a task and then look in task scheduler on the agent and you'll see the task created. obviously if the computer is turned off then the task wont run. and if the agent is "offline" meaning the computer is turned on but has no internet, the task will attempt to run and fail. the way it works is agent just stores the task id, and when it's time to run it reaches out to the rmm with the task id. rmm queries database for that id, and sends back to the agent all the info like the script, timeout etc. so without this info the agent cannot run the task and so it will simply return without running. so basically if an agent is offline its not going to be able to run anything anyway. hopefully that clears up what i meant by fire and forget. same thing with running bulk commands, scripts etc. rmm will just fire and forget to all the agents you selected. if the agent is not responding the rmm doesn't care it will just skip it and move on to the next so only option i see is adding a "skip if in maintenance mode"

kerem commented

2026-03-02 02:15:20 +03:00

Author

Owner

@renbanford commented on GitHub (May 14, 2021):

Ah, understood - thank you.

A "skip if in maintenance mode" would also be useful :)

@renbanford commented on GitHub (May 14, 2021): Ah, understood - thank you. A "skip if in maintenance mode" would also be useful :)

kerem referenced this issue

2026-03-02 02:23:55 +03:00

[PR #309] [CLOSED] Adding example GPO deploy script #1591

kerem referenced this issue

2026-03-14 07:25:44 +03:00

[PR #309] [CLOSED] Adding example GPO deploy script #3541