This article describes an issue that typically occurs in a Remote Desktop License server that is running Windows Server 2012 R2 when there are multiple license servers in the deployment and during high load. Before you install this update, see the Prerequisites section.
When this issue occurs, clients can't connect to Remote Desktop Services (RDS) servers until the license services are restarted.
How to get this update
Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
Method 1: Windows UpdateThis update is provided as a Recommended update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.
Method 2: Microsoft Download CenterThe following files are available for download from the Microsoft Download Center:
For more information about how to download Microsoft support files, select the following article number to view the article in the Microsoft Knowledge Base:
|All supported x64-based versions of Windows Server 2012 R2||Download the package now.|
119591 How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Update detail information
PrerequisitesTo install this update, you should first install April 2014, update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) in Windows Server 2012 R2.
Registry informationTo apply this update, you don't have to make any changes to the registry.
Restart requirementYou may have to restart the computer after you apply this update.
Update replacement informationThis update doesn't replace a previously released update.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.