[GH-ISSUE #713] Automation Policy 'Block Policy Inheritance' Not Functioning #453

New issue

Closed

opened 2026-03-02 02:16:28 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 02:16:28 +03:00

Owner

Originally created by @r3die on GitHub (Sep 15, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/713

Originally assigned to: @sadnub on GitHub.

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: Chrome & Edge
RMM Version (as shown in top left of web UI):0.8.4

Installation Method:

[X ] Standard
Docker

Describe the bug
When an Automation Policy is set to a Client or Site and 'Block Policy Inheritance' is checked on a specific agent, the checks from the policy are still inherited from the Automation Policy of the Parent OU

To Reproduce
Steps to reproduce the behavior:

Select a Client Site , right click and Assign Automation Policy
Select an agent under that site, right click and Assign Automation policy (choose a different policy and check 'Block Policy Inheritance')
Refresh checks/ Sync policies and review checks of the agent that should have the policy blocked to find the original checks are still present

Expected behavior
After Syncing Automation Policies and Refreshing the checks on the agent the checks from the policy assigned to the parent OU should not be present.

Originally created by @r3die on GitHub (Sep 15, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/713 Originally assigned to: @sadnub on GitHub. **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: Chrome & Edge - RMM Version (as shown in top left of web UI):0.8.4 **Installation Method:** - [X ] Standard - [ ] Docker **Describe the bug** When an Automation Policy is set to a Client or Site and 'Block Policy Inheritance' is checked on a specific agent, the checks from the policy are still inherited from the Automation Policy of the Parent OU **To Reproduce** Steps to reproduce the behavior: 1. Select a Client Site , right click and Assign Automation Policy 2. Select an agent under that site, right click and Assign Automation policy (choose a different policy and check 'Block Policy Inheritance') 4. Refresh checks/ Sync policies and review checks of the agent that should have the policy blocked to find the original checks are still present **Expected behavior** After Syncing Automation Policies and Refreshing the checks on the agent the checks from the policy assigned to the parent OU should not be present.

kerem

2026-03-02 02:16:28 +03:00

closed this issue
added the
bug

fixed
labels

kerem commented

2026-03-02 02:16:29 +03:00

Author

Owner

@sadnub commented on GitHub (Sep 24, 2021):

It looks like the checkbox wasn't actually saving when set in the UI. I just submitted a fix for this. Will be in the next update.

@sadnub commented on GitHub (Sep 24, 2021): It looks like the checkbox wasn't actually saving when set in the UI. I just submitted a fix for this. Will be in the next update.

kerem commented

2026-03-02 02:16:29 +03:00

Author

Owner

@silversword411 commented on GitHub (Oct 6, 2021):

Closing, as there is no PR to link for auto-closing

@silversword411 commented on GitHub (Oct 6, 2021): Closing, as there is no PR to link for auto-closing

kerem referenced this issue

2026-03-14 03:04:50 +03:00

[GH-ISSUE #453] Feature request: New version alert #2221