[GH-ISSUE #1802] Bulk Reboot scheduler #3067

New issue

Open

opened 2026-03-14 06:25:12 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 06:25:12 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Mar 19, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1802

Is your feature request related to a problem? Please describe.

Manually planning reboots for each agent can be cumbersome, especially when it's not scripted.

Describe the solution you'd like

I propose the addition of a "Bulk Reboot Menu" feature, similar to the existing "Bulk Command" and "Bulk Script" functionalities. This feature would allow users to schedule reboots for multiple devices based on client, site, or agents. Additionally, it should offer options to spread the reboots evenly over a specified interval. For instance, if 6 machines are scheduled for reboot with a 10-minute interval, the last one would reboot an hour after the first.

Describe alternatives you've considered

While scripts and automation policies can be used, they lack the ability to schedule reboots at regular intervals. Scripting only allows for random reboot times, which makes it challenging to ensure a smooth sequence of reboots.

Originally created by @P6g9YHK6 on GitHub (Mar 19, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1802 **Is your feature request related to a problem? Please describe.** Manually planning reboots for each agent can be cumbersome, especially when it's not scripted. **Describe the solution you'd like** I propose the addition of a "Bulk Reboot Menu" feature, similar to the existing "Bulk Command" and "Bulk Script" functionalities. This feature would allow users to schedule reboots for multiple devices based on client, site, or agents. Additionally, it should offer options to spread the reboots evenly over a specified interval. For instance, if 6 machines are scheduled for reboot with a 10-minute interval, the last one would reboot an hour after the first. **Describe alternatives you've considered** While scripts and automation policies can be used, they lack the ability to schedule reboots at regular intervals. Scripting only allows for random reboot times, which makes it challenging to ensure a smooth sequence of reboots.

kerem commented

2026-03-14 06:25:19 +03:00

Author

Owner

@NiceGuyIT commented on GitHub (Mar 19, 2024):

This is similar to or a duplicate of

#1459

@NiceGuyIT commented on GitHub (Mar 19, 2024): This is similar to or a duplicate of - #1459

kerem commented

2026-03-14 06:25:24 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Mar 19, 2024):

similar yes
duplicate no

i don't think both request are mutualy exclusive.

@P6g9YHK6 commented on GitHub (Mar 19, 2024): similar yes duplicate no i don't think both request are mutualy exclusive.

kerem commented

2026-03-14 06:25:29 +03:00

Author

Owner

@bbrendon commented on GitHub (Mar 19, 2024):

Why can't you use tasks? Tasks run on a schedule.

@bbrendon commented on GitHub (Mar 19, 2024): Why can't you use tasks? Tasks run on a schedule.

kerem commented

2026-03-14 06:25:34 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Mar 19, 2024):

Why can't you use tasks? Tasks run on a schedule.

for the same reasons there is dedicated "reboot" button rather than only a "send command" button.
Convinience and if this convinience is available, more tools can be built around it. (i gave the exemple of the intervals)

@P6g9YHK6 commented on GitHub (Mar 19, 2024): > Why can't you use tasks? Tasks run on a schedule. for the same reasons there is dedicated "reboot" button rather than only a "send command" button. Convinience and if this convinience is available, more tools can be built around it. (i gave the exemple of the intervals)