Windows Server 2016 and introducing AVC 444 mode

With the upcoming release, Microsoft has been busy with adding alot of new features to the RDS platform. Like RemoteFX vGPU for GEN2 and for Server OS + GPU Passtrough and Server VDI etc.. But out the blue came this

Also Rachel Berry at Nvidia also blogged about the limitations on H.264 and 4:2:0 –> anyhow I was curious just how does this affect my RDP performance?

The Setup was pretty simple, either I can use it with RemoteFX vGPU or a plain virtual machine running 2016 TP4. I also require a Windows 10 with build 1511 or higher.

There are basically two policies that we can define


Now Prefer AVC hardware encoding, if you are using RemoteFX vGPU, the policy should be set on the Hyper-V host and not the RDS server itself.


After these settings are enabled and active, next time you try to connect to an RDP session you will see it triggers an event in the events log under RDS Applications and Services Logs -> Microsoft -> Windows -> RemoteDesktopServices-RdpCoreTS
Just need to reconnect after setting the policy


Profile: 2048 (Yep we are good)

Now I did a couple of tests, which were pretty simple to see the bandwidth usage, (Also to test the differences between RDS 2012 and 2016) which were running the same setup in policies just one was enabled with AVC 444 and the other wasn’t

This was a simple test of video transfer, the 1 line is RDS 2012 R2 and the below is running 2016 TP4 (almost 20MB lower bandwidth usage) wow!


Now I ran the same test again and I got similar results for 2012 R2, but this time I was running with AVC 444 mode enabled, which my initial guess would state that it used a bit more bandwidth


I also did a couple of more tests, but the conclusion was almost the same. Use of AVC 444 in video uses about 10% more bandwidth. I will need to test more to see how much better the graphics actually are.

Leave a Reply

Scroll to Top