Hi everyone, this is Christian Montoya from the Remote Desktop team. I am writing to let you know of performance improvements we have made to the Remote Desktop (RD) Connection Broker in both
Windows Server 2016 Technical Preview 4
and Windows Server 2012 R2 (with
In particular, we have made changes to the connection-handling logic of the RD Connection Broker to significantly improve the performance.
Internal testing of the RD Connection Broker connection-handling code shows a significant improvement during logon storms and when adding/restarting RD Session Host servers to a farm. We also see similar improvements through internal testing of the end to end connection scenario via the Windows RD client (MSTSC).
Specific results include:
100% connection success with initial burst of 100 connections at a rate of 2 connections per second
0.2 second average connection time through RD Connection Broker, down from over a minute
100% success adding/restarting servers at rate of 1 server per second with 5 sessions per server
2 second average add/restart time, down from over thirty minutes
MSTSC End to End
100% connection success at a rate of 100 connections per minute
25 second average connection time, down from over seven minutes
More scale testing is currently being done for the new RD Connection Broker in Windows Server 2016 and we hope to provide a white paper shortly. We are excited to also share these improvements with you for use on your Windows Server 2012 R2 Remote Desktop Services deployments. For the hotfix itself and for more information, see the KB article
We hope you will take full advantage of these significant improvements to the RD Connection Broker in Windows Server 2016 and Windows Server 2012 R2.
Note: Questions and comments are welcome. However, please DO NOT post a request for troubleshooting by using the comment tool at the end of this post. Instead, post a new thread in the
RDS & TS forum
. Thank you!