As we’ve discussed previously on this blog, we discovered a bug in Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2 some time ago that prevented our software from being able to calculate RDP bandwidth used per RDS user and per RDS session on these operating systems. We kept an eye on it and along the way provided an update on the issue with calculating RDP bandwidth.
A Hotfix From Microsoft
Microsoft worked diligently with us in 2014, and by the end of that year, had released two hotfixes (one for Windows 8 and Windows Server 2012, the other for Windows 8.1 and Windows Server 2012 R2). These hotfixes are now available for download.
UPDATE: Now, in 2016, these hotfixes have been incorporated into updates for the above operating systems, particularly Windows Server 2012 R2. So, provided your systems are being routinely updated, these bandwidth counters should be functioning again.
Once you apply the above appropriate hotfixes (and/or updates) to your Terminal Server farm, you can then start leveraging Remote Desktop Reporter to track RDP bandwidth consumption in a variety of ways.
A New Family of Reports Targeting RDP Bandwidth
With the release of Version 3.0 of Remote Desktop Reporter, we offer a new RDP Bandwidth report family – Bandwidth Consumption By User.
This new class of reports can aggregate all of the RDP bandwidth usage by individual users across multiple servers by day, by week, or even by month. It’s great to quickly pinpoint users that are most expensive in terms of the bandwidth they consume. This information also can be useful for MSPs who need to meter bandwidth usage by their clients.
As with all Remote Desktop Reporter reports, it’s easy to filter by user(s), server(s), and/or date and time.
Get Started Today Tracking RDP Bandwidth
So, what are you waiting for? Apply the hotfixes/updates to your Windows 2012 servers, and then start a monthly subscription of our Remote Desktop Commander Suite for only $9 per server per month. In addition to the RDP bandwidth reports above, you will have complete visibility into user activity on your terminal servers, whether it be CPU consumption, memory consumption, session recordings, user time tracking, or even RDP latency/connection quality.