mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1323] Agent settings policy's for workstations and Servers #825
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#825
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mvthul on GitHub (Oct 21, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1323
Would like to see a option/policy to setup default general settings for agent.
Example workstation agent settings policy
- Disable check get overdue email alerts
Example server agent settings policy
- Enable check get overdue email alerts
@silversword411 commented on GitHub (Oct 21, 2022):
You're explaining what general policies are
There's already another feature request about helping people or having a recommended template for new installs here. https://github.com/amidaware/tacticalrmm/issues/1247
Unless you have other information, I'll close this as dupe in 24hrs
@mvthul commented on GitHub (Oct 22, 2022):
Hi @silversword411 i c but there is no policy or global setting to configure these settings. This can be done only manual now.
@joeldeteves commented on GitHub (Nov 27, 2022):
It's possible to set the alert settings using an Alerts Template, however currently it does not appear to be possible to configure the default offline and overdue timeouts using a template.
I think that would be a useful feature @silversword411
@3gmgithub commented on GitHub (Jan 19, 2023):
I second this I just spent like 20 minutes looking where to set the global setting for this and could not find it...
This confirmed it is not available.
@silversword411 commented on GitHub (Jan 20, 2023):
I completely misread your request, you want a policy for the times.
Pretty sure there's another request for this.
The problem as explained to me by wh1te is that these numbers are actually part of the postgres db schema, and read from there so you'd have to be able to change your DB schema defaults...on the fly which I think is a prpblem and lots of work. Hence the not done yet.
@maieredv-manuel commented on GitHub (Feb 10, 2026):
Is there any news about this topic?
Would be nice to change the timeouts for all Workstations / Servers at once ...