I’ve noticed a couple annoying issues since updating PRA from 25.1.1 to 25.1.2. We only exclusively use Jump Clients to Windows Servers and Clients through the console, and here’s what I’ve noticed:
- During the connection process after logging into Windows, if you switch focus to a different tab/connection and then come back, the jump client will have connected, but you will not have mouse control. You can use keyboard control or use any of the quick commands from the Console, but in order to get mouse control back, you must fully disconnect and reconnect back into the jump client, ensuring you don’t switch focus to a different server. This one is pretty consistent and can be reproduced almost every time.
- This one is a little more random and doesn’t always happen, but I’ve noticed it happening often now since the PRA update. In order to launch applications in Windows, I have the habit and clicking the Windows Start key and immediately start typing the product/application I need to launch. Windows will start performing the search for what you typed. For some reason when doing this in PRA, Windows often ignores the keystrokes and there is no way to search without clicking into the search bar and using that (which I often hide because I don’t need it).
Has anyone else noticed anything like this? Possibly related, but I do have to run with Clipboard Synchronization Mode to Manual because PRA doesn’t play nice with our main ERP product, so this could all be related to that setting since that controls mouse/keyboard control.
