Remote Desktop Session (RDP): how to make sure that a duplicate connection is not thrown out?

Question

System administration

Good time friends!

There is a terminal server based on a converted Windows 7, 10 RDP users have been created. Accounts are provided to a large number of individuals who from time to time connect to them and use the software on the server.

The problem is that if some user takes from the list of accounts and enters under it, if this account is already used by another user, that user is thrown out of the session.

How to make it so that when trying to authorize using an RDP account, if it is already in use at the moment, the user does not connect to the slave. table, but did you see a warning about the account being busy? And the user currently working in the session continued to work until he completed it himself, without throwing it away.

Answer 1

Is it possible to take organizational measures: either create as many accounts as there are users, or create the 11th service account.
The user logs into the service account and sees in the Task Manager which "work" accounts are busy. Turns off and enters free.

Answer 2

Create accounts according to the number of users.

Answer 3

Make at the level of Group policy of group local policy to enter several accounts.
To do this, you go to the server > start > cmd prompt and there you type gpedit.msc
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections -> Restrict Remote Desktop Services users to one Remote Services session Desktops
For English version
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections -> Restrict Remote Desktop Services users to a single remote session