tacticalrmm
tacticalrmm copied to clipboard
Microsoft RDP
Is there anyway to include an option to remote in via MS-RDP? through the mesh central router? I may be overlooking something here.
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
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.
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.
What about the "Web-RDP" from mesh? Could that be exposed in tactical?
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 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.
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