Mobile Development: RDP AutoLogin v5

Print This Post Print This Post

Based on version-4 here is an more extended version with the option to preset Resource mapping (Device storage and Remote desktop sound).

These two options are controlled by the default.rdp file:

EnableDriveRedirection:i:1
AudioRedirectionMode:i:

with the following options for windows mobile:

EnableDriveRedirection
1=enables access to local files inside the host session
0=disable access to local files

AudioRedirectionMode
0=Redirect sounds to the client,
1=Play sounds at the remote computer,
2=Disable sound redirection; do not play sounds at the server

The settings program has been updated to let you change the corresponding registry settings for RDP_AutoLogin.exe:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\RDP_autologin]
...
"AudioRedirectionMode"=dword:00000002
"DeviceStorage"=dword:00000001
...

Here are the updated executables:

RDP_Autologin.exe: [Download not found] Latest

RDP_Autologin_Settings.exe: [Download not found] Latest

RDP_Keepbusy.exe: REMOVED

Update 21.aug.2012: new binary downloads at code.google.com (google code is discontinued). Fixed a bug with RDP_AutoLogin (if run twice). Added RDM_KeepBusy settings to settings application (see also changelog at google code).

Update 10. Feb 2015: fixed code so that AudioRedirection and DeviceStorage settings are applied. The WM6 Pro binary is updated.

For Windows Mobile/Embedded Handheld 6.5.3 use RDM_KeepBusy (google code discontinued)!

Source Code (google code is discontinued) new at github

RDM_KeepBusy.exe Binary at github

