WM 6.5: Remote Desktop Client disconnects after 10 minutes
Print This Post
Hi
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: 393, size: 8.07 kB)
Version 3: Updated version (you dont need to start RDM before starting RDM_KeepBusy): DOWNLOAD:RDM_KeepBusy 3 - (Hits: 342, 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: 362, size: 8.56 kB)
http://www.led-mg.de
Hi,
I have tried this new version on the CK71 but i won’t work. I have started the RDM_KeepBusy.exe, RDM is started but after 10 minutes i’m getting the time out.
I also don’t see the visual control in the taskbar.
Maybe i’m doing something wrong.
regards,
jordy
You have first to start RemoteDesktopMobile and then RDM_keepBusy, otherwise RDM_KeepBusy will exit immediately as the wpctsc.exe is not found in memory. You may start RDM, minimize RDM by clicking the (X) in the lower right corner and then run RDM_KeepBusy. Then RDM_KeepBusy will bring RDM to front and you can start your connection.
Hi Josef, Thanks for the application. I need to focus RDM when the user executes the aplication the second time. Can you upload the code somewhere?
Thanks!!!
Customer has tried RDMKeepBusy application, but it starts RDM in VGA resolution, and not in QVGA, which we have solved with a path. RDMKeepBusy, which moves the cursor around, is a work around, is there a solution?
It also seems like RDMKeepBusy only works, if it starts after “RemoteDesktop” is connected, it is hard to control when the system needs starting immediately.
Hi
RDM_KeepBusy does not start RDM in any special resolution. It does not know about VGA or QVGA. Please check your findings.
For people unable to run RDM_KeepBusy after launching there “own” or the normal RDM, the new attached executable does not exit as long as you don’t use StopKeepBusy.exe.
~josef
Hi eDo (and others)
there will be no source code. You can read everything I did special to other code and so you should be able to write your own KeepBusy:
“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.”
Sorry
Josef
[...] a post to let you know, that RDM_KeepBusy for WM6.5 has been updated Bookmark It Tags: disconnects, remote desktop mobile, windows [...]
Hi, and sorry for my english (I’m spanish): I have a problem with the application, it records a log continuously. I’d like to know how to deactivate it
Thanks in advance
Hello Jose
depending on settings in source file a log file is used. Please use the latest RELEASE build or check out the code at code.google.com (use TortoiseSVN or AnkhSVN).
regards
Josef
Hi.
I downloaded the WM6.5.3 version dec 2011 but it appears to have the same issue as Josef reported that it is logging by Default, not accoding to the usage text file which says dologging as a command line parameter to turn on logging. Unfortunately, this is causing my Application folder on my Motorola MC9190 to fill up. Could you please point me at a WM6.5.3 version without the logging turned on by Default or please provide me with a way of turning off the logging.
Regards Ben.
Hi again.
It appears that i misstyped my email address with regards to the comment above so it is now correct in this one.
Regards Ben.
Hi again.
We have looked at the source code on code.google.com under RDP_keepBusy but the code appears to be logging to a port, not a file and there also appears to be no code for StopKeepbusy.exe either. If someone could provide me with either the source code for version dec 2011 or the exe’s without the logging turned on by default I would really appreciate that.
Regards Ben.