Small v9 Bug - Allow Multiple Connections
Hi RDM Support
Another v9 "artefact" to look at...
The way that the option "Allow open multiple connections" works has changed. Prior to version 9, it was a simple check-box (AllowMultiplePrevious.jpg). In version 9, this has been upgraded to a drop-down list (AllowMultipleV9.jpg).
I see the point of having the three options "Default", "True", "False" - don't get me wrong - I like it.
But the problem is, on the previous version (8.4.6.0), I had configured hundreds (but NOT ALL) of our Putty sessions to TICK this box to ALLOW multiple opens. Now that I've upgraded to v9, all these connections have reverted to a state of "Default". Now I know that I could change my Options so that my default setting is to "Allow" multiples (under File > Options > General), but the problem with that approach is that it would FIX all the sessions that were checked previously, but it would BREAK all the sessions that weren't (ie - it would allow multiple opens that previously weren't allowed).
Since there are so many connections that I had put a TICK in the box, is there a way to update (eg - via direct SQL) all those entries to set the new variable to "True"?
Guys - I can handle this manually if required, so please don't spend more than 5 minutes thinking about this one - if there's an easy way - let me know - otherwise I'll live with it!
Thanks
Des
AllowMultiplePrevious.jpg
AllowMultipleV9.jpg
All Comments (3)
Des,
This is one issue that I have to fix in the batch edit.
David Hervieux
Sorry, I don't follow. Do you mean "A simple batch edit of the affected connections should allow you to set the Allow Open Multiple Connections option, however editing that particular property isn't currently a feature of Batch Edit. In the future, we intend to add it to Batch Edit, which will provide you with a reasonable workaround to the problem." ??
I was looking at writing a PowerShell script to fix the affected entries myself, but unfortunately, it doesn't seem to work. If my dectective work has been accurate, the property used to be called "MetaInformation\AllowMultipleConnectionPerSession", but is now called "MetaInformation\AllowMultipleConnections". I was hoping that PowerShell would have read/write access to both of these at the same time, allowing me to create a loop that fixed all my connections, but it seems that since I've upgraded to v9, my PowerShell only sees the later, no the former.
Oh well, enough time spent on this one - drop it, I say! :)
Cheers
Des
Quick note to let you know that you can now edit "Allow Open Multiple" via batch edit.
Stéfane Lavergne
10-15-2013 4-51-34 PM.jpg