[GH-ISSUE #2198] [Feature Request] Better handling of automation policy exclusions / server reboots #3304

New issue

Open

opened 2026-03-14 07:05:42 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 07:05:42 +03:00

Owner

Originally created by @joeldeteves on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2198

Is your feature request related to a problem? Please describe.
Our current Default Server Policy applies a set of standard checks and tasks across the board. However, for certain server roles e.g. domain controllers, print servers, file servers, etc. we have custom policies layerd underneath them at the agent level.

This works well for everything except handling reboots: we can either set a scheduled task to reboot with a random task delay and hope our domain controllers aren't rebooted too close to other servers, or we can schedule each server agent manually which is extremely time consuming and error-prone.

Describe the solution you'd like
It would be nice if there was a better way to handle automation exclusions at the Default level. Not sure how this would look as currently we can only exclude from the entire policy which isn't great. Another possible solution is to allow adding multiple policies as defaults (example we could have a Scheduled Reboot Policy applied as well as our Default Server Policy, then exclude our DCs from the default Scheduled Reboot policy).

Describe alternatives you've considered
I don't really have a great solution at the moment

Additional context
N/A

Originally created by @joeldeteves on GitHub (Apr 8, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2198 **Is your feature request related to a problem? Please describe.** Our current Default Server Policy applies a set of standard checks and tasks across the board. However, for certain server roles e.g. domain controllers, print servers, file servers, etc. we have custom policies layerd underneath them at the agent level. This works well for everything except handling reboots: we can either set a scheduled task to reboot with a random task delay and hope our domain controllers aren't rebooted too close to other servers, or we can schedule each server agent manually which is extremely time consuming and error-prone. **Describe the solution you'd like** It would be nice if there was a better way to handle automation exclusions at the Default level. Not sure how this would look as currently we can only exclude from the entire policy which isn't great. Another possible solution is to allow adding multiple policies as defaults (example we could have a Scheduled Reboot Policy applied as well as our Default Server Policy, then exclude our DCs from the default Scheduled Reboot policy). **Describe alternatives you've considered** I don't really have a great solution at the moment **Additional context** N/A

kerem commented

2026-03-14 07:05:48 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Apr 9, 2025):

eset has something similar to what you are asking "throttling" to tasks where no 2 same tasks can be executed at the same time

i also requested something similar for one off's
https://github.com/amidaware/tacticalrmm/issues/1802

my current solution :
https://github.com/amidaware/community-scripts/tree/main/scripts_staging/TasksUpdater

i have got a var on each server containing the template updates / reboot times of each devices and a script will process these info to schedule all the tasks

@P6g9YHK6 commented on GitHub (Apr 9, 2025): eset has something similar to what you are asking "throttling" to tasks where no 2 same tasks can be executed at the same time ![Image](https://github.com/user-attachments/assets/74422ee0-3ad6-4ad0-8e67-2e8bd3e65f0c) i also requested something similar for one off's https://github.com/amidaware/tacticalrmm/issues/1802 my current solution : https://github.com/amidaware/community-scripts/tree/main/scripts_staging/TasksUpdater i have got a var on each server containing the template updates / reboot times of each devices and a script will process these info to schedule all the tasks ![Image](https://github.com/user-attachments/assets/b3e52066-f6ff-4555-9040-e7ad05a34d8c)