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 just tested this with the exact same parameters you provided and was able to successfully connect through an RDS gateway to my target RDP host.
The best way to find out what might be going wrong is to drag the ad hoc connection once it's created to one of your existing documents. Then, you can inspect it's properties and check if everything's configured as you would expect.
Hope that helps!
I've given the beta of Royal TS X V6 a whirl and I've tried using a link in the same format as described above:
How is this progressing in terms of beta/release?
I can't yet comment on the actual release date but we'll have a public beta ready in the next couple of weeks.
the query string syntax for overriding connection properties in ad hoc connections will be supported in the next major version of Royal TSX (V6).
Hope that helps!
We have an online portal that manages access to hundreds of VMs, and it provides access by customising an rtsx link using the below format:
To join in on this. We have a platform where we are managing many multiple Virtual machines with an rtsx URL generated automatically based on the parameters clicked on via the website access portal.
These links follow the general format:
These links work perfectly fine in Royal TS for Windows so was expecting them to work on the Mac version so I'm quite surprised that the functionality is not equally matched as a minimum.
Can this please be looked into?
@Pascal: Perfect, glad I could help!
Yes, that will absolutely work… Thank you!
Best regards, Pascal
Thanks for the quick reply.
You may have seen this post: https://support.royalapps.com/support/discussions/topics/17000021725?page=1
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
Could you please describe your use case so that we know exactly what's missing from your point of view?
Any news on this?