In two previous posts during 2014 (Part 1 and Part 2), we disclosed that due to the integration work related to RemoteFX technologies in Windows Server 2012, it was no longer possible to obtain RDP bandwidth information on a session by session basis on Windows Server 2012, Windows Server 2012 R2, Windows 8, and Windows 8.1.
Microsoft Generates Two Hotfixes
Fortunately, after our identification of this bug and follow-on advocacy, Microsoft agreed to generate two Hotfixes to restore this functionality. As a result, the first Hotfix was released and is available for download!
Note well that this first Hotfix only will work on the Windows Server 2012 and Windows 8 codebase. At the time of writing this article, a subsequent hotfix was to be released later for the Windows Server 2012 R2 and Windows 8.1 codebase.
The Symptoms . . .
In the article ID, Microsoft explains the symptoms corrected by this hotfix:
When you try to use the WTSQuerySessionInformation Remote Desktop Services API function to obtain information about incoming bytes (WTSIncomingBytes) or outgoing bytes (WTSOutgoingBytes) for a Remote Desktop session on Windows 8 or Windows Server 2012, the return value is always zero bytes.
Thanks Microsoft Support and Development Teams!
We’d like to give a hearty thanks to the support and development teams at Microsoft that made this happen. Good job, guys!
Remote Desktop Reporter Helps Gain Insight On RDP Bandwidth Consumption With Windows Server 2012
Given this hotfix, consider deploying our Remote Desktop Reporter tool to gain insight on RDP bandwidth consumption in your RDS farm and find out which users are the heaviest consumers.
Updated: October 2020.