Alternative to SendKeys when running over Remote Desktop?

Question

I have an application which injects keystrokes into applications via SendKeys.

Unfortunately, the application will not work when I am running it via Remote Desktop b

Answer 1

You can workaround RDP issue by having desktop always logged in before use (or configured for auto-login @ every boot).

And even with the auto-login, if you ever need remote desktop access to run automation, or manage system, etc., the preferred method is using VNC for remote access rather than RDP. Reason is VNC is cross platform and you won't run into this RDP issue. VNC works like a relay of your actual desktop (RDP console session 0 or the "head" of the machine), the disadvantage being one remote session at a time only (or you all share the same desktop + keyboard + mouse). VNC will work for virtual machines too. Use VNC instead of RDP or local (RDP) access from the (VMWare/Hyper-V/Xen) virtual machine manager software.

The only thing to watch out for with VNC still is that the desktop not be configured to auto-lock on idle or screensaver, that may also stop send keys and GUI automation from running, so be sure to disable that. Screensaver & monitor power save is ok, just no auto-lock & password protect.

NOTE: I'm not sure, but believe since VNC relays the desktop "as is", it is the same as executing locally from the app/system's point of view, so it should in theory also be able to fool the system/app that doesn't allow SendKeys via RDP. I've had no issues using this VNC method for AutoIt + SendKeys, whether I was actively connected via VNC, or disconnected (sendkeys/automation still continues to work after disconnect because on the actual desktop, it's still logged in, just that VNC not active).

Answer 2

SendKeys is not a good fit mainly due to:

• It can only send keys to active/focused application, which is never guaranteed to work because the the active application can change between the time the keys are actually sent.
• RDP and many other libraries (e.g., DirectX) block them mainly for security reasons.

Better alternatives:

• Use SendMessage or SendInput for simple needs
• Some good examples of how to use SendMessage can be found:
  • Send strings to another application by using Windows messages
  • SendMessage via pInvoke
  • How To Send Keystrokes To Extern Win Application
• For more elaborate needs, it is recommended to use WCF
• To get you started, read this Basic Tutorial that talks about Inter Process Communication

Sample code using SendMessage:

HWND hwndNotepad = FindWindow(_T("Notepad"), NULL);
HWND hwndEdit = FindWindowEx(hwndNotepad, NULL, _T("Edit"), NULL);
SendMessage(hwndEdit, WM_SETTEXT, NULL, (LPARAM)_T("hello"));

Answer 3

In my case I was successfully using WinAPI's SendInput with hardware scan codes. It seems like SendKeys maps chars to scan codes incorrectly.

Answer 4

In my case I was using sendkeys as part of test automation. It would not work from my build machine, where the build agent runs through remote desktop protocol. I'm not happy about it but I was able to skip that test as part of my automated builds.

Using Win32 calls to send window messages might work, if I have time I may try that someday.

Anyhow, here is the check to see if the current code is running in a remote desktop session:

System.Environment.GetEnvironmentVariable("SESSIONNAME").StartsWith("RDP-")