mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #2191] Add --nomesh checkbox to Agent Deploy #3302
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#3302
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 @southeasterntech on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2191
Is your feature request related to a problem? Please describe.
Having to manually edit the config file to include --nomesh for those of us who have an independent mesh server is quite cumbersome at scale. An option to download an agent with --nomesh would be very favorable.
Describe the solution you'd like
On the install agent config screen, a checkbox that says No Mesh, next to Enable RDP and Enable Ping seems logical.
Describe alternatives you've considered
Since the folks that have their own separate mesh server (we've used mesh for 5+ years before adopting tactical), will always select the "--nomesh" check box for deployment of an EXE, a global option would be best. If you select somewhere else in settings that you have an independent mesh server, then Agents should always be deployed with the "--nomesh" variable.
Additional context
Having to manually edit a script each time do do a new deployment is less than ideal.
@Kf637 commented on GitHub (Apr 8, 2025):
I need that, because due to laws, I'm not allowed to install Tactical on some computers due to Mesh, even if I uninstall Mesh.
@Kf637 commented on GitHub (Apr 10, 2025):
I've looked in the source code and seems pretty easy to implement, not sure why it's not already implemented.
@P6g9YHK6 commented on GitHub (Apr 10, 2025):
if that easy do a PR :3
and there is not an army of dev working on the mass of feature request coming in
@silversword411 commented on GitHub (Apr 10, 2025):
What law?
@P6g9YHK6 commented on GitHub (Apr 10, 2025):
we have the same here. not allowed to install mesh on laptops.
you are not allowed to have anything that could be used to spy on employees.
as an employer you do not have the right to have the possibility of snooping on what people do.
this goes as far as not having the right to have delegated rights on mailboxes.
CCTV is a no no if there is no shoplifting risks
https://www.espacedroit.ch/articles/surveillance-des-travailleurs/
imo a better implementation on mesh side of the request to take control would probably fix this but currently would not be possible.
welcome to the realm where workplace protections are a thing.
@Kf637 commented on GitHub (Apr 10, 2025):
We are not allowed to install anything that can be used to spy and remotely control a machine, we have strict laws.
@southeasterntech commented on GitHub (Aug 22, 2025):
BUMP (Any updates to this?)
This has come up again.
can we get a checkbox for agent deployment to add the --nomesh option? that would be huge? @Silversword (edited)
This is important because we have an external mesh server on AWS already with 1200 endpoints... but we have to do this manual edit for every TRMM script agent deploy. If this could be triggered for Win\Linux that would make life much easier.