as MS does not change it, the Remote Desktop Mobile application still disconnects a session after 10 minutes idle time.
Although there is a solution for Windows Mobile 6.1 (http://www.hjgode.de/wp/2009/09/18/wm6-1-remote-desktop-client-disconnects-after-10-minutes/) based on the posting of Rafael (MS Support), this will not work with Windows Embedded Handheld (WM6.5).
The TSSHELLWND will not react on mouse_event and you have to replace the calls by SendMessage and send the WM_MOUSEMOVE to the Terminal Server Input window.
The attached application will do so but it will start only on Int*rm*c devices. It sends a mouse_move message all 4 minutes to the TS input window and so the idle timer will not timeout.
If you ever need to stop RDMKeepbusy from running in the background, you will need StopKeepBusy which is part of the executable download.
For visual control, RDMKeepbusy shows a small blinking line in the task bar:
green = Remote Desktop window found and input window is active
yellow = Remote Desktop window found, but no input window active
red = Remote Desktop window not found
Version 1: DOWNLOAD:RDM Keepbusy - Windows Embedded Handheld application to avoid idle timeouts (Hits: 407, size: 8.07 kB)
Version 3: Updated version (you dont need to start RDM before starting RDM_KeepBusy): DOWNLOAD:RDM_KeepBusy 3 - (Hits: 362, size: ) Note: this will run only on intermec devices!
Version dec 2011: Updated version (see usage.txt): DOWNLOAD:RDM_KeepBusy - remote desktop mobile disconnects after 10 minutes of idle time. RDM_KeepBusy will avoid this by simulating mouse movements (Hits: 384, size: 8.56 kB)