Additional variation (old behaviour) for Launch at startup: Last opened connections

Hello,

Thank you for contacting us on that matter!

I have to be completely honest, I'm not quite certain I understand the difference between the old and new behavior from the way you describe them. I apologize for asking, but could you please reiterate what behavior is, according to you, lacking or malfunctioning?

Best regards,

Hi Gabriel,

sorry for writing too messy, and probaby too much around it ;-)

I found a change in behaviour regarding "Open last opened connections" some versions ago. At first I thought it was a bug and waited for some updates and because there was no change back I started investigating.

I have the following settings configured for a long time now:

• "Options > Types > Keep tab page opened on disconnect: Yes"
• RDP Session Properties > Display: Embedded (tabbed)

I do not

• remember to configure something for the "Open last sessions" when starting RDM, so I guess it was a default setting
• know if the "Edit > Play List > Play List Management > Launch at startup: Last opened connections" option exists since a long time, or if this was implemented during the last updates and resulted in the changed behaviour, but I did not make a change here, therefore it was configured to "Open last sessions"

The different behaviours

• I have open embedded/tabbed sessions (connected ones or disconnected ones) when closing RDM
  • No change in behaviour
    • => When starting RDM again it lists those sessions and asks if I want to open them again

• I have all sessions closed (no tabs anymore, but had some open during RDM runtime)
  • Old behaviour
    • => RDM starts clean/empty without showing me a list, because I left RDM clenaed up when closing
  • New behaviour
    • => When starting RDM again it lists the sessions I had opened (and closed) during the last RDM runtime and asks if I want to open them again

For me this new behaviour is impractical, in my workflow/for my mindset.
I loved the feature with the old behaviour, because I was able to restart my computer/RDM or continue the next day without loosing the currently opened sessions I had to continue my unfinished tasks.
When my work is done in sessions and closed them, they were gone (out of my mind) - but when no session is left when closing RDM, it shows all those "finished" sessions again and I ask myself again and again: "Was I done, or was there something left to do on this server?" :-)

So I know this is not done by accident, and I guess a lot of users like this new behaviour. So I am asking for some workaround or additional option to chosse from.

Again a lot of text, but I hope it is clearer now!? Continue asking if not :-)

Have a great day!

Greetings
Lucas

Hello,

Thank you for the clarification! I was able to replicate the behavior you described. I have opened a ticket to our engineering team to see if it would be possible to implement an option that allows the "Last Opened Connections" playlist option to only include the tabs that were still open when RDM was closed.

We will let you know when progress is made on the case. In the meantime, if you have any additional questions on the subject, don't hesitate to let us know!

Best regards,

Hello again,

thanks a lot for your help!
Your product but also your great and fast support and responsiveness to the community made us buying the Enterprise version since several years, even if we (team of 3) use it locally and only a small portion of the immense functionalities.

The more I think about it, the less I understand the current behavior and why somebody would like it this way :-)
Why would somebody close all sessions completely (and not use the function "Keep tabs open after disconnect") in the first place and want them back again when starting RDM next time!?
As soon as one session/tab is open when closing, all of those closed sessions will not be in the list... so you have to have a very specific situation as well.
So maybe it IS some kind of bug!? Like you wanted to improve the old behavior and give the users more options, like opening a Play List when starting RDM. And to keep the old behavior you created the automatic Play List option "Last opened connections". This is automatically filled with the current sessions to have the list available after the restart. And this list is not cleaned up or synchronized 100% when RDM is closed!?

So maybe you can check my thoughts as well and have an explanation or usecase for the current behaviour - maybe I can learn or improve my workflow :-)

Thanks again and have a great afternoon.

Greetings from Germany
Lucas

Hello,

Although I have previously been able to replicate the behavior you describe, I don't seem to be able to trigger it anymore, and neither can my colleagues in engineering. This most likely means that the behavior is caused by specific actions or configurations. This inconsistency seems to indicate that the new behavior might indeed be accidental.

In order to help us replicate the behavior again, could you please provide us a video recording of it? This would greatly help us replicate the issue internally, and in turn locate the cause it's cause. You can use our safe ShareFile link below to send us the video :
https://api.devolutions.net/redirection/96436835-ca81-4cf4-9daa-47417c226684

Best regards,

Hi,

I reproduced the problem and uploaded the video from it to the provided link.
I use RDM in portable mode, so for the test I downloaded the latest version and created a separate instance of RDM portable
=> Everything was new and default, beside the one setting I changed (Keep tab open after disconnect).
I forgot to mention, that I am on Windows 10 Pro v1909.

I hope the annotations in the video make clear which was which scenario and you can see the "wrong" behaviour.
If you have further questions feel free to ask, I will try to help.

Greetings
Lucas

Hello,

Thank you for sending us the video! I will provide them to our engineering team and keep testing. We will let you know when new development is made on the case.

Best regards,

Hello Lucas,

We have completed a fix for this issue and the changes should be available starting from the next major release of RDM.

Best regards,

Hi Michael,

that's great news - it's not a big problem, but it really annoyed me to be honest :-)
I appreciate your great work and support on this product!

Have a great day.

Greetings
Lucas