0 vote
Hi,
I would like to request support for opening Rustdesk sessions.
There is already an add-on for RDM Windows.
Thank you,
https://forum.devolutions.net/#authz_code=Ttfb2hbTX238&state=1bbeae825b088cba9dec3d821b729e96a1zD9ENx1&authn_code=BBbpP6Tl0UylGKLX&code=xnTqtZ21g6AyWttL
Hi ZeekWorld,
In RDM Windows they seems to be using command line (in the form of <executable> --connect <id>). Do you know if such a method also works for their macOS client? And if not, can you confirm?
Best regards,
Xavier Fortin
Not working for me on RDM mac.
Hello
Their CLI doesn't seem to be documented, but to launch a .app on macOS with arguments it's normally necessary to invoke the binary inside the bundle. So, an example would be (assuming you installed RustDesk.app into your "Applications" folder):
/Applications/RustDesk.app/Contents/MacOS/rustdesk --connect 123
(Where "123" is the ID you want to connect to)
It looks like they also support a --password argument too.
Thanks and kind regards,
Richard Markievicz
Hi!
I am running Version 2024.1.7.2 (April 10, 2024) and it seems that /Applications/RustDesk.app/Contents/MacOS/rustdesk --connect 123 does not work.
Running this command from macos terminal works though.
Any ideas?
Hello
I did reproduce the problem; I'm checking with the RDM Mac team if there's something to be fixed or maybe we are using this feature in the wrong way. Sorry for the inconvenience and thank you for your patience!
Kind regards,
Richard Markievicz
Hello again
Ok - this is not rustdesk specific, but rather an issue with the command-line script session in RDM Mac 2024.1.x. I tried to find a workaround using AppleScript but it doesn't seem possible right now. A bug ticket has been opened and linked to this thread, and we'll post back once a fix is available.
Thanks for your patience and please don't hesitate with other questions or comments in the meantime.
Kind regards,
Richard Markievicz