WM 6.5: Remote Desktop Client disconnects after 10 minutes

Print This Post 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: REMOVED as nobody seems to use the actual version

Version 3: REMOVED as nobody seems to use the actual version

Version dec 2011: REMOVED as nobody seems to use the actual version

Latest version always at GITHUB (WM 6.5)

29 Comments

  1. jordy says:

    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

  2. Josef says:

    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.

  3. eDo says:

    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!!!

  4. Thomas says:

    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.

  5. admin says:

    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

  6. admin says:

    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

  7. […] a post to let you know, that RDM_KeepBusy for WM6.5 has been updated Bookmark It Tags: disconnects, remote desktop mobile, windows […]

  8. Jose A. says:

    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

  9. admin says:

    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

  10. Ben T. says:

    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.

  11. Ben T. says:

    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.

  12. Ben T. says:

    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.

  13. Rick Hernandez says:

    Hello Josef…

    Can you please explain me a little bit more about the source file… what is the exact name for the source file and what is the parameter I should add in order to avoid the log file population…. In the usage.txt file I see the parameter “dologging – enable logging to file” but what should I use to NOT logging…

    I really appreciate your response… Thank you very much in advance

    – Rick Hernandez

  14. James S says:

    The program is awesome in that it resolves the 10 minute timeout issue. However, I cannot turn OFF the logging, which fills up the devices storage in a day or two of constant running. How can logging be turned OFF?

  15. Vit N says:

    Hello.
    THis program is working fine for me, BUT HOW TO TURN OFF LOGGING?

  16. josef says:

    hello Vit N

    just change the global log var:

    BOOL bUseLogging=FALSE;

    and then re-compile.

    ~josef

  17. Vit N says:

    Thank you for reply, Josef.
    Can u post link for source code from code.google.com ?

  18. josef says:

    Hello Vit N and ALL OTHERS:

    http://www.hjgode.de/wp/2013/12/03/mobile-development-rdp_autologin-updated-to-support-clipboard-redirection/ has the link to all related posts and the source code.

    ~josef

  19. Jim K. says:

    Does anyone has a version of not logging as a default? This is a good program but if the logging is enabled it’s defeat it purpose.

    Thanks,

  20. Jim K. says:

    Found this link from the developer Hjgode, he has a version of no logging RDM_KeepBusy_nologging.exe but can’t download it.

    https://code.google.com/p/rdp-auto-login/source/browse/#svn%2Ftrunk%2Fbin

    Anyone?

    Thanks!

  21. JamesV says:

    Hi Jim K, if you are still looking for the no logging exe for RDM_KeepBusy it is available from the Google Code Archive on this page: https://code.google.com/archive/p/rdp-auto-login/source/default/source

  22. bradB says:

    I cant find a downloadable exe for the RDM_KeepBusy without the logging. Could someone send me the file or point me in the right direction. Google archive doesn’t have it any longer.

    Thanks

  23. josef says:

    Hi bradB

    executables are at Github and there is now a registry key to enable/disbale logging.

    ~Josef

  24. PaulT says:

    Hello
    i have an Problem with the RDM_KeepBusy.
    I use an CK3x divice with WM 6.5 EH and downloaded the latest version of the KeepBusy application.
    I startet Remote Desktop Mobile and than KeepBusy.
    After connecting the visual control should be blinking green, but it stil blinking yellow and Remote Desktop disconnect after 10 minutes.
    On a second device (Dolphin 60s) KeepBusy worked fine and the remoteconnection won´t disconnect (visual control is green).
    Can anybody help me with my Problem?

    Greeting Paul

  25. PaulT says:

    Hello josef,

    thank you for your answer.
    I tried both versions, but nothing worked.
    How can I disable Logging at the CK3x device? I searched for this option before, but I did not found the right way.

    Greetings Paul

  26. josef says:

    Hi PaulT

    for analysing the issue, the logging is needed. Just a few words about how it works: RDM_KeepBusy runs in background and searches for a sub window of RDM with a defined class. If it finds the window, the indicator truns green and the tool will send periodic mouse clicks inside the found sub window of RDM. That simulates the user not being idle.

    Please do the following: use the debug version (AFAIR https://github.com/hjgode/rdp-auto-login/blob/master/RDM_keepbusy/Windows%20Mobile%205.0%20Pocket%20PC%20SDK%20(ARMV4I)/Debug/RDM_keepBusy_18_03_2015.zip?raw=true). Copy the exe to \Windows on the device. Create a Link for the exe in your Program Files directory of the device. Start the exe using the Link. The indicator should blink in red as RDM is not running. Start Remote Desktop Mobile, the indicator should blink yellow. Now, in RDM connect to a Terminal Server or Remote Desktop. The indicator should blink in green.

    If the above does not work for you, please describe exactly what you do and what you see in detailed steps!
    The Dbug version should write a log file named “\Windows\RDM_keepbusy.exe.log.txt”. Upload the file to DropBoox or another free file hoster and send me the link. I will then look at the log to find your issue, but I assume you are doing something special as the app works fine on the CK3X. Please add the firmware version of the CK3X you use for testing and any SRs you installed. You may use the DevHealth dashboard to let the device create a sysinfo log: Press the question mark key and just close the Dashboard app. The Dashboard will write a new log file to \SmartSystems\ScreenCapture. Upload that latest log from this dir so I can get a copy.

    ~Josef

  27. PaulT says:

    Hi josef,

    I did everything exactly you wrote and placed the keepBusy app in \windows and copy a Link to ProgramFiles directory.
    I rebooted the Device.
    When I started RDM_keepBusy via Link in ProgrammFiles, the Remote Desktop Mobile launched automatically, but the indicator was blink in red.
    Then I connect RDM to the Remote Desktop and the indicator was blink in yellow, but did not changed to green.
    Firmware: 1.62.27.0006
    OS: 5.2.29354
    SS Ref Client Version: 4.92.03.343
    Build: 29354.5.3.12.43
    Software Update: SV01_1.62_CK3
    I didn´t install any (more) SR.
    The DRM_keepBusy Logfile created successful.

    Is it possible for you to contact me via my Mail-adress for sending the Logfile? The company I work for prohibited me to send the Logfile via Dropbox or something.

    Greetings Paul

  28. josef says:

    After looking at the log file it shows that the Remote Desktop Mobile client of PaulT uses a different Windows Text for connected sessions. Normally the text is “<something>- Remote Desktop Mobile” but he has “<something>- Remotedesktop Mobile”.

    There is a new version at github that can be configured on which Texts or classes to look for.

Leave a Reply