mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1171] Policies marked as linux applying to windows when they're checks #2665
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#2665
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 @Vedeneb on GitHub (Jun 14, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1171
Originally assigned to: @sadnub on GitHub.
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
When a policy is marked as linux (for example a script is used where the platform is set to Linux) it still get's executed on windows agents as well.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The script-check should be executed on all linux agents, but not on windows agents
Screenshots




If applicable, add screenshots to help explain your problem.
Additional context
This was discussed with and confirmed by @silversword411 on discord
@sadnub commented on GitHub (Aug 14, 2022):
Can you browse to the summary tab for this agent and see what the platform text is? I'm not able to replicate this.
@Vedeneb commented on GitHub (Aug 14, 2022):
Has this possibly been addressed already? Just tried it again and could not reproduce it myself (now running TRMM version
0.14.6and agent version2.3.0).Maybe @silversword411 could try if it's still reproducible for him? Otherwise I think the issue can be closed.
@sadnub commented on GitHub (Aug 14, 2022):
I actually patched up a couple issues that could make this happen intermittently. It will be in the next release. Thanks!