Forum Discussion
Feb 20, 2018
It seems that Microsoft Server 2016 isn't supported yet. See section 'Remote Desktop Gateway Compatibility Matrix':
However, I found this post. Seems like a registry change under Microsoft Windows Server 2016 could solve the problem.
https://devcentral.f5.com/questions/windows-server-2016-rdp-from-apm-53075
We found out that we need to change a registry key on any windows 10 or windows server 2016
Navigate to this Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
Change “SecurityLayer” to a zero
It seem that the F5 Big-Ip act as a really old rdp client and it's blocked by Windows 10 or Windows Server 2016 even if on the GUI it's allowing connection from an older RDP client.