You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)
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.
The text was updated successfully, but these errors were encountered: