Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
+++Reconnect session in the same tab NOT WORKING
#21
Ok, DevOma, here is the information you wanted

in the RD-Gateway settings,
Default Values tab==>Do not use RD Gateway server (checked)
Inherited Values tab==>Use these RD Gateway server settings (checked) 
                                        Servername:  <our terminal server name, note it is just named like a terminal server not sure if that matters>
                                        Logon method:  Automatic (greyed out) 
                                        Bypass RD Gateway server for local addresses  (not checked)
                                        Credential: <our credential to connect to terminal server>
                                        Use connection credential (not checked)

With this current settings, except the annoying issue of jumping the tab to the furthest right (often hidden due to the limit space on tab header line), the RDP session to the server will be automatically reconnected without any input after I hit the Reconnect button. 
But if the "Reconnect session in the same window/tab" checked in the ASG setting, the tab stays but it will ask for username and password to gateway server as if it completely ignores the settings in RD-Gateway.  

Hope this information helps.  

Please fix this annoying bug as it happens to many of us who are using ASG2020 and 2021.  I am thinking, even if you somehow can't reproduce it from your side, you should be able to do some fixing logically in your code.  There must be somewhere in your code says to completely ignore RD-Gateway setting with "Reconnect session in the same window/tab" checked but don't ignore it when the tab is not checked.  Please fix the code logic.  Thanks.
Reply
#22
Just your settings in RDP=>Remote Gateway of a used connection - want to be sure we are using the same way of configuration...
Regards/Gruss
Oliver
Reply
#23
Is this a statement of yours or a question to me? I don't understand what you are saying.
Reply
#24
Goto one of your connections that is causing the "cred prompt" when reconnecting and tell me what you have configured in RDP=>RD Gateway - which options do you use?!?
Regards/Gruss
Oliver
Reply
#25
Dude, didn't I already provide the detailed information above on RD-Gateway settings or not?!!!  That IS the setting which causes re-prompt for username and password.   What more do you need?
Reply
#26
Yes dude - you posted twice and I didn't read the second post :-) My fault!
Regards/Gruss
Oliver
Reply
#27
Hi DevOma, just to clarify my wish/request. Not only I wish the tab stays and not ask for UN/PW when the tab/connection is timed out due to idle but also I wish the tab stays and not ask for UN/PW when we need to reboot the tab/server.

Not sure if you guys do this in your company, many of us are doing something called PnB (Patch and Reboot) on tens of servers a day, ie the tab/server will be reboot (in order) AND we don't want the tab to disappear and we want it to stay at the same location at the tab header line. We need to have all the tabs/servers at a strict order, ie we need to line all the ducks in a roll with a particular order and we don't want the tab to disappear or jump around no matter of what (time out or reboot), unless we explicitly want to close the tab. Thanks.
Reply
#28
when we set the tab to "stay", it needs to really stay at the same spot on the tab header line no matter time out or reboot, unless we explicitly hit close sign on the tab. This is crucial for our daily operation. I am sure thousands of your customers out there are doing the similar thing and have similar issue. Thanks.
Reply
#29
Yes of course it should stay - and it does - the reconnect will be done within the DockControl - so nothing is changing - I will try to reproduce your issue again
Regards/Gruss
Oliver
Reply
#30
Able to reproduce it or not, the issue is there for many of us. Please fix it in the code and add more logics to deal with this. Thanks.
Reply
#31
Please make the tab don't jump around or close by itself not matter of time out or reboot, if the user chooses to set so.  Tab should stay at the exact spot and in the same original order no matter what unless the user explicitly hit x on the tab header.  At least that should be an option to user.  This will be a huge user experience improvement for people who need to deal with a lot of servers at one time.  Thanks.
Reply
#32
We found and fixed the issue - will be part of the next release!
Regards/Gruss
Oliver
Reply
#33
Great news, I hope it comes out soon. Is it end of march?
Reply
#34
DevOma, can I ask you for another feature request?  Big Grin Can you please make the active tab head appears bigger in size and with bold border  than other tabs or use more differential method (such as only the active tab head has color while other inactive tab heads are plain)?  The point is that the current color scheme in which every tab head  has very similar/close color makes our eyes blind and very hard to find the active tab.  All those fancy useless stuff which decreases the work productivity should be avoided and got rid of.  Cool  I am just providing you the user experience feedback and I understand you guys may have different opinion.   Thanks.
Reply
#35
We are in final testing of Release 2022 - try to publish the release very soon :-)

The color scheme of inactive tabs is now a little different to active tabs - gradient style changed - font is bold - if it will not fit your needs, we will try to make for differences
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)