Windows – How to stop a remote desktop session from ending

remote desktopwindows-server-2008-r2

We have Windows 2008 r2 servers running at the moment.

If I log into the server using remote desktop connection, and then someone else tries to log into the same server while I am working on it, I get thrown off the server and am displayed the following message:

Your Remote Desktop session has ended.

Another user connected to the remote computer, so your connection was
lost. Try connecting again, or contact your network administrator or
technical support group.

My question is, is it possible to configure the server to stop this from happening. So instead of kicking off the user who is already working on the server, stop the second user from connecting or allow both to connect at the same time?

Best Answer

The situation you described would only happen if the two users are using the same username or you have hit the maximum concurrent users for the server (however you said there are only 2 people involved and the error you had would not happen till a 3rd person logged on and you don't have terminal services licensing set up).

If you are having the "same username" problem the two ways to fix it are to have the users use separate usernames to log in or to allow a single user to have multiple sessions open.

If you are having the "maximum concurrent users" problem you need to purchase a terminal services license and enable it on the server.

Related Solutions

Windows – How to use the current credentials with Remote Desktop

Before you start, ensure that your server is configured to allow Single Sign-On (SSO). If you have a Remote Desktop Session Host, the Always Prompt for Password setting should not be set for the connection in Properties>Log on Settings and also on the General tab, the Security Layer should be set to Negotiate or SSL.

Also, SSO needs to be enabled on your local / domain policy. Check the value of Allow Delegating Default Credentials here in your GPO:

Computer Configuration\Administrative Templates\System\Credentials Delegation

Also ensure that your server (TERMSRV/) is added to the server list, if required. You may use wild card characters to add multiple server names

When you run the Remote Desktop Connection, you should tick the box for Allow me to save credentials.
enter image description here

You will then be prompted to enter your credentials. When you do so, ensure you tick the box for Remember my credentials. Your credentials should then be saved, and next time you log in it will be passed through.

enter image description here

Here is a link with some basic step by step instructions: http://itowns.blogspot.co.uk/2011/06/enabling-remote-desktop-connection.html

Windows 7 Remote Desktop Connection Save Credentials not working

i found the solution. It was at the same time both subtle, and obvious.

As mentioned in the question, when i was modifying the following Remote Desktop Connection Client Group Policy settings:

Prompt for credentials on the client computer
Do not allow passwords to be saved

i was checking them on the server:

enter image description here

i thought it would be the server that dictates what the client is allowed to do. Turns out that is completely wrong. It was @mpy's answer (while incorrect), which led me to the solution. i shouldn't be looking at the RDP client policy on the RDP server, i need to look at the RDP client policy on my RDP client machine:

enter image description here

On my client Windows 7 machine, the policy was:

Do not allow passwords to be saved: Enabled
Prompt for credentials on the client computer: Enabled

i do not know when these options were enabled (i did not enable them in recent memory). The confusing part is that even though

Do not allow passwords to be saved

is Enabled, the RDP client would still save password; but only for servers below Windows Server 2008.

The truth table of functioning:

Do not allow saved  Prompt for creds  Works for 2008+ servers  Works for 2003 R2- servers
==================  ================  =======================  ==========================
Enabled             Enabled           No                       Yes
Enabled             Not Configured    No                       No
Not Configured      Enabled           Yes                      Yes
Not Configured      Not Configured    Yes                      Yes

So there is the trick. The group policy settings under:

Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Remote Desktop Connection Client

on the client machine need to be configured with:

Do not allow passwords to be saved: Not Configured (critical)
Prompt for credentials on the client computer: Not Configured

The other source of confusion is that while

a domain Enabled policy cannot override a local Disabled
a domain Disabled policy can be overridden by a local Enabled policy

Which again leads to a truth table:

Domain Policy   Local Policy    Effective Policy
==============  ==============  ==============================
Not Configured  Not Configured  Not configured (i.e. disabled)
Not Configured  Disabled        Disabled
Not Configured  Enabled         Enabled
Disabled        Not Configured  Disabled
Disabled        Disabled        Disabled
Disabled        Enabled         Disabled (client wins)
Enabled         Not Configured  Enabled
Enabled         Disabled        Enabled (domain wins)
Enabled         Enabled         Enabled

Best Answer

Related Solutions

Windows – How to use the current credentials with Remote Desktop

Windows 7 Remote Desktop Connection Save Credentials not working

Related Question