Typing Macro running in an RDP session
Hi, I'm running the free edition v 2019.1.39.0 x64 on Windows 10.
I'm trying to run a Typing Macro on one or more RDP sessions (embedded).
The Macro runs as expected -- but the typing follows the focus everywhere.
By everywhere I mean in any focusable text box in any app both local & remote.
Is this the intended behavior?
I created the macro both in the RDP Event properties as well as the macro manager. In the latter case I set the check to prompt for which session(s) to run the macro on. I was prompted but the macro still sent keys to any focusable box I clicked on -- and wouldn't actually send to the session I asked it to, unless I focused the session myself.
To test this I just added a macro string "z z z z z z ", and set the command time to 3000 ms.
All Comments (6)
Hello,
The macro will run where the focus is set.
You would need to increase the starting time of the macro so that the macro starts after that you had place the cursor in the appropriate field to start properly.
The focus needs to be done manually by you prior to the execution of the macro.
Best regards,
Jeff Dagenais
So you're saying there's no way to send keystrokes only to a remote session?
I don't understand, what's the use of being able to run a macro on more than one session at once, if you're only able to set focus on one session at a time?
Maybe I'm asking this wrong, is there a way to run a typing macro that only affects a remote session - or at least not send keys locally if the session loses focus?
...Or, is there a way to keep a remote session alive - to prevent the remote OS from going idle? (maybe by background input?)
Hello,
In the properties of your RDP session, under the Experience tab, there's a KeepAlive option.
Could you give it a try?
Best regards,
Jeff Dagenais
I have that option set, but I assume that's to keep the remote desktop (protocol) session itself alive -- not the OS login session. Two separate things.
I was hoping to send a {scrollock} key to the remote session every 60 seconds to keep it from locking the screen....
This actually works great, but RDM will only send to to the local active focus -- so I have to keep both RDM and the session tab in focus for this to work.
The documentation (more than) implies that the typing macro is sent to the remote session only, so I was hoping it was a bug...
Hello,
Indeed, you need to be inside the appropriate session so that the typing macro can be executed into the appropriate session.
That being said, when the session is active, but the user is disconnected, if you right-click on the tab and select Reconnect, this should reconnect the session and send the credentials, which will allow you to authenticate rapidly. Could you give it a try?
Best regards,
Jeff Dagenais
The remote session is not being disconnected, the OS session is timing out - as in screen saver/power saving.
Sorry, we're getting nowhere here.
All I was looking for was a way to send keystrokes to a session without having it in focus - as in the local machine focus.
Although this would great, this feature was obviously never intended to be used this way.
Currently when the OS Session times out I do reconnect as it's faster than unlocking the OS with creds.
Thanks, we'll say you solved the problem.