RDP connect until success

hilmar_laxdal · December 6, 2018, 1:54pm

I fixed the reconnect part with having a Disconnect Task which has a timeout and then reconnects with

Command ## C:\Windows\System32\cmd.exe

Arguments ## “/c Timeout /T 30 && RoyalTS.exe /action:connect /donotactivate /protocol:rdp /using:uri /uri:$URI$”

Working Dir ## C:\Program Files (x86)\code4ward.net\Royal TS V4

norman · January 4, 2019, 8:11am

1. if a user disconnects a session from within the session it will not be considered as a failure and the automatic reconnect checkbox will be unchecked in this case (in fact, only disconnect reasons > 3 will result in checking the option)

The reconnect feature works better for me in Beta Builds before these changes.

Can u please give us an Option to enable Auto-check-reconnect also for Exit Codes < 2

(Maybe a Checkbox in RDP Connection)

tom_scott · January 4, 2019, 1:56pm

I would like the reconnect option for when I manually reboot servers.. I have version 5 of RoyalTS and have enabled the “Auto Reconnect on Disconnected Tab” option but when I manually reboot servers that check box isn’t checked.

Thanks

stefan_koell · January 5, 2019, 10:23am

Thanks for the feedback. The next release will have a plugin option to always enable autoreconnect by default for those cases. Stay tuned…

aleksandr_sukhorukov · July 30, 2019, 6:31am

When i try to connect to the server which is offline now there is no reconnect function ? Why? This could be the same timeout checkbox, let the royal ts try again and again until success?

stefan_koell · July 30, 2019, 7:43am

Hi,

it is correct. The auto reconnect as of today needs at least one successful connection before this feature kicks in. This feature is intended to automatically reconnect in case it gets remotely disconnected. Having the auto reconnect enabled from the beginning is problematic because in case you have typo in the host name or so, you may not really know if you have a typo or if the host is down.

Regards,

Stefan

aleksandr_sukhorukov · July 30, 2019, 7:54am

What the difference if this a typo o host is down ? This is unsuccessful connection in both cases))

But if you are sure, if the connection is not new - this function could be helpfull

stefan_koell · July 30, 2019, 8:00am

The difference, especially for new and unexperienced users is the following:

Imagine you setup a connection with a wrong host name. Then you connect to it and you immediately get the auto reconnect screen as the host is not available because you entered the wrong one. The user may wait for a while until he investigates and possibly wastes a lot of time until he realizes that there’s the wrong host configured. The user can easily get frustrated as the auto reconnect screen may imply that the host is just down and might be up soon.

If you want to have this also for the initial connection, I kindly ask you to file a new feature request to see how many users really want/need to have that. Then we can look into it and see how we can make this clear from a UX perspective that the frustration mentioned above can be avoided.

Regards,
Stefan

aleksandr_sukhorukov · July 30, 2019, 8:51am

If this is a new connection no matter what error you get. It;s a sign to recheck the settings))

I think so, will fill the request.

stefan_koell · July 30, 2019, 9:51am

Thanks for the feature request.