User connection fails when many connections are made to Windows Server 2012 R2-based RD Connection Broker

This article describes a hotfix for Remote Desktop Connection Broker (RD Connection Broker) in Windows Server 2012 R2. Before you install this hotfix, check out the Prerequisites section.
About this hotfix
This hotfix contains the following improvements:
  • Improves the number of successful user connections when many user connections are coming in (especially in peak logon periods).
  • Decreases CPU usage on SQL Server that's used in a High Availability-based Connection Broker deployment.
  • Optimizes the number of SQL calls that are invoked by Connection Broker when it processes RD user connections.
This hotfix improves the overall performance of the Connection Broker by being able to scale more user connections that typically occur during peak logon periods.

This hotfix applies to both RD Session Host and Virtual Desktop Infrastructure (VDI)-based deployments.
Issues fixed in this hotfix
If there's a significant high number of remote desktop connections that are made to a High-Availability RD Connection Broker in a short duration of time, you may encounter the following issues:
  • The connections experience long delays, or users are never connected to the system.
  • High CPU usage on SQL Server that's used with High Availability-based Connection Broker.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
File Information
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

Windows Server 2012 R2

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

Notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.3.960 0.18xxxWindows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes aren't listed, are signed with a Microsoft digital signature.
x64 Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Cbclient.dll6.3.9600.1806434,30424-Sep-201517:16x64
Sdclient.dll6.3.9600.18068244,22430-Sep-201513:59x64
Tssdjet.dll6.3.9600.18068109,56830-Sep-201513:59x64
Terminalserversessiondirectoryrole.cmdNot applicable24318-Jun-201314:57Not applicable
Tssdis.exe6.3.9600.18068807,42430-Sep-201513:59x64
Tssdis_migplugin.dll6.3.9600.18068154,62430-Sep-201513:59x64
Tssessiondirectory.events.xmlNot applicable58718-Jun-201314:57Not applicable
Rdcentraldbplugin.dll1.0.0.11,552,89630-Sep-201513:49x64
Rdcmsdbverify.dll1.0.0.192,16024-Sep-201517:58x64
Rddbobjectfactory.dll1.0.0.190,11230-Sep-201513:59x64
Rdmanagement.mofNot applicable27,00318-Jun-201314:50Not applicable
Rdmanagementuninstall.mofNot applicable56018-Jun-201314:50Not applicable
Rdms.dll6.3.9600.18068700,92830-Sep-201513:59x64
Cbclient.dll6.3.9600.1806424,06424-Sep-201516:48x86
Sdclient.dll6.3.9600.18068204,80030-Sep-201513:57x86
Tssdjet.dll6.3.9600.1806889,08830-Sep-201513:57x86

Additional file information

x64 Windows Server 2012 R2
File propertyValue
File nameAmd64_7c54f977ff43eb2287aea1fad6d9e3cd_31bf3856ad364e35_6.3.9600.18068_none_757509f6a2e3b0bc.manifest
File versionNot applicable
File size713
Date (UTC)30-Sep-2015
Time (UTC)21:19
PlatformNot applicable
File nameAmd64_c0889e59bb6e5ab07d3592a8e1482f3e_31bf3856ad364e35_6.3.9600.18068_none_f05f3e3e10a5867b.manifest
File versionNot applicable
File size732
Date (UTC)30-Sep-2015
Time (UTC)21:19
PlatformNot applicable
File nameAmd64_f8657260058b10c7a8033a881946e68d_31bf3856ad364e35_6.3.9600.18068_none_e7cc2a897af802dd.manifest
File versionNot applicable
File size730
Date (UTC)30-Sep-2015
Time (UTC)21:19
PlatformNot applicable
File nameAmd64_fcedf87dfcbb767e41e2bd22243515f9_31bf3856ad364e35_6.3.9600.18068_none_98c867d590e3966c.manifest
File versionNot applicable
File size732
Date (UTC)30-Sep-2015
Time (UTC)21:19
PlatformNot applicable
File nameAmd64_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.3.9600.18068_none_f43c6f304d0a8c19.manifest
File versionNot applicable
File size39,205
Date (UTC)30-Sep-2015
Time (UTC)15:43
PlatformNot applicable
File nameAmd64_microsoft-windows-t..iondirectory-server_31bf3856ad364e35_6.3.9600.18068_none_e4543b9ea707749f.manifest
File versionNot applicable
File size85,259
Date (UTC)30-Sep-2015
Time (UTC)15:43
PlatformNot applicable
File nameAmd64_microsoft-windows-terminalservices-rdms_31bf3856ad364e35_6.3.9600.18068_none_d6bbf36b5bbae904.manifest
File versionNot applicable
File size15,781
Date (UTC)30-Sep-2015
Time (UTC)15:43
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,509
Date (UTC)30-Sep-2015
Time (UTC)21:19
PlatformNot applicable
File nameX86_microsoft-windows-t..iondirectory-client_31bf3856ad364e35_6.3.9600.18068_none_981dd3ac94ad1ae3.manifest
File versionNot applicable
File size39,163
Date (UTC)30-Sep-2015
Time (UTC)15:18
PlatformNot applicable
Properties

Article ID: 3091411 - Last Review: 11/11/2015 00:27:00 - Revision: 1.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation

  • kbqfe kbsurveynew kbfix kbautohotfix kbhotfixserver kbexpertiseinter KB3091411
Feedback