Keeping remote desktop session “alive” [closed]

Answer 1

You might want to attach your current RDP session to the CONSOLE. In such case even after disconnection the UI will be still active.

TSCON {sessionid | sessionname} /DEST:CONSOLE

Answer 2

My nightly regression suite used to fail on my local machine because enterprise rules locked the machine automatically after 14 mins of inactivity. So I wrote a small vbScript program to press "PrintScreen" key every 12 mins and it really solved the problem. Though this was not on RDP, but executing something similar on remote machine would help.

Answer 3

The accepted answer doesn't work if there is no rdp session at all, and you still want automate it through AutoIt.

They say in this case you should not use WinActivate and use ControlSend in AutoIt scripts instead, and it would work smoothly. And yes, that works, checked it myself.

Answer 4

We had the same problem with RDP. A workaround we used was to open another remote desktop session to connect to the same server:

1. You connect to server with RD.
2. From RD of step 1, you connect to server once again.

This way the 2nd session will be still "active" when you minimize or even disconnect your first RD session. Of course your Remote Desktop server has to support multiple connections from the same user.