RDP connect until success

bubihead_jk · February 16, 2017, 1:37pm

I want to connect to a RDP connection until it is successful (e.g. server restart). There is currently no way to do this (support says). So I want to do a feature request for a future version of RoyalTS.

Thanks

Matthias

adrian_martin · March 3, 2017, 2:57pm

This feature is available in competitors’ software (Devolutions RDM). Simple feature.

adrian_martin · March 6, 2017, 3:12pm

Any input from RoyalTS team?

stefan_koell · March 7, 2017, 9:40am

Hi,

thank you for the feedback and the feature request. This feature is already on our todo list but we cannot really tell when it will be available. As trivial this may seem, it’s quite some work to make this a robust feature. But while we are here already, maybe you can help me to find the best way to implement that in Royal TS. Right now we are planning the following:

Connect: when a connection attempt fails, a message box is shown and allows the user to tell Royal TS that it should quietly continue to connect in the background until the connection is up and running or until the user manually closes the tab.
Remote disconnect: when a connection is remotely disconnected, you can already configure Royal TS to keep the tab open. If that’s the case, we can let Royal TS try to reconnect in the background until the connection is up again.

Would the above reflect the desired behavior?

Regards,
Stefan

bubihead · March 7, 2017, 9:48am

Hi Stefan,

The ideas sounds great to me.

Thanks & regards

Matthias

adrian_martin · March 7, 2017, 4:00pm

Stefan,

Here’s the scenario that I typically face this problem in.

I’m rebooting a machine and the connection is closed to the remote (windows server) PC. That’s fine. However, now I’d like to have the option to “connect when the machine comes back online.” I’m assuming this is done by continuous ping and that once the machine responds, an attempt is made to then RDP back in.

Either of your two scenarios works as well. I’d say, take a look at Devolutions RDM to see their implementation. Its simple and stays in the background. Its integrated with their command tasks. A small window pops up and shows a few lines about the host being online (tested by constant ping) and if it can remote in. You can see a spinning/loading icon where it is attempting to connect.

Hope this helps!

jarel_walker · April 27, 2017, 3:15pm

I would like to request this feature as well.
I am often doing server maint that requires a reboot. If RTS could automatically reconnect that would be great. I already have RTS configured to keep the tab open when closing a connection, if there was a checkbox on the disconnected tab to auto reconnect when accessible again that would be awesome.

I wouldn’t want every VM to auto reconnect all the time though. If I log off because I am done with a VM for the time being I don’t want it to just pop back up indefinitely until I close the tab (I try to log out of servers rather than leave disconnected sessions on servers).

stefan_koell · April 27, 2017, 3:31pm

Thank you for the additional information, Jarel. This is very helpful!

raffaele_vigliotti · February 27, 2018, 9:38am

+1 on this feature, is there any ETA?

stefan_koell · February 27, 2018, 2:59pm

Thanks for your vote, Raffaele. There’s still no ETA but we hope to have that in V5…

Regards,
Stefan

tom_scott · March 11, 2018, 1:28am

Just wondering if this has been implemented yet..

Thanks

stefan_koell · March 12, 2018, 10:36am

Hi Tom,

it hasn’t been implemented yet but it’s still on our roadmap for V5. Stay tuned!

Regards,

Stefan

norman · October 2, 2018, 7:41am

Hi, any Updates about this Feature?

Its something i missing most and would be really, really Helpfull in my Workflows.

Greetings,

Norman

bmccleary · October 2, 2018, 9:27pm

I would really appreciate this feature as well. My scenario is that our office VPN will automatically drop a connection after 8 hours. I’ll have 5-10 RoyalTS RDP windows open, and when the VPN drops, even though I can reconnect within 60 seconds, RoyalTS goes through it’s “Attempting Reconnect 1 of 3” and goes through those three attempts in less than 10 seconds. Therefore, after reconnecting to the VPN, I have to re-establish my sessions to the the servers, and even though that only takes a minute or two, it’s irritating to do that every single day. If we could simply have it wait 30 seconds between each re-connection attempt (as opposed to the 5 seconds currently set for that), or have it attempt to reconnect perhaps 10 times instead of 3, that would solve my issue.

darrell_swafford · October 3, 2018, 1:40pm

If we could have it configurable instead of set number that would be better. 2 fields Number of retries or infinit. And delay before retrys.

stefan_koell · October 3, 2018, 1:54pm

Thanks for the feedback! Would that be a plugin level setting or a connection specific setting?

darrell_swafford · October 3, 2018, 1:56pm

Not sure at the moment.

Thinking a Global Plugin level option and a connection specific option.

Connection specific would override plugin/global.

stefan_koell · October 3, 2018, 2:22pm

Well, this is the combination which requires a lot of work and I guess in most cases a general setting will suffice. I will try to get a plugin setting into the next V5 beta release and see how it goes from there…

stefan_koell · October 9, 2018, 6:39pm

I just released the beta with the first iteration of this feature. It’s much harder to implement that I thought. The automatic reconnect should happen in the background and not grab the focus of the connection once it is successful. At the moment, RDP is the only connection which supports the new auto reconnect feature and you also need to configure Royal TS to keep remotely disconnected tabs open to make it work (you can find this setting under View -> Options -> Behavior). When a connection is disconnected remotely, the tab will change to the “disconnected” state and at the very bottom you will see a checkbox (by default checked) which counts down (currently 30 seconds) and tries to reconnect every 30 seconds. You can uncheck this box to stop automatic reconnect (check it again to enable it) und you can also hit Connect at any time to manually try to connect.

The new beta can be found here:

https://www.royalapplications.com/ts/win/features-beta

Should you experience any issues, let me know.

stefan_koell · October 22, 2018, 1:30pm

A couple of users complained about that feature interfering with certain “disconnect” reasons. As a result I tweaked the feature in two areas:

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 “new” automatic reconnect feature will be turned off by default and can be enabled for all RDP connections in the plugin settings for Remote Desktop. I feel I need more feedback which disconnect reason codes should be considered to automatically enable the reconnect option and which ones are better to ignore.

The next beta with the above tweaks will be available shortly…