mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #36] Checks from policy not automatically applying #7
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#7
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 @Omnicef on GitHub (Aug 12, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/36
Originally assigned to: @wh1te909, @sadnub on GitHub.
I have some checks set up as a policy and have the policy applied. However they do not show up until I create a check manually and then delete the check from a device. Then the policy checks show up for only that device.
@wh1te909 commented on GitHub (Aug 12, 2020):
this is a known bug see the discussion in https://github.com/wh1te909/tacticalrmm/issues/6
@wh1te909 commented on GitHub (Aug 12, 2020):
gonna re-open this for visibility and tracking
@sadnub commented on GitHub (Aug 15, 2020):
@Omnicef Can you see if your issue is resolved with the latest updates?
@Omnicef commented on GitHub (Aug 16, 2020):
It is working now!
@Omnicef commented on GitHub (Aug 23, 2020):
After the latest update... I am now experiencing this issue again.
@sadnub commented on GitHub (Aug 25, 2020):
@Omnicef I am doing some rework on the policy checks and we look at this. Thanks for testing!
@sadnub commented on GitHub (Aug 26, 2020):
@Omnicef I think this is due to policies not applying to newly installed agents. I will make a fix shortly.
@sadnub commented on GitHub (Aug 26, 2020):
#78 Should fix this issue. Once it is merged, let me know if you have any issues. Thanks!