Experience tab called Detect connection quality automatically. If selected, it
will detect the connection speed and auto select the approriate connection-quality features accordingly. Although this is a good idea, it's not always practical or
My scenario is that we push out a 'master' RDP file using group policy to all our users for connecting to our RDS Servers. The master RDP file is created using an older RDP shell and configured to 'LAN' connection speed on the experience tab. However we found that when this RDP file was pushed out to clients with RDP 8.0, it didn't set it to 'LAN' but instead 'Detect connection quality automatically'.
Although it enabled most connection-quality features, it did not auto detect the
connection as LAN speed, and therefore did not apply RemoteFX for the session.
The users therefore saw a drop in performance, particularly when watching videos and usability of PDF files.
You can check if the session has RemoteFX enabled in the event logs of the RDS Server.
Application and Service Logs >
RemoteDesktopServices-RemoteDesktopSessionManager > Admin
Why wasn't it auto detecting the connection speed as LAN (10mbps or higher) when I was actually connecting to an RDS Server on the LAN via a 100mbps switch? Couldn't quite work that out...
I even used iPerf (a download) and ran iperf -s (on the RDS Server) and iperf -c <ip address of RDS Server> (on the client) to find out the avaliable bandwidth between the two, which was infact 85mbps (8.5 x faster than the minimum required for LAN connection).
To resolve, I had to edit the RDP file that we pushed out to the clients. I opened up the master RDP file in notepad and added the following to the bottom of the file:
This will remove the 'Detect connection quality automatically' option from RDP
connections with RDP 8.0 and ensure it is always set to LAN (or which other experience option you specifically set in your RDP file - also set in the file as connection type:i:6)