remote desktopwindows
I have been trying to remote desktop from a Windows 10 client into a headless computer running Windows 10.
I have not been able to log into the console session as shown by qwinsta. I have tried the /admin switch or adding administrator session:i:1 to an rdp file.
The remote account I am logging into is an administrator. I have also tried local and microsoft account to no avail.
I use XP's built-in RDP when I need to connect to my Win7 box at home from work. I've not run into the problem you are describing, but typically when I close an RDP session I use Start > Disconnect instead of clicking the X in the corner of the RDP bar (but either method should disconnect instead of logging you off.) I'd suggest checking to see if you have more than one open session by using the QWINSTA command and kill any errant sessions using RWINSTA, then try reconnecting and see if the issue persists.
Easiest way...
When you open up Remote Desktop, Expand options and then go to Local Resources.
You want to change the sound to "Leave at remote computer" on the old version.
On the new version, Click settings then select "Play on remote computer"
Best Answer
The
/consoleswitch was for connecting to the console session. This functionality is no longer considered useful, and has been removed.For backwards compatibility, the
/adminswitch behaves like the/consoleswitch when connecting to a Windows 2003 or Windows 2003 R2 server. It does not behave like the/consoleswitch when connecting to a modern version of Windows. (I am not sure whether the/adminswitch has any effect when connecting to a Windows XP machine.)When connecting to a modern server version of Windows with the Remote Desktop Services component installed, the
/adminswitch affects certain behaviour, most notably whether a CAL (Client Access License) is consumed, as described in the linked article. (Note: prior to Windows 2008 R2, the Remote Desktop Services component was called Terminal Services.)When connecting to a modern version of Windows Server that does not have Remote Desktop Services installed, or to a modern version of a Windows client edition, you do not need the
/adminswitch. You can use it, but it has no effect.In summary: in theory, at least, you should not need to connect to the console session. Whatever documentation you are reading that suggests that you do may be out of date.
Addendum: Windows does allow components and third-party software to distinguish between Remote Desktop sessions and local sessions. In particular, applications run in Remote Destkop sessions have the REMOTE INTERACTIVE LOGON token whereas applications run in local sessions have the CONSOLE LOGON token.
I am not personally aware of any Windows components or third-party software that only allow access to the console logon except for the "Restrict [CD-ROM/Floppy] access to locally logged-on user only" policies, which are off by default.
The
/adminswitch does not affect this behaviour. I no longer have access to any Windows Server 2003 machines to see what the/consoleswitch did in this respect.