mirror of
https://github.com/amidaware/rmmagent.git
synced 2026-04-26 06:45:48 +03:00
[GH-ISSUE #57] Using custom MeshCentral in TacticalRMM #38
Labels
No labels
bug
bug
enhancement
fixed
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rmmagent#38
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 @fanynek86 on GitHub (Mar 26, 2025).
Original GitHub issue: https://github.com/amidaware/rmmagent/issues/57
Hello everyone!
I have a question for you.
I used my existing MeshCentral, in Tactical RMM.
I have the following problem when deploying the agent:
level=error msg="exec: "C:\Program Files\Mesh Agent\MeshAgent.exe": file does not exist: "
The problem is that my already deployed MeshCetral does not have a native folder name or executable file.
Where can I please modify this verification so that I can define the path?
@fanynek86 commented on GitHub (Mar 26, 2025):
We probably misunderstood each other. The message is there because
MeshAgent.exe is not called MeshAgent.exe, but according to the name I
specified, and the folder is not called MeshAgent, but according to the
name I specified.
Dne st 26. 3. 2025 19:23 uživatel dinger1986 @.***>
napsal:
@dinger1986 commented on GitHub (Mar 26, 2025):
yeah, I reread what you had written and deleted my comment cause it was wrong
@wh1te909 commented on GitHub (Mar 26, 2025):
there is an optional installer flag to specify path to custom mesh agent: https://docs.tacticalrmm.com/install_agent/#optional-installer-args
@dinger1986 commented on GitHub (Mar 26, 2025):
thats what I was going to post before getting side tracked
@fanynek86 commented on GitHub (Mar 27, 2025):
When I wanted to use the existing MeshCentral I used the parameter -local-mesh "C:\Program Files\MYCOMAPNY\MYCOMPANY_agent\MYCOMPANY_agent.exe"
Then I had to enable "allowFraming" on the server with meshcentral. Now I have the problem that when I click on "Take control" in Tactical RMM, only a black window appears.
@fanynek86 commented on GitHub (Mar 28, 2025):
I tried to solve the black screen problem by installing with the "-meshdir" parameter.
However, I can't define the exe file name here. If I define the path and the file name, MeshAgent.exe is still added to the end of the query.
Without define exe file name:
level=error msg="exec: "C:\\Program Files\\MYCOMPANY\\MYCOMPANY_agent\"\\MeshAgent.exe": file does not exist: "
With define exe file name:
level=error msg="exec: "C:\\Program Files\\MYCOMPANY\\MYCOMPANY_agent\\MYCOMPANY_agent.exe\\MeshAgent.exe": file does not exist: "
@fanynek86 commented on GitHub (Apr 4, 2025):
Hello everyone.
I have an interesting problem here.
I connected Tactical rmm to my existing MeshCentral. The connection works, but Tactical-RMM is generating the link incorrectly. There is a faulty link to the node. Once I change the gotonode to the correct one and leave the rest of the link, everything works as it should.
Can you please advise me how to fix this so that Tactical RMM generates the correct link to the node?
Is it possible that this is caused by an installation problem during this verification?
@fanynek86 commented on GitHub (Apr 7, 2025):
Hello everyone.
I solved this problem via simlink.
Could you please correct the path so that it defines the actual MeshAgent name?