ASG-2017 - Dont close sessions on disconnect

[burtzz]

Hi,

Im trying to find a way to keep RDP Tabs opened even when the session is disconnected.

I want a way of not loosing track of disconnected or timeout sessions.

Example:
When I come back from an hibernate (with ASG left opened at the time), or even after a network change, all opened sessions disapear.
This is not very pratical. You loose track of what you were doing.


ty

[Michael Scholz]

Hi,

We have settings to save disconnected sessions. If I have a disconnected session I get a popup message trying to automatically reconnect to the session. If activated ASG-RD saves the actual sessions while closing the application and restores them on next restart automatically or with a popup-box asking to restore. Have you tried those settings ?



best regards,
Michael

[burtzz]

Hi,

Yea, its activated but it doesn't work sometimes.
Anyway, that's when you close ASG.

How about when you have the program running?
Imagine the following, Im working on 10 RDS sessions, for some reason 1 or 2 are disconnected. That particular TAB(s) automatically disappears/closes. How can I avoid this?
I keep loosing track on where I was connected and what I was doing because of this.


Ty

[Michael Scholz]

Which version do you actually use ?
If I have a session disconnect ( for example Lan interruption ) a popup will be displayed that ASG-RD tries to reconnect.
regards,
Michael

[burtzz]

Which version do you actually use ?
If I have a session disconnect ( for example Lan interruption ) a popup will be displayed that ASG-RD tries to reconnect.
regards,
Michael

Hi Michael,

Version 10.0.5564.0

I don't get any popup or reconnect.

Another good example:
I've hibernated my machine yesterday's afternoon with 7 opened sessions.
This morning, when resuming my machine there were only 5 sessions in ASG. After a few minutes another tab closed (unknown reason, probably disconnect/timeout) and I was with 4 sessions.
Right as I write this text, more 2 sessions tabs gone without any warning or reconnect.
I'm now with only 2.


I have a colleague with the same issue.

[Michael Scholz]

Hi again,

hmm...not easy to say whats happening, but are these sessions always the same sessions or rather servers ? Because it's important how the servers are configured regarding session handling. It's possible that the server closes disconnected sessions or timed-out sessions. That should be checked. Maybe you can test such a problematic session with the microsoft rdp client. Hybernate your machine with mstsc.exe open and an active session to see if there is the same behaviour.
However maybe our feature "Layouts" helps a lot !? Have you tried that ? For example if you have 10 important sessions then you can save those sessions in a "layout". So you can open the layout bar at the right side with "Control-U" , right click on "Layouts" - "new" -> "layout". Then again choose "layout" and click on "capture". Thats it. To open the layout simply Start the Bar with "Ctrl-U" and doubelclick the saved layout.
Hope that helps ;-)

Best regards,
Michael

[burtzz]

Hi again,

hmm...not easy to say whats happening, but are these sessions always the same sessions or rather servers ?  Because it's important how the servers are configured regarding session handling. It's possible that the server closes disconnected sessions or timed-out sessions.  That should be checked. Maybe you can test such a problematic session with the microsoft rdp client. Hybernate your machine with mstsc.exe open and an active session to see if there is the same behaviour.
However maybe our feature "Layouts" helps a lot !?  Have you tried that ?  For example if you have 10 important sessions then you can save those sessions in a "layout". So you can open the layout bar at the right side with "Control-U" , right click on "Layouts" - "new" -> "layout". Then again choose "layout" and click on "capture". Thats it. To open the layout simply Start the Bar with "Ctrl-U" and doubelclick the saved layout.  
Hope that helps ;-)

Best regards,
Michael

Servers may be configured to close disconnected sessions. Or even another user disconnects my session.
But that isn't the point. 

I just want the possibility of having this sessions tabs kept opened even after a disconnect, for whatever the disconnect reason is.

I've used another RDP software like RDP conection manager and RoyalTS and it was possible.
We moved to you guys because we saw some clear advantages but this simple and basic feature needs to be incorporated, if there isn't a way already.

I can give an example in RoyalTS:
I still have a tab opened there from a disconnected server session that happened days ago. Its a blank/empty tab because I'm not actually connected to it of course, but at least I know I was working on it because the tab exists. And the tab only closes if I sign out from the machine or click on the tab and choose close.

[Michael Scholz]

Hi again,

thanks for your opinions ! we will think over it and I will discuss this with development soon ! But have you checked the "LAYOUT" feature that I described in my last response ?
This will have all open sessions saved. You just have to do it before closing or suspending your session.

best regards,
Michael

[burtzz]

Yea, I've tried.
Its a workaround, I can do that everyday before hibernating the machine as a precaution.
But is not really what is needed here and requires a manual action every single day.

And its not a solution for disconnected sessions while the application is opened.

But ty for the sugestion

[Michael Scholz]

Your welcome ;-)

I will discuss this behaviour with development soon. But regarding the disconnects and closed tabs: I can only reproduce the automatic closing of a tab if a disconnect is forced from the server side or the target system your are connected to. If a network interrruption occurs the tab stays open here.

Have a good weekend,
Michael

[DevOma]

Automatic reconnect can be configured in Settings=>Connections - but we could add also an option for a button inside the session tab that allows to reconnect the session... we will add it for the next version

[drlandau]

Hi, so I have enabled "Reconnect sessions in same window/tab" and "Retry Button" (and attempts 10 / timeout 5 even though these are probably not needed when not using automatically), "Return codes" is blank.

If I restart a server, the tab closes. Is this intended or do it not work? We are on 10.1.5630.1, not the lastest Update yet.

BR,
Nicolaj

[DevOma]

Yes you are right - restart of a server do not hold the tab - we should extend the function to restart

[drlandau]

Actually when set to popup and I changed the network in VMWare and the RDP connection dropped I was prompted, but not when I restart it "clean" - so is it something about the returncode the servers sends back to the RDP client that determined if it is a "dirty" disconnect (and try reconnect) or it is a "clean" disconnect and it doesnt try to reconnect?

It would be sweet if you could consider adding an option to allow reconnects for "clean" disconnects

[DevOma]

Already added to my task list...

[drlandau]

Way ahead of me, sounds great :-)

[MiniP]

Has this been fixed? If so, which version.

[DevOma]

It should be checked if you choose the restart option from ASGRD - but not if you choose inside the OS