On average, 150-200 MB of memory is required for one user session, without taking into account the launched apps.

Microsoft’s logic is simple: if you need a Remote Desktop server – buy a Windows Server license, RDS CALs, install and configure the Remote Desktop Session Host (RDSH) role.įrom a technical point of view, any Windows version with a sufficient amount of RAM can support simultaneous operation of several dozens of remote users. Therefore, this restriction does not allow to create a terminal RDP server based on the workstation that can be used by multiple users. A remote RDP session will be also forcibly terminated if the user will try to log locally.Īctually, the number of simultaneous RDP connections is limited rather by the license (then by any technical aspect).

If there is a user who works on the console of the computer (locally), then when you try to create a new remote RDP connection, the console session will be terminated.

When you try to open a second RDP session, the user is prompted to close the existing connection.

Only one simultaneous RDP connection is supported.

In Windows 10 Home editions, the incoming remote desktop connections are forbidden at all (you can solve this only using the RDP Wrapper Library).

RDP access feature supported only in higher Windows editions (Professional and Enterprise).

Let’s consider the main restrictions of the Remote Desktop Service usage on Windows 10 (and all previous desktop Windows versions): If you continue, they’ll be disconnected. If you try to open a second RDP session, a warning appears asking you to disconnect the first user session.Another user is signed in. But there is a restriction on the number of simultaneous RDP sessions – only one remote user can work at a time. Remote users can connect to their Windows 10 computers through the Remote Desktop Services (RDP) running on the Pro and Enterprise editions (but not on Home/Single Language).

Multiple rdp sessions