How to remote into PC without locking console session

[kcchesnut]

I've got a Win 10 PC connected to my TV for gaming, and a Macbook that I will RDP into the PC to do some work. As soon as the RDP session connects, the PCs console session is locked and displays the Locked screen. To be specific, the Macbook is displaying the console (i.e. Connect to admin session), but a new session is being created and locking the TVs session.

The PC does not have a screen saver enabled, and the 'On resume, display login screen' is not checked.

I've seen that I can exit the RDP session using: tscon.exe # /dest:console to end the RDP session and unlock the console session ... but I'm not always going to remember to do that.
My preference is to prevent the console session from being locked in the first place.

Also, I've seen that if I use Chrome Remote Desktop, the console session is not locked; but I'd rather just use RDP since I'm on my private LAN.

So my goal is to keep the PC unlocked, but still be able to periodically remote into it. RDP is preferred, but another LAN based remote product would be great too.

Thanks,
casey

My current workaround is to use an Xbox One controller with a chatpad to unlock the PC. Then I have a little helper app listening for some XInput commands to launch Steam in Big Picture Mode. I assumed the XB1 home button would launch BPM, but its not working for me. Also, I tried an XB360 controller with chatpad, but its driver wont let me login at the lock screen. Finally, I tried a Steam Controller, but I cannot get it to open a virtual keyboard at the lock screen. Currently trying to avoid having a keyboard in the living room.

[Morbo]

Have you tried VNC[www.realvnc.com]?

[Nevynn]

I'm not sure if it will work on Windows 10, but with Windows 7 all you have to do is replace "C:\Windows\System32\termsrv.dll" with the Server2008R2 version to allow multiple active users.

Some creative web searching will get you the information and files you need to accomplish this

[kcchesnut]

Just tried Teamviewer and RealVNC. Neither locked my console session so that was good. Both had problems with the resolution of my TV being different than my notebook. Teamviewer wouldn't scale up to full screen and RealVNC did not render the left 10% of the screen, although it might have been scaled correctly. Teamviewer perf did seem better than RealVNC when comparing video playback.

[kcchesnut]

Splashtop seems to be working. It's handling my setups disparate screen resolutions, although slightly less sharp than RDP. Streaming videos look good. I think it's a workable solution.

[Morbo]

I'm not familiar with Splashtop. Thanks for posting what you came up with.

[kcchesnut]

Following up on Nevynn's suggestion. I tried out the RDP wrapper. Basically, it lets you have multiple sessions on a single Win 10 machine.

One option is to use RDPConf.exe to let a single user have multiple sessions. So your console mode could be running Steam BPM connected to the TV, and then your RDP sessions can be work related. Doubtful about apps supporting multiple sessions, so I'm not trying this out.

Instead, I setup 2 user accounts. First user account 'gaming' will auto login to PC (console) and runs Steam BPM (visible on TV). Second user account (my account) can RDP in as needed from notebook.