Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ASG-RD-2019 Patch2 (2.0.6279.1)
#1
Currently running ASG-Remote Desktop v 11.0.5988.1 (SQL database) and investigating updating to ASG-RD-2019 Patch2 (2.0.6279.1).
Can anyone tell me, if I upgrade on my device, does it in turn update the database and therefore anyone else connecting to it will be forced to update in order to connect to the database?
Reply
#2
There are only minor database changes - so other users can still connect and work with the database - but of course some new features can only be set by the new client version so all users should update as soon as possible...
Regards/Gruss
Oliver
Reply
#3
(03-04-2019, 03:52 PM)DevOma Wrote: There are only minor database changes - so other users can still connect and work with the database - but of course some new features can only be set by the new client version so all users should update as soon as possible...

Thank you - that's all I really needed to know is how it was going to effect the rest of the team - didn't know it would require a downtime for users.
Reply
#4
So installed the updated version which appeared to import all my environments. But when I launch putty sessions to an enviroment for the first time, it launches external to the app, and in the app I get a message that says:

"The session log file "putty.log" already exists. You can overwrite it with a new esssion log, append your session log to the end of it, or disable session logging for this session. Hit Yes to wipe the file, No to append to it, or Cancel to disable loging."

If I click either Yes or No, it still keeps the session in a separate putty window external to the app. There doesn't appear to be any way to re-dock the window. Only a couple of my sessions ended up self-docking back to the main app.
Reply
#5
(09-04-2019, 11:19 AM)Kim A Wrote: So installed the updated version which appeared to import all my environments. But when I launch putty sessions to an enviroment for the first time, it launches external to the app, and in the app I get a message that says:

"The session log file "putty.log" already exists. You can overwrite it with a new esssion log, append your session log to the end of it, or disable session logging for this session. Hit Yes to wipe the file, No to append to it, or Cancel to disable loging."

If I click either Yes or No, it still keeps the session in a separate putty window external to the app. There doesn't appear to be any way to re-dock the window. Only a couple of my sessions ended up self-docking back to the main app.

Hi,
could you please check the putty sessions settings: make sure you disable the log or set it to "always append" or "overwrite" depending on your needs. The effect you discover only shows up when there is an extra window from putty "stealing" the frame. So if logging is set to silently append or overwrite the session will be embedded into the tab normally. But that setting is pure putty.
Best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --
Reply
#6
(09-04-2019, 01:29 PM)Michael Scholz Wrote: Hi,
could you please check the putty sessions settings: make sure you disable the log or set it to "always append" or "overwrite" depending on your needs. The effect you discover only shows up when there is an extra window from putty "stealing" the frame. So if logging is set to silently append or overwrite the session will be embedded into the tab normally. But that setting is pure putty.
Best regards,
Michael

Thanks Michael. That does seem to have fixed it, but this wasn't an issue with the prior versions for me, only just now with this version even though it carries forward the prior settings, so that's what puzzled me.
Reply




Users browsing this thread: 1 Guest(s)