How to make sure that the active RDP session is not thrown out under the same profile by another person trying to log in?

Question

System administration

I mean, this is the situation.
Person 1 works on RDP. Person2 connects and Person1 flies out.
And it is necessary for Person2 to receive an error saying that it is busy if person1 is working.
Moreover, the rdp profile must always be logged in. That is, the programs in it should always work.
Please tell me where to find the checkbox.

Answer 1

Group Policy
"Limit the number of connections"

Determines whether the number of concurrent connections to the server is limited by Remote Desktop Services.
You can use this setting to limit the number of Remote Desktop Services sessions that can be active on the server. If this number is exceeded, new users will receive an error message when they try to connect, notifying them that the server is busy and advising them to connect later. Limiting the number of sessions improves performance because fewer sessions request system resources. By default, RD Session Host servers allow an unlimited number of Remote Desktop Services sessions, and Remote Desktop for Administration allows two Remote Desktop Services sessions.
To use this policy setting, specify the maximum number of connections for the server. To set an unlimited number of connections, enter the number 999999.
If the status is set to Enabled, then the maximum number of connections is limited to the specified number, according to the version of Windows and the mode of Remote Desktop Services running on this server.
If the state is set to Disabled or Not Configured, the connection limit is not enforced at the Group Policy level.
Note. This setting is intended for use on RD Session Host servers (that is, Windows-based servers with the RD Session Host role installed).

Answer 2

Option 1:
Edit the registry. Set
fSingleSessionPerUser = 0 in the branch HKLM\SYSTEM\ CurrentControlSet\Control\Terminal Server\fSingleSessionPerUser
After that, several RDP connections can be made to one user.
Option 2:
Use RDS shutdown (shadow connection)
Mstsc.exe [/shadow:sessionID [/v:Servername] [/control] [/noConsentPrompt]] on the client, but this method has many disadvantages:
1) Session someone must create in advance
2) For both clients, the screen resolution should be slightly larger than the resolution when creating the session (otherwise the font will decrease)
3) work correctly within the local network
4) No sound transmission
5) Requires preliminary configuration by the administrator

Answer 3

It will be the biggest mistake to create such a setup. Imagine that one person logged in to a PC and forgot where and when, or went home, but did not complete the session, he will no longer get to the server. It would be more correct to make a separate profile or allow parallel connections as described above by sashaqwert