This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 66%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBK%3C/text%3E%3C/svg%3E)
I am creating an RDS deployment in a corporate domain. Servers are running Win2019 Standard Server Core in a Session-based desktop deployment. Server A is acting as RD Broker, RD Web Access, RD Gateway, RD License server, and RD Session Host to serve Collection A. Server B has the RD Session Host role to serve Collection B. The purpose of the deployment is to provide remote access to pools of Windows servers via RDC.
All configuration is complete with the servers assigned to their appropriate roles in the deployment. SSL certs are installed and trusted for our corporate domain; never any error/warning about certs during the connection process. I have 60 Per User CALs installed on Server A. Users connecting via RDWeb/RDC are having a CAL assigned and they are decrementing the CAL total as expected. The RD Session Hosts on Servers A and B both specify the License Server FQDN and licensing mode in the Remote Desktop Services\Remote Desktop Session Host\Licensing local group policy items.
Connections are showing up as expected in Server Manager and show the proper RDSH server assigned for each Collection. The collections are RemoteApp Program deployments. I have an instance of mstsc published for each remote desktop we wish to access specified using the /v argument.
The problem is that the 2 concurrent connection limit is still being enforced for all the clients we are connecting to. I would expect if the CALs were being applied properly that the limit would not be a problem. There is no problem detected in the Licensing Manager or Diagnoser on Server A. The local RDS groups on Servers A and B are populated as I would expect them to be. There is no global group policy being applied to the servers affecting the Remote Desktop Services policies. "Limit number of connections", etc. are all Not Configured.
I'm not sure what to look at next. Any suggestions are appreciated. Thanks for your time.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
problem is that the 2 concurrent connection limit is still being enforced for all the clients we are connecting to
Did you mean connecting from? Once the RDS role is added I wouldn't expect the two admin connections to work unless you happen to use the admin switch when connecting as in mstsc.exe /admin
Hello. Like you say, I would expect the RDSH to be the one managing the transaction, but to me it at least "looks" like it is the destination that is restricting the sessions. However, in this deployment of publishing mstsc instances, it is tough for me to be 100% sure who is considered the source of the session. To me, it appears that the destination is the one throwing this dialog not the RDSH.
I'd try working through this one.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/troubleshoot-remote-desktop-disconnected-errors
I figured it out. The problem is that the RDC destinations have no awareness of the RDS environment or the licensing since they did not have any RDS role. The CAL verification is performed by an RD Session Host so if your destinations are not RDSH then they will fall back on the 2 admin connections regardless of whether or not the user has a CAL assigned by the RDS license server.
In practice, I added the destination servers to the Server Manager on the RD Broker and installed the RDSH and RD License roles. The destinations are added to the RDS Overview as Session Hosts however they are not assigned to any RDS collection. These "hosts" are not actually hosting or providing any apps. They simply have the role to check in with the license server and allow multiple terminal connections.
Thanks.