Limit connected users

[GARCIREPROMA]

I have installed and working correctly rdp wrapper. My problem is that when the user limit of 15 is reached, it no longer lets more users connect. What I can do? Sorry for errors in writing, I'm Spanish and I'm using the translator. regards

[binarymaster]

You need more RAM obviously.

[GARCIREPROMA]

Thank you very much for your response and help. I do not think it's RAM problem, I have 16 GB installed:

I have tried removing a memory card and left the computer in 8 GB. And still connect fifteen users (obviously the computer goes slower, but connect the same users as with 16 gb). Please help. Thank you very much

[binarymaster]

For now I can't check this use case, because I don't own any machines with such configuration.

[GARCIREPROMA]

Excuse me for opening another issue, but I did not know how to reopen the previous one. I had forgotten to comment that the connections I am making by remoteapp (I do not know if it will have something to do with this). Any help on your part or any user will be very welcome. Thank you very much for everything

[jerasa]

I can confirm that the 15-18 connection limit is present, regardless of the amount of RAM installed. OS is Windows 10 Enterprise version 1607 (build 14393.693).
The system allows more users to log in, but the sign itself takes a long time, while other users desktop becomes almost unusable slow.

[kmeaw]

Would granting access to a VM with 16G ram help solving this issue?

Please excuse the speculation, but the limit of 15 (or in one user's case, 18) may still be due to resource exhaustion. Unfortunately I'm unsure what resource Windows would be checking for. It may be performing timing tests or some read or write may be timing out.

If anyone has access to Windows Server (there is a 180 day evaluation available with registration) and can free up a normal desktop to run it and test the behavior when around 15 users are active I suspect that would provide valuable information. Otherwise, more people pushing the limit would help, to see if it really is a hard limit of 15 or if most hardware tends to max out at 15.

It seems unlikely that there is a second check for a desktop license somewhere in the terminal server code. It is more likely there is some quality of service check, depending on something relatively obscure.

@jerasa You are able to have more people log in past the 15-18 limit however all sessions become very slow, correct?

[kmeaw]

Just installed a Windows VM: https://kmeaw.com/img/multiuser.png
On one vCPU is it slow as hell, but it works with 20 remote users logged in simultaneously.
Task manager shows 4G RAM used.
It is Windows Server 2016 installed from this ISO: http://care.dlservice.microsoft.com/dl/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO
After 10 minutes CPU utilization went down and VM performance went normal — it seems an effect of a first login of 20 new users requiring to set up a fresh user profile directory and execute RunOnce tasks.

It looks like Windows Pro and Home versions do something different than Windows Server. Re-running the test on a desktop version is probably worthwhile to see if the slowdown @GARCIREPROMA and @jerasa experienced wasn't just due to RunOnce tasks and user setup.

If the slowdown wasn't due to user setup, then I admit to having no good information to go on. A guess would be to debug termsrv.dll on Windows Server and see where it branches out to and how execution differs from professional and home versions.

[kmeaw]

Windows 10: https://kmeaw.com/img/multiuser10.png
Without rdpwrap I had 18 clients displaying that I cannot log in. Installing rdpwrap fixed the problem: all users can log in retaining the console session for administrator.
4.7G RAM used for this experiment.