I’ve been reading the support documentation of Royal TS, and the Command Line documentation looks to be very Windows oriented.
I wanted to use the same Command Line options on MacOS, but it doesn’t seem to work.
If it’s not supported, will it be in the future?
I’m asking because I can’t seem to be able to use the “URI” properly when it comes to RDP session.
When I use “open” in my Terminal with a quoted “rtsx://…” URI, each time I add a query string, the connection fails without error (it looks like it tries to connect but closes immediately). Without the appended query string (that I use to name my adhoc connection window), it works flawlessly.
I’m running Royal TSX within a bash script with the “open” command.
open -n -F -W "rtsx://rdp%3a%2f%2f$USERNAME%3a$ENCPASSWORD@localhost%3a${LOCALPORT}?property_Name=${SERVER}"
The above command actually doesn’t work. It starts Royal TSX and I can see the RDP url in Royal TSX, but it doesn’t work because the query string is added to the RDP URL (I don’t think that’s supposed to happen, is it?)
If I manually remove the query string in Royal TSX (or if I remove it in my script), it works properly and it connects to my Windows machine.
I followed this manual when I created my bash script:
Does it mean that the query string parameters are not supported at all on macOS for now?
Because even without “property_Name”, and just specifying action, or using, it fails.
Anyway, thank you for moving my threads to ideas, I think it’d be great to at least support the full URI scheme that is available for Windows on macOS.
Unfortunately it’s not currently possible to override those values using ad hoc connections. Since ad hoc connections are based on the default settings for the respective connection type, you could modify your default settings to reflect the configuration you need. Obviously this would apply to all ad hoc connections and any newly created connections.
the default settings located under “Application - Default Settings - Connection Types (i.e. Remote Desktop)” apply to ad hoc connections as well as newly created regular connections.
So any changes you make to those default settings will also apply to ad hoc connections.
While this works like a charm, we are requested to authenticate our S2S VPN connection by going to a URL and entering specific credentials there, to actually make the connection work.
So my idea would have been to
create a new web page connection in Royal TSX where my S2S connection credentials get filled in
Extend the VPN connect script to open the web page connection where the S2S connection gets confirmed
so you would like to open a specific, existing connection in Royal TSX from a script, is that correct?
If so, you can already use AppleScript for that which can also be invoked from shell scripts using the osascript command. See this post on how to invoke it.
