Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, January 2, 2016 4:43 AM | 1 vote
Hello, I'm running Windows 10 on my PC.
When I RDP into my PC from a Macbook, the PC console session immediately displays the lock screen.
On the Mac side, 'Connect to admin session' is checked.
My screen saver is set to (None), and 'On resume, display logon screen' is not checked.
I've seen how to exit the RDP session using: tscon.exe # /dest:console
which ends the RDP session and unlocks the console.
That's not ideal because I'm certain to walk away and not run the batch file.
Also, I see how Chrome Remote Desktop does not lock the console session, but I'm on my own LAN, and am really looking for an RDP solution.
My goal is to have an unlocked console session, that I can periodically RDP into, and the console session remains unlocked.
Thanks,
casey
All replies (3)
Sunday, January 3, 2016 1:20 PM âś…Answered | 1 vote
RDP locks the console, no way to avoid that. RDP gives a remote session, not an extra session or a shared session. If that user session already exists RDP will connect to that user session as it is, and if disconnected the session will carry on running.
You should be able to unlock the machine from the console, so if you return to the console unlock that and it will disconnect any RDP connections. Does that do what you want?
If you want to connect and keep the console viewable and open you will need to use 3rd party software such as TeamViewer which has some functionality free for personnel use.
Sunday, January 3, 2016 2:40 PM | 1 vote
Thanks, I came to similar conclusion:
http://steamcommunity.com/discussions/forum/11/458604254458624157/
Being able to unlock the machine from the console does not support the scenario of PC game streaming (e.g. to Nvidia Shield TV or Steam Link). They both expect an unlocked session and are not capable of unlocking.
Monday, January 4, 2016 9:00 AM | 1 vote
Hi casey,
Yes, there is no other workaround but using tscon sessionID /dest:console. However, The mentioned command leaves the remote computer unlocked, which can reduce the system security.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].