none
Disable/turn off concurrent Windows 7 remote desktop sessions/connections

    Question

  • Please could someone advise me where I can post the following question about disabling concurrent remote desktop connections to Windows 7?

    We have a number of workstations running Windows 7 Enterprise 64-bit. Our users can connect to these workstations via a remote desktop connection.

    If a user is connected and logged in to a workstation, and another user tries to connect, the following message is displayed and a connection is not established.

    ‘Logon Message
    Another user is currently logged on to this computer. If you continue, this user has to disconnect from this computer. Do you want to continue?’

    If a user is connected and logged in to a workstation, the user can disconnect their session and leave their processes/applications running. Another user is then able to connect and login to the workstation. If the disconnected session is using processor time, and other system resources, this has an impact on the connected user.

    We would like to achieve the following configuration. If a user connects to a workstation via remote desktop and disconnects their session, a second user is unable to connect. Preferably, the above message is displayed.

    I have reviewed the group policy objects to try and find a way to achieve this configuration. If the following group policy object is set to Enabled and 1, an error is displayed when a user attempts to start a second session on the workstation.

    Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections\Limit number of connections

    The following error is displayed when a user attempts to start a second session:

    ‘This computer can’t connect to the remote computer.
    Try connecting again. If the problem continues, contact the owner of the remote computer, or your network administrator.’

    This error simply tells the user that they cannot connect to the workstation, not that another session is preventing them from connecting. This error does not provide enough information to the user on why they cannot connect, and does not provide the option to log the other user off if we are unable to identify who is connected.

    If the following group policy objects are set to Enabled and 1 minute, the user’s disconnected session is deleted after 1 minute.

    Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits\Set time limit for disconnected sessions

    Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits\Terminate session when time limits are reached

    This configuration is unsuitable because it could result in a user losing their work, whether they disconnected intentionally or not.

    Any advice on how this configuration can be achieved would be much appreciated.

    Saturday, November 26, 2011 1:43 PM

All replies

  • Hi,

     

    If another use logon via remote desktop, the current would be prompted such as:

     

     

    And the current user could click Cancel to prevent another user logon. Then they would receive a message:

     

     

    “Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections\Limit number of connections

     

    The following error is displayed when a user attempts to start a second session:

     

    ‘This computer can’t connect to the remote computer.

    Try connecting again. If the problem continues, contact the owner of the remote computer, or your network administrator.’”

     

    Please understand this is by the design. In this case, the destination machine reject the RDC requires. But many other issue could cause this problem, such as network connect related issue. As a workaround, you could descript the error for these users, and let them know why it appears.

     

    However, if you want to feedback your opinion to Microsoft, you could submit your advice here:

    http://mymfe.microsoft.com/Windows%20%207/Feedback.aspx?formID=195

     

    Thanks for your understanding.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Monday, November 28, 2011 9:59 AM
  • Hi zhen tan,

    Thank you for your response.  However, the scenario you describe assumes that a user is connected to the workstation via RDC, and another user attempts to connect via RDC.

    The scenario I described assumes that a user connects to the workstation via RDC, disconnects the session (this is not the same as clicking log off).  The second user is able to connect to the workstation via RDC, and the first user's session is still running in the background.

    Ideally, I want the second user to be presented with a message saying that someone else is already connected to the workstation.

    Please let me know if this is still unclear.  Thanks.

    Monday, November 28, 2011 10:07 AM