Limit connected users
GARCIREPROMA opened this issue · 25 comments
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
You need more RAM obviously.
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
For now I can't check this use case, because I don't own any machines with such configuration.
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
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.
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?
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.
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.
RDPWrap-v1.6.1.zip was used for Windows 10 VM and no RDPWrap for Windows Server 2016.
@binarymaster @kmeaw Should this be closed then? The original problem may not exist but was thought to due to the test environment needing to initialize all of the logged in but newly created users at the same time.
@R030t1 Yep, I think this can be closed, since link to the issue is included in README.
The main problem could rely on the NT SMSS + CSRSS / client-server session architecture. Roughly speaking, each session is the process of queue messaging between kernel-mode Win32k and user-mode applications. If there are too many sessions, this would lead to high CPU load, up to the Denial of Service (hanging).
Hi i am facing some issue with my win 10 as i installed RDP Wrapper v-1.6.2 it is allowing only one user at a time either admin or either user i am not able to use as a multiple user server & also showing in RDP Conf as not supported.
plzzz help me out in this any one guys!!
Thanks
Same problem here. Installed Windows updates from the last 12 months and now only one connection at the same time is allowed. before the updates I did not have any issues at all.
I've just recently build a Ryzen 7 2700 with 16GB of ram. windows 10 pro 1809 17763.292.
people can get up to 15 active client but...
I cant seem to get my 10th user to log in and 9th if the user is new and was prompt to fill privacy settings page, assume thats was system and it also needs to be active to do its job.
Even if the users got disconnected not sign out yet the 10th user still cant log in, unless i went to task manager and start to forcing disconnected user to sign out.
I've tried going to
gpedit.msc
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections\Limit number of connections
enable it and set it to max at "999999" but still nothing.
i do hope i can get more active session. it's a server I've prepare for my students to do homework.
I face the same problem with more than 15 users connected.
I noticed that Remote Display Adapter drivers fail.
I disabled GPU acelération using gpedit.msc :
Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment.
I set the following policies to Disabled, to disable the use of the AVC/H.264 codec :
Configure H.264/AVC hardware encoding for Remote Desktop connections
Prioritize H.264/AVC 444 Graphics mode for Remote Desktop connections
For now It seems to work however it uses much more CPU.
"Nom du journal :System
Source : Microsoft-Windows-DriverFrameworks-UserMode
Date : 23/09/2019 10:43:12
ID de l’événement :10110
Catégorie de la tâche :User-mode Driver problems.
Niveau : Critique
Mots clés :
Utilisateur : Système
Ordinateur : XXXXXXXXXXXX.XXX
Description :
Un problème s’est produit avec un ou plusieurs pilotes mode-utilisateur et le processus hôte a été arrêté. Par conséquent, l’accès aux périphériques peut être momentanément interrompu.
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2e35aaeb-857f-4beb-a418-2e6c0e54d988}" />
<EventID>10110</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2019-09-23T08:43:12.782223100Z" />
<EventRecordID>47571</EventRecordID>
<Correlation />
<Execution ProcessID="132" ThreadID="1088" />
<Channel>System</Channel>
<Computer>win10srv.pag.lan</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UMDFHostProblem xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<LifetimeId>{a10ea718-42fe-4877-8f40-078363dd16fe}</LifetimeId>
<Problem>8</Problem>
<DetectedBy>2</DetectedBy>
<ActiveOperation>0</ActiveOperation>
<ExitCode>1879048193</ExitCode>
<Message>0</Message>
<Status>4294967295</Status>
</UMDFHostProblem>
</UserData>
</Event>"
I am also facing the same issue .... No one is able to login after 15 concurrent sessions.
The same problem here. Only 15 sessions.
Please note that RDP also consumes GPU memory. You should check the memory consumption of the graphics card so that it does not reach the limit (ex. with Process Explorer - Sysinternals).
I am not able to connect more then 5 users at same time.
I have 32 GB of RAM on my PC. More than 30 users are not allowed. I guess it's related.
i have a similar problem. since the same Windows 10 Pro 21H1 comp 19043.1288 i started to have problems... at first i had the exactly issue, but i updated the ini file and then the issue changed into the "your remote desktop services session has ended" for more than 2 users. all is green, the conection limit i already changed to 999999. but still my limit is 2. its not a matter of memory, it has 16GB and before this week i could have 8 sessions open. i am desperated i dont know what can i do, i tried almost everything
I have similar issue on the same hardware with 16GB RAM and i7 cpu with different windows 10 builds. For me Windows 10 pro 1809 64bit eng. (fresh install) last that has no limit in 7+ users. Next 1903, 1909, 2004 as i test not allow connect more than 7 concurrent RDP. When i try connect more, 8 session appear with login screen when enter passwd got black screen, next few sessions looks the same, from ~10 just timedout connection from client and newer get in. More to that to back to normal state we need reboot windows (logout not enough, maybe i need wait more that 5 min to try rdp again). I play with policy editor and registry to set near unlimited tcp sessions, but that not help at all. So issue still present when use new windows 10 builds and 7+ simultaneous RDP session.