Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Licensing report file is corrupted in Windows Server 2012 R2 RDS environments for large report files


View products that this article applies to.

This article describes an issue in which the licensing report file that you generated is corrupted and has a wrong name in Windows Server 2012 R2 Remote Desktop Services (RDS) environments. A hotfix is available to fix this issue. Before you install this hotfix, see the Prerequisites section.

↑ Back to the top


Symptoms

This issue occurs when you use a Remote Desktop Licensing Manager tool to generate reports, and the size of the report file is greater than 4 kilobytes (KBs).

↑ Back to the top


Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.


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, install update 2919355 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.

↑ Back to the top


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
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.17 xxxWindows Server 2012 R2RTMGDR
    6.3.960 0.18 xxxWindows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed 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 are not listed, are signed with a Microsoft digital signature.
x64 Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Lserver.dll6.3.9600.18047747,52003-Sep-201516:31x64
Tlsrepplugin.dll6.3.9600.17415100,35229-Oct-201402:02x64
Tlsunattend.exe6.3.9600.1741510,75229-Oct-201402:42x64
Tslicensing.events.xmlNot applicable54918-Jun-201314:47Not applicable

Additional file information
x64 Windows Server 2012 R2
File propertyValue
File nameAmd64_40ff5f4d18b1ef11f0d75be8506e0867_31bf3856ad364e35_6.3.9600.18047_none_0f4542660f719d57.manifest
File versionNot applicable
File size722
Date (UTC)04-Sep-2015
Time (UTC)06:16
PlatformNot applicable
File nameAmd64_microsoft-windows-t..vices-licenseserver_31bf3856ad364e35_6.3.9600.18047_none_92344e24725c5b49.manifest
File versionNot applicable
File size95,247
Date (UTC)04-Sep-2015
Time (UTC)06:16
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,604
Date (UTC)04-Sep-2015
Time (UTC)06:16
PlatformNot applicable

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kb, kbqfe, kbsurveynew, kbfix, kbexpertiseadvanced, kbautohotfix, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 3092695
Revision : 1
Created on : 1/7/2017
Published on : 11/4/2015
Exists online : False
Views : 198