Windows 10: Windows 10 PRO - Remote desktop : local console session disconnects when a user signs in...

I have a Windows 10 PRO with Remote desktop enabled.There are two accounts associated with this machine.When user 1 is signed in on this physical machine and user 2 tries to connect remotely, the user 1 session is disconnected from the physical machine.How can I solve this?This is the reason for me to upgrade from windows 10 HOME to

:)

 

Windows 10 Remote Desktop Session - Sound stops when disconnect

This was originally asked as a question back in 2016

Windows 10 Remote Desktop Session - Sound stops when disconnect

To summarise: Connecting or disconnecting a Remote Desktop session to a Windows 10 machine disrupts the Audio Drivers in a way that halts audio playback, and requires the playing application to be restarted. It seems tied to updates to Remote
Desktop in Windows 10 Anniversary Edition.

That thread had plenty of people experiencing the same problem, plenty of attempts to fix the problem, but no conclusion or feedback from Microsoft.

I have tried:

• Disabling audio redirection in the Registry (HLKM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fDisableAudioCapture)
• Disabling the Remote Desktop Port Redirection Service
• Disabling (on my client) Remote Audio Playback (Playback on Remote PC)

None of these help. As soon as you connect or disconnect, RDP is messing with the Wave drivers, and the applications can't handle it.

Does anyone share this problem or have any other suggestions to try?

 

Windows 10 v1903 suspends Microsoft Outlook when Windows remote desktop user disconnects

It seems that Windows 10 Pro v1903 suspends Microsoft Outlook (365 or 2019 with latest office build v1908) when remote desktop user disconnects session (user closes session and does not log off).

In summary, we use remote desktop to connect to a clean install Windows 10 v1903 VM with Microsoft Outlook installed (365 or 2019 with latest build 1908). We set Outlook to Offline mode, queue 10 emails, turn Outlook back to online and quickly disconnect the session (not logging user out). I would expect that the emails should be sent. This however does not happen and is only sent when I log back into the remote session.

We can confirm that:

1. It is not a Windows 10 power and sleep setting, as all screen savers, sleep modes and such are disabled.
   
2. It is not a ‘System unattended sleep timeout’ as set out in this post. Bear in mind that the ‘suspension’ is immediate and does not take effect after 1 or 2 minutes.
   
3. It is not the NIC that is suspended, as we ran console ping tests while disconnected, which continued to poll.
   
4. But most importantly, an exact duplicate of the setup, using a Windows 10 Pro v1809 build, does not suspend Outlook build 1908, and the queued emails is successfully sent.
   
5. Updated. Changed group policy settings' Session Time Limits as suggested by harrymc, but it was unsuccessful.
   
6. Updated. The Terminal Server registry fix suggested here by harrymc , did not resolve the problem.
   
7. Workaround This disconnect shortcut proposed by harrymc DID WORK as interim workaround.
   

We are therefore convinced the problem is with a setting change on remote desktop users in Windows v1903. We have found that only Outlook is so far affected.

Any comment that might point us in the right direction to restore the functionality to Outlook whilst the remote session is disconnected, will be highly appreciated.

 

Connect to Console Session from Remote Desktop Mobile

This is an old topic, but one of the first Google search results for 'Remote Desktop Mobile connect to console'. I've been fiddling with this for the past few days and wanted to share my experience. I say experience because I haven't reallydone
anything to achieve a /console connection with RDP mobile.

I'm running WinMo 6.5 Pro and using the standard RDP client it ships with. I am connecting to my home PC, which is running Win7x64 Ultimate. If I choose to log in as a currently logged in user and provide the proper credentials, I am connected to the existing
session without any hassle.

I don't know if this is a new feature of terminal services/remote desktop on Win7, or a designed advantage of the mobile RDP client.