However, please DO NOT post a request for troubleshooting by using the comment tool at the end of this post. Note: Questions and comments are welcome.
#Windows server 2016 remote desktop slow full#
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. For the hotfix itself and for more information, see the KB article We are excited to also share these improvements with you for use on your Windows Server 2012 R2 Remote Desktop Services deployments. The console or some other programs can be started using the Taskmanager but explorer. The task manager can be started with Ctrl-Alt-End. 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. On a Windows Server 2016 with RDP role sometime when a user may log on remotely via the remote client, he lands on a black screen. We also see similar improvements through internal testing of the end to end connection scenario via the Windows RD client (MSTSC).ġ00% connection success with initial burst of 100 connections at a rate of 2 connections per secondĠ.2 second average connection time through RD Connection Broker, down from over a minuteġ00% success adding/restarting servers at rate of 1 server per second with 5 sessions per serverĢ second average add/restart time, down from over thirty minutesġ00% connection success at a rate of 100 connections per minuteĢ5 second average connection time, down from over seven minutes 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.
In particular, we have made changes to the connection-handling logic of the RD Connection Broker to significantly improve the performance.
I am writing to let you know of performance improvements we have made to the Remote Desktop (RD) Connection Broker in both Hi everyone, this is Christian Montoya from the Remote Desktop team.
First published on CloudBlogs on Dec 15, 2015
0 kommentar(er)
