starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 06:55:52 +03:00

[GH-ISSUE #213] Microsoft RDP #2075

New issue

Open

opened 2026-03-14 02:22:17 +03:00 by kerem · 7 comments

kerem commented

2026-03-14 02:22:17 +03:00

Owner

Originally created by @JerresonJ on GitHub (Dec 17, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/213

Is there anyway to include an option to remote in via MS-RDP? through the mesh central router?
I may be overlooking something here.

Originally created by @JerresonJ on GitHub (Dec 17, 2020). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/213 Is there anyway to include an option to remote in via MS-RDP? through the mesh central router? I may be overlooking something here.

kerem added the

enhancement

requires agent update

integration

labels

2026-03-14 02:22:17 +03:00

kerem commented

2026-03-14 02:22:28 +03:00

Author

Owner

@wh1te909 commented on GitHub (Dec 17, 2020):

meshcentral runs completely separate than tacticalrmm, i just integrate with it for take control, terminal and file browser wrapped in an iframe in the tactical UI
you can just login to mesh.yourdomain.com and download the mesh router and use it as if tacticalrmm was not installed

@wh1te909 commented on GitHub (Dec 17, 2020): meshcentral runs completely separate than tacticalrmm, i just integrate with it for take control, terminal and file browser wrapped in an iframe in the tactical UI you can just login to mesh.yourdomain.com and download the mesh router and use it as if tacticalrmm was not installed

kerem commented

2026-03-14 02:22:33 +03:00

Author

Owner

@JerresonJ commented on GitHub (Dec 17, 2020):

Yea, I was kind of piecing that together here. I'm picking things apart to see how everything is tied together. I've never used MeshCentral before.

Ideally, I would like to be able to click RDP in RMM and have it automatically open MS-RDP and connect through to the endpoint.

@JerresonJ commented on GitHub (Dec 17, 2020): Yea, I was kind of piecing that together here. I'm picking things apart to see how everything is tied together. I've never used MeshCentral before. Ideally, I would like to be able to click RDP in RMM and have it automatically open MS-RDP and connect through to the endpoint.

kerem commented

2026-03-14 02:22:38 +03:00

Author

Owner

@JerresonJ commented on GitHub (Dec 17, 2020):

How difficult would it be to add an RDP button to RMM that follows the same suit as the RDP link in MeshCentral?
So you can click "RDP"
Which opens MeshRouter and starts the connection.

@JerresonJ commented on GitHub (Dec 17, 2020): How difficult would it be to add an RDP button to RMM that follows the same suit as the RDP link in MeshCentral? So you can click "RDP" Which opens MeshRouter and starts the connection.

kerem commented

2026-03-14 02:22:43 +03:00

Author

Owner

@bbrendon commented on GitHub (Jan 3, 2021):

What about the "Web-RDP" from mesh? Could that be exposed in tactical?

@bbrendon commented on GitHub (Jan 3, 2021): What about the "Web-RDP" from mesh? Could that be exposed in tactical?

kerem commented

2026-03-14 02:22:48 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jan 4, 2021):

i used to have the meshcentral web-rdp in the agent's context menu in tactical, but removed it cuz its not that stable plus it requires you to uncheck the "allow connections only from computers running RDP with NLA" on each computer.

i do plan on adding RDP through a reverse proxy built directly into the tactical agent, for now i'll see if it's possible to integrate with meshrouter

@wh1te909 commented on GitHub (Jan 4, 2021): i used to have the meshcentral web-rdp in the agent's context menu in tactical, but removed it cuz its not that stable plus it requires you to uncheck the "allow connections only from computers running RDP with NLA" on each computer. i do plan on adding RDP through a reverse proxy built directly into the tactical agent, for now i'll see if it's possible to integrate with meshrouter

kerem commented

2026-03-14 02:22:53 +03:00

Author

Owner

@azulskyknight commented on GitHub (Jan 5, 2021):

@wh1te909 I do not think that's an issue any longer.

I was playing with Mesh Router, and the Web-RDP link and neither of them required me to disable that box.

Web-RDP won't work to any of my stuff internally because it apparently doesn't support NAT loop back...

And while it worked for me to a remote location, it isn't working for one of my users at that location that has a mesh login. So the instability is certainly still there.

Mesh Router on the other hand is so powerful it's a bit scary.

@azulskyknight commented on GitHub (Jan 5, 2021): @wh1te909 I do not think that's an issue any longer. I was playing with Mesh Router, and the Web-RDP link and neither of them required me to disable that box. Web-RDP won't work to any of my stuff internally because it apparently doesn't support NAT loop back... And while it worked for me to a remote location, it isn't working for one of my users at that location that has a mesh login. So the instability is certainly still there. Mesh Router on the other hand is so powerful it's a bit scary.

kerem commented

2026-03-14 02:22:58 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Mar 9, 2024):

I have solved this on my side with the following:
1 a collector tasks that create a custom variable that contain "ip:port" it also can be manualy edited in case the script got it wrong or the ip is natted.
2 a url action with the following: rdp://{{agent.RDP IP}}
3 https://github.com/richard-green/MstscLauncher
4 enjoy

@P6g9YHK6 commented on GitHub (Mar 9, 2024): I have solved this on my side with the following: 1 a collector tasks that create a custom variable that contain "ip:port" it also can be manualy edited in case the script got it wrong or the ip is natted. 2 a url action with the following: rdp://{{agent.RDP IP}} 3 https://github.com/richard-green/MstscLauncher 4 enjoy

kerem referenced this issue

2026-03-14 06:55:32 +03:00

[GH-ISSUE #2075] Usage Monitoring Endpoint via Docker / MON_TOKEN via (docker-) environment variable #3233