starred/tacticalrmm

Fork 0

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

[GH-ISSUE #63] Feature Request: Policies For Servers and/or Workstations #1974

New issue

Closed

opened 2026-03-14 01:54:52 +03:00 by kerem · 6 comments

kerem commented

2026-03-14 01:54:52 +03:00

Owner

Originally created by @bradhawkins85 on GitHub (Aug 21, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/63

Originally assigned to: @sadnub on GitHub.

Would it be possible to configure a policy so that it only applies to Servers or Workstations (or both)?
E.G. Disk Space check for Servers vs Workstations could be at different percentages? Or only apply a Service Check to Servers etc.

Perhaps two tick boxes, Apply To: Servers, Workstations when creating/editing a policy?

Originally created by @bradhawkins85 on GitHub (Aug 21, 2020). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/63 Originally assigned to: @sadnub on GitHub. Would it be possible to configure a policy so that it only applies to Servers or Workstations (or both)? E.G. Disk Space check for Servers vs Workstations could be at different percentages? Or only apply a Service Check to Servers etc. Perhaps two tick boxes, Apply To: Servers, Workstations when creating/editing a policy?

kerem

2026-03-14 01:54:52 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-14 01:55:08 +03:00

Author

Owner

@bradhawkins85 commented on GitHub (Aug 21, 2020):

I've just noticed you can only apply one policy to a client or site, so this may not work anyway. Unless it can be possible to assign multiple policies to clients and sites.

@bradhawkins85 commented on GitHub (Aug 21, 2020): I've just noticed you can only apply one policy to a client or site, so this may not work anyway. Unless it can be possible to assign multiple policies to clients and sites.

kerem commented

2026-03-14 01:55:13 +03:00

Author

Owner

@sadnub commented on GitHub (Aug 21, 2020):

@bradhawkins85
Thanks for the heads up! I was thinking more about this and it might make sense to create separate workstation and server policies per container.

So instead of applying a single policy to a client, site, and agent, you can apply server and workstation policies to them. So when you go to apply a policy, there would be a drop-down for workstation policy and one for server policy and you can assign any existing policy to them.

Currently you can only assign a single policy per container, but splitting up the server/workstation policies will help with most use cases.

Does that sound good? I can start working on that if so.

@sadnub commented on GitHub (Aug 21, 2020): @bradhawkins85 Thanks for the heads up! I was thinking more about this and it might make sense to create separate workstation and server policies per container. So instead of applying a single policy to a client, site, and agent, you can apply server and workstation policies to them. So when you go to apply a policy, there would be a drop-down for workstation policy and one for server policy and you can assign any existing policy to them. Currently you can only assign a single policy per container, but splitting up the server/workstation policies will help with most use cases. Does that sound good? I can start working on that if so.

kerem commented

2026-03-14 01:55:18 +03:00

Author

Owner

@Omnicef commented on GitHub (Aug 21, 2020):

I vote for separate Server/Workstation Policies. Thanks sadnub for all your hard work!

@Omnicef commented on GitHub (Aug 21, 2020): I vote for separate Server/Workstation Policies. Thanks sadnub for all your hard work!

kerem commented

2026-03-14 01:55:23 +03:00

Author

Owner

@bradhawkins85 commented on GitHub (Aug 25, 2020):

sadnub that sounds good, would it be too much to allow multiple policies per container as well?
It will increase the flexibility of what can be done with policies in the long run.

@bradhawkins85 commented on GitHub (Aug 25, 2020): sadnub that sounds good, would it be too much to allow multiple policies per container as well? It will increase the flexibility of what can be done with policies in the long run.

kerem commented

2026-03-14 01:55:28 +03:00

Author

Owner

@sadnub commented on GitHub (Aug 26, 2020):

@bradhawkins85 I was having issues getting the multiple policies to work properly. I was also unsure which checks should take precedence if there were multiple conflicting checks applied to site.

I am thinking a group-based approach might be more flexible, but that would take a while to implement.

I did just submit a PR to separate the workstation/server policies. That should allow for more flexibility.

One thing to note is the policies applied to clients and sites will need to be added again since the DB schema changed.

@sadnub commented on GitHub (Aug 26, 2020): @bradhawkins85 I was having issues getting the multiple policies to work properly. I was also unsure which checks should take precedence if there were multiple conflicting checks applied to site. I am thinking a group-based approach might be more flexible, but that would take a while to implement. I did just submit a PR to separate the workstation/server policies. That should allow for more flexibility. One thing to note is the policies applied to clients and sites will need to be added again since the DB schema changed.

kerem commented

2026-03-14 01:55:33 +03:00

Author

Owner

@sadnub commented on GitHub (Aug 26, 2020):

This PR has been merged. Let me know if you have any issues!

@sadnub commented on GitHub (Aug 26, 2020): This PR has been merged. Let me know if you have any issues!

kerem referenced this issue

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

[GH-ISSUE #1974] Users and Rols #3180

kerem referenced this issue

2026-03-14 07:13:26 +03:00