32 Comments

  1. Adam J says:

    Hi – great program, RDP_AutoLogin works great for me after the “run twice” bug fix was implemented, and the RDP_KeepBusy is a huge help as well. One thing I noticed, on the RDP_Autologin_Settings exe out a Google, is that the new RDMKeepBusy settings page does not seem to fully update the registry with modified values.

    Also, on the first time running RDP_Autologin_Settings, it creates default registry entries for the RDP_AutoLogin and RDM_KeepBusy programs, but those entries differ from the examples you list in the source code. I am not quite sure what registry settings are required to get RDM_KeepBusy working, I’ve tried a few different options, but it doesn’t work like RDP_KeepBusy did.

    I am using several Intermec CK3 devices with Windows Mobile 6.1 Classic.

  2. admin says:

    Hi Adam

    RDP_KeepBusy is deprecated, please use RDM_KeepBusy (sources also at google).

    I did not expose all settings of RDM_KeepBusy, as they are very technical, for example what keys to simulate or what values to use for mouse move.

    RDP_KeepBusy did mot work for me starting with WEH 6.5.3.

    Regards

  3. Adam J says:

    Thanks for the reply. I have tried RDM_KeepBusy, and even though I see the process running in Task Manager, it does not keep the session active and RDP will still timeout after 10 minutes. For what is exposed in Autologin_settings, I tried both what the program defaulted for registry entries and what the sample registry entires on Google are, with no luck.

  4. Conner says:

    Hi.

    Thanks very much for the excellent software! I love that RDM_KeepBusy has been integrated into the RDP_Autologin_Settings.

    On my Win Mobile 6.5 device everything works great with RDP_Autologin_Settings.exe except for the “Fit remote desktop to screen” option in the “Screen” tab. Even though I select it and save it, as soon as the unit reboots, these settings revert back to not being enabled (the colors also revert to 256, but that is not a big issue).

    Is there a file that I can manually change/set/save the “Fit remote desktop to screen” settings on the mobile unit?

    Thanks in advance,
    Conner

  5. admin says:

    Hello Adam

    I will check the settings will save/restore correctly the next days.

    Thanks for your testing and comments.

    regards

    Josef

  6. admin says:

    Uuups

    although I would like to thank Adam, the comment was for Conner.

    Hello Conner, I will check the code and update. Thanks for your testing too.

    regards

    Josef

  7. josef says:

    Hello Conner

    I cannot reproduce your issue. Just checked that the values are written correctly to the registry, saved to default.rdp and filled back in tsc_dialog.cpp into the dialog:

    ====================================
    REGEDIT4

    [HKEY_LOCAL_MACHINE\Software\RDP_autologin]
    “ColorDepth”=dword:00000003
    “AudioRedirectionMode”=dword:00000000
    “DeviceStorage”=dword:00000000
    “FitToScreen”=”1”
    “SavePassword”=”1”
    “ExecArgs”=””
    “StartOnExit”=””
    “DesktopWidth”=”480”
    “DesktopHeight”=”640”
    “Domain”=””
    “Password”=”rdesktop”
    “UserName”=”rdesktop”
    “Computer”=”192.168.128.5”
    “FullScreen”=”0”
    ====================================

    Domain:s:
    ColorDepthID:i:3
    ScreenStyle:i:1
    DesktopWidth:i:480
    DesktopHeight:i:504
    SavePassword:i:1
    UserName:s:rdesktop
    ServerName:s:192.168.128.5
    Password:b:0200000000000000000000000000000000000000000000000800000072006400700000000E66000010000000100000003278110349D4D2D2EFCA0F05CB2DF19C0000000004800000100000001000000099C0CDE62EF8E4E796255CADF84E41412000000076F6C149034570E9117CF9E75E7912324C29471EEA760850FFE25E1CA308CD2D14000000547E9D36CC172E544E01D12E50256FACEBE8DEFD
    MCSPort:i:3389
    Keyboard Layout:s:00000409
    BitmapPersistCacheSize:i:1
    BitmapCacheSize:i:21
    KeyboardFunctionKey:i:12
    KeyboardSubType:i:0
    KeyboardType:i:4
    KeyboardLayoutString:s:0xE0010409
    Disable Themes:i:0
    Disable Menu Anims:i:1
    Disable Full Window Drag:i:1
    Disable Wallpaper:i:1
    MaxReconnectAttempts:i:20
    KeyboardHookMode:i:0
    Compress:i:1
    BBarShowPinBtn:i:0
    BitmapPersistenceEnabled:i:0
    AudioRedirectionMode:i:2
    EnablePortRedirection:i:0
    EnableDriveRedirection:i:0
    AutoReconnectEnabled:i:1
    EnableSCardRedirection:i:1
    EnablePrinterRedirection:i:0
    BBarEnabled:i:0
    DisableFileAccess:i:0
    MinutesToIdleTimeout:i:5
    GrabFocusOnConnect:i:0

    ======================================
    the values for DesktopWidth:i:480 and DesktopHeight:i:504 are the ones filled when FitRemoteDesktopToScreen is selected. If not selected you will get DesktopWidth:i:640 and DesktopHeight:i:480 (or whatever the device screen resolution is).

    I also checked for the ColorDepth setting and that is OK to.

    As you have the source, you can simply check yourself.

    Tested on WindowsEmbedded Handheld 6.5.3 device.

    best regards

    Josef

  8. philippe says:

    Hi,
    this tool should be great but does it woks on windows ce 5.0 (because I tried and I had an error message).

    Thanks any way.

  9. admin says:

    Hello philippe

    this tool is not needed on a Windows CE device as WinCE supports launching the RDP client using .rdp files. Ask your device’s OEM.

    ~Josef

  10. philippe says:

    Hello Joseph,
    thanks for the reply, but I thought that with the .rdp, it was not possible to put the password, and also start the connexion directly, (without user intervention)

    Philippe

  11. Conner says:

    Hi Josef.
    Thanks again for all your hard work.
    The RDP_Autologin_Settings file accurately shows the “Fit remote desktop to screen”.
    The problem arises when the user launches RDP_autologin” and connects to the server, then in the options button of the RDP connection window, the Fit remote desktop to screen” is unchecked (but all the other portions load correctly from the RDP_Autologin_Settings.

    Is it possible to provide the path to the files that are written/read from so that I may check that the
    “DesktopWidth”=”480″
    “DesktopHeight”=”640″
    are correct? I tried searching on the Win Mobile 6.5 unit but cant find the files.

    Is there a particular directory the RDP_autologin and RDP_Autologin_Settings files should be saved to in the 6.5 units?

    Thanks,
    Conner

  12. Conner says:

    Just found the default.rdp in the “\Windows” directory it looks like:
    Domain:s:domain
    GrabFocusOnConnect:i:0
    MinutesToIdleTimeout:i:5
    DisableFileAccess:i:0
    BBarEnabled:i:0
    EnablePrinterRedirection:i:0
    EnableSCardRedirection:i:1
    AutoReconnectEnabled:i:1
    EnableDriveRedirection:i:0
    EnablePortRedirection:i:0
    AudioRedirectionMode:i:2
    BitmapPersistenceEnabled:i:0
    BBarShowPinBtn:i:0
    Compress:i:1
    KeyboardHookMode:i:0
    MaxReconnectAttempts:i:20
    Disable Wallpaper:i:1
    Disable Full Window Drag:i:1
    Disable Menu Anims:i:1
    Disable Themes:i:0
    KeyboardLayoutString:s:0xE0010409
    KeyboardType:i:4
    KeyboardSubType:i:0
    KeyboardFunctionKey:i:12
    BitmapCacheSize:i:21
    BitmapPersistCacheSize:i:1
    Keyboard Layout:s:00000409
    MCSPort:i:3389
    Password:b:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    ServerName:s:1.1.1.1
    UserName:s:username
    SavePassword:i:1
    DesktopHeight:i:480
    DesktopWidth:i:640
    ScreenStyle:i:2
    ColorDepthID:i:1

    but I cant find the “tsc_dialog.cpp” nor the:
    REGEDIT4

    [HKEY_LOCAL_MACHINE\Software\RDP_autologin]
    “ColorDepth”=dword:00000003
    “AudioRedirectionMode”=dword:00000000
    “DeviceStorage”=dword:00000000
    “FitToScreen”=”1″
    “SavePassword”=”1″
    “ExecArgs”=””
    “StartOnExit”=””
    “DesktopWidth”=”480″
    “DesktopHeight”=”640″
    “Domain”=””
    “Password”=”rdesktop”
    “UserName”=”rdesktop”
    “Computer”=”192.168.128.5″
    “FullScreen”=”0″

    Sorry for not completely understanding how to make sure the files are corect.
    Conner

  13. Conner says:

    Hi Josef.
    I mistakenly had the values switched for the Height and Width in the above posting. The have them correct in the actual default.rdp file (DesktopHeight:i:640 DesktopWidth:i:480). This works well in version 4 of RDP_autologin. But somehow, with version 5, even with the correct settings in the default.rdp file, the “Fit remote desktop to screen” is not checked off in the RDP connection window eventhough it is checked in the RDP_Autologin_Settings.
    Also, do you know of anyway to lock down each field in the RDP connection window so that users dont make unauthorized changes to the settings?
    Thanks again for sharing your awesome work!
    Connie

  14. […] fixed a bug in RDM_KeepBusy. It worked only for the first session and not after close/open another session. Please always use […]

  15. Toni says:

    Hello Joseph,

    You can use the program together RDM_autologin and iLock5?

    I want to block the terminal and start the RDM session and end the session. ILock5 possible with?

    I use Intermec CK3 with WM6.5

    Tranks! (sorry for my bad english)

  16. josef says:

    Hello Toni

    Yes, you can use all these together.

  17. Toni says:

    Hi Josef,

    Thanks for your response.

    as is the proper way to use them? I do not get them to work well

    Thanks!

  18. Poinson says:

    Hello,

    I found your autologin application very usefull.
    But I can’t succeed to make the sound work.
    The sound is produced by the server (ie windows sound when login).
    I heard it on the terminal when i am running RDM without autologin (the resource remote desktop sound is set to “Play on this device”). Then all is fine.

    When I run autologin (the resource remote desktop sound is set to “Play on this device” using RDP autologin description), I heard no sound at all. During connection, if I edit the options of RDM, the resource remote desktop sound is set to “mute”.

    I think this is a bug (difference of value between autologin and rdm ??).

    I tried to set different values into default.rdp AudioRedirectionMode:i:0 or 2, this has no effect.

    Any idea of the problem ?

    Regards from France 😉

    Sebastien

  19. josef says:

    Hello Sebastien

    I did again double check the code and what happens. From programmers side everything is correct:

    Before rdp_autologin starts wpctsc.exe and fills the dialog it creates a \windows\default.rdp file with the settings of the rdp_autologin registry. I have checked what is written to the rdp file and it is the same as when you manually setup remote desktop mobile (RDM):

    %< -------------------------------------------------------------------------------- else if(wcsstr(rdpLines[c].line, L"AudioRedirectionMode")!=NULL){ wsprintf(szTemp, rdpLines[c].line, dwAudioRedirectionMode); //0=Redirect sounds to the client, //1=Play sounds at the remote computer, //2=Disable sound redirection; do not play sounds at the server %<-------------------------------------------------------------------------------- The only possible cause I can imagine is that RDM does not care about the AudioRedirectionMode setting in the rdp file and just uses what is visible in RDM Options/Resource s dialog. I did test and wrote a rdp file with AudioRedirectionMode:i:2. I then killed wpctsc.exe! Then started RDM again and opened Options/Resources it shows the selection 'Mute', which is AudioRedirectionMode:i:2. This is all correct. I am sorry, but I cannot help. BTW: you are hopefully using the latest version (v5) of the tool set: http://code.google.com/p/rdp-auto-login/downloads/list

    ~josef

  20. Toni says:

    Hi Josef, Please contacme with my. I want to propose development. Tranks!

  21. josef says:

    Hello Toni

    what do you want to propose?

    ~josef

  22. Toni says:

    Hi Josef,

    Please, write via email. Thanks

  23. Poinson says:

    Hi Josef,

    You are right.
    It seems that the Audiomode parameter is not read into default.rdp by the MS client.
    The value set into the drop box is only kept into memory.
    If you close the MS client, the default value is MUTE !

    I am really interested into a RDP client for windows mobile.
    I see rdekstop-ce but it seems that this product does not work with a win2008r2 server.
    If you have any advice for me, you are welcome.

    regards,

    Sebastien

  24. Poinson says:

    Hi Josef again,

    About mute sound, is possible that autologin change the contents of the option/resources/Sound drop box according to the correct value stored into autologin parameters ?

    Regards

  25. Barry says:

    Hello Josef

    We are looking for a method for autologging in on Remote Desktop Mobile for our Socket 655 devices. These are running Windows Embedded Handheld 6.5. Also a method for stopping the 10 minute timeout on the RD client.

    We are reading your various blogs and sites with interest but we are not sure where the latest binaries are. We have the ones from February 2013 but there appear to be changes up to June 2013. Is the idea that others like us would or could now use the exectuables as in the early days you seemed to be posting the source as well.

    It seems there is no other way of configuring this auto login in WEH 6.5 other than your utility. We are hoping to try it soon.

    Thanks very much

    Barry

  26. josef says:

    I am sorry for not updating the binaries every time.
    OTOH this is for developers and these should be able to compile an actual binary based on the sources I provide.

    Sorry, not only providing ready-to-use apps and tools.

    ~Josef

  27. Barry says:

    Hi Josef

    Sorry, we didn’t mean to upset. We are a bit light on CPP skills at present. Also, we cannot see how to download all the source and .sln files. We would be willing to pay for this utility.

    Can you help us?

    Barry

  28. Les says:

    Very useful tool/program. I’m using a Honeywell Dolphin 7800 w/WM 6.5
    The program will run once or twice, but will hang as a process. The only way to get it to re-connect is to start task manager and Kill Process. Is there a new version or known work around for this

  29. josef says:

    Always use the latest versions as available thru http://code.google.com/p/rdp-auto-login/source/checkout

  30. Felix says:

    Hi,

    gibt es eine Möglichkeit dafür die title bar auszublenden? Das muss meines Wissens in der Applikation geschehen.
    Nun geht ja das hier leider nicht, da der Microsoft RDP Client verwendet wird und sich dieser schlecht bearbeiten lässt :).

    Ich versuche auf einem Intermec CK3X mit dem Ilauncher eine RDP Session zu starten. Da klappt auch. Leider gibt es in der Zeit, in der die Verbindung aufgebaut wird, die Möglichkeit, die Title Bar hervor zu heben.

    Haben Sie hier eine Idee, wie ich das umgehen kann?

    Vielen Dank
    Felix

  31. Felix says:

    ausblenden ging zwar nicht, aber die Funktion der Icons auf “dummy.exe” zu setzten klappt ganz gut:

    https://msdn.microsoft.com/en-us/library/ff599645.aspx

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

Leave a Reply