Windows 10: RDP had multiple active sessions

Hithe other day i had this unusual issue where a user was using RDP to connect to their work machine and instead of joining the existing session they had from a previous day it created a new one whilst also keeping the old one active, this prompted the user to select which session they wanted to join although upon reading the EULA and other forum posts this shouldn't have been possible. The user logged into the same remote computer as they usually do and signed in with the same set of user credentials both to create the initial session and the new session, Anybody have any ideas what caused th

:)

 

How do i configure multiple RDP sessions or Multiple concurrent user sessions in Windows 10 pro

i have a dell optiplex with pre-installed windows 10 opreating system , i need to setup multiple RDP sessions or Multiple concurrent user sessions in this computer , could you please anyone help me out of this , thanks

 

how to Allow Multiple RDP Sessions in Windows 10?

Good Day for all

Dears,

I have Windows 10 and I need a feature

multiple RDP (Remote desktop protocol) session in same time

How do I do this and work successfully because I tried many methods that did not work

 

Windows 10 1709; host sleeps during active RDP session

I am reporting a bug/oversight.

HOST OS:

Windows 10 64-bit Version 1709 (OS Build 16299.192)

HOST SETTING:

Set to sleep after 2 hours of inactivity

PROBLEM:

Host computer sleeps after 2 hours of inactivity even when a client is connected via RDP (Remote Desktop)

DESCRIPTION:

In previous versions of Windows and even in Win10 before the Fall Update an active RDP session has always prevented the host computer from entering a sleep state even when set to do so after X minutes of inactivity. Since the Fall Update the host computer
of an active RDP session will sleep during an active RDP session when there is lack of activity on the client computer. There should never be a reason for the host of an active RDP session to enter sleep mode when there is a client connected. If the client
computer is set to sleep after X minutes of inactivity it seems natural it should do so even during an active RDP session, but then, and only then, should the inactivity timer start for the host computer.

HISTORY:

There was a bug introduced in Remote Desktop sometime prior to Win10 Fall Update wherein a host computer would not sleep when set to do so after a period of inactivity after a client had connected and subsequently disconnected to the host via RDP. This
was finally fixed in Fall Update, but I have a sneaking suspicion the fix was too aggressive and this is what led to the problem I am reporting.

Sean