7

I just installed Windows 7 on my laptop. I want to be able to log in using RDC quickly. If I failed to log out or disconnect prior to walking away from my laptop, when I attempt a RDC connection it pops a confirmation dialog up on the laptop and won't connect the RDC connection for 30 seconds unless the confirmation dialog is used.

Is there a way to disable this?

Charley Rathkopf
  • 267

4 Answers4

7

using Local Group Policy Editor (gpedit.msc) there is a setting under :

Administrative Templates \ Windows components \ Remote desktop services \ Remote desktop session host \  Connections

saying "Set rules of remote control of remote desktop services" witch lets you specify the interaction mode and the control level for an RDP session

enable it and choose the "Full control without user permission" option. so the logged user won't be prompt for confirmation (there is more details there)

you can also set the Session time limit for active but idle RDP service under session time limit folder to "Never" and it won't disconnect you you IDLE.

1

This Microsoft Support article :
Remote Desktop Connection 6.0 prompts you for credentials before you establish a remote desktop connection
suggests turning off this message by text-editing the .rdp file and changing the value of authentication level to zero, like that:

authentication level:i:0

harrymc
  • 498,455
0

You could use an AutoHotkey script to check if the window is open periodically. Without an image of the comfirmation dialog, I don't know the exact text, but you can substitute it in my script:

SetTitleMatchMode, Slow
loop 
{
    IfWinExist, Remote Desktop Connection Disconnected ; modify this
        Send { Enter }
    else
    {
    Sleep 1000 ; wait a second, save our CPU
    }
}
0

I had the same problem for a Windows Server 2012 machine. After trying many other approaches, I tried the one suggested by John T and got it to work. It's somewhat different, probably because of the Metro interface and/or the secure desktop that the popup dialog runs in. It's not able to interact by window title (which is "Remote Desktop Connection"), so I have it detect the process and then send enter.

; Wait for the "Remote Desktop Connection" process to popup and automatically cancel
; must use PID matching on sessionmsg.exe because IfWinExist didn't work (secure desktop?)
loop 
{
    Process, wait, sessionmsg.exe, 2
    NewPID = %ErrorLevel%  ; Save the value immediately since ErrorLevel is often changed.
    if NewPID = 0
    {
        Sleep 1000 ; wait a second, save our CPU
    }
    else
    {
        Send { Enter }
        Sleep 10000 ; it takes sessionmsg.exe several seconds to exit
    }
}
Matt Chambers
  • 203