Remote Desktop client always reconnects to the first "disconnected" session

Dmytro Bezotosnyi 21 Reputation points
2022-10-07T08:44:16.323+00:00

We use the Multiple RDP Sessions by one user on the RDP Server. To do this, in Group Policies we:

  1. disable Restrict Remote Desktop Services user to a single Remote Desktop Services session;
  2. set RD Maximum Connections allowed to 999999 in Limit number of connections.

To allow users to reconnect to their session we set RDP's MaxDisconnectionTime to 120 sec, so that sessions remain active if they were terminated by network loss. If the user has lost the network, then during this time the session will be in the "Disconnected" status and the user will be able to connect to it. At first glance this seems to work fine. But there is a problem when several sessions with the "Disconnected" status hang, and if a new user connects at this time, then his RDP is redirected to the first (by ID) session with this status. Thus, the user is not in his session.

To reconnect to the correct session, we plan to use a reconnection cookie. This should help the user to reconnect into his session.

The question arises, how can we start exactly a new session so that it does not fall into one of the sessions with the "Disconnected" status?

We tried many options, including interactive logon, starting of the process in session with the interactive desktop, but all our attempts failed to create a new session -- session does not appear in the users list.

We will be grateful for any help.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Nesure Brown 0 Reputation points
    2023-06-14T10:19:15.3766667+00:00

    Anyone konws?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.