Forum Discussion

Jdemers_204143's avatar
Jdemers_204143
Icon for Cirrus rankCirrus
May 01, 2017
Solved

Windows server 2016 RDP from APM

Hi,   we have been using remote desktop with the application access from our F5 device for a while. We never had any issues until we tried to add connections to some windows server 2016.   The ...
application delivery
BIG-IP
BIG-IP Access Policy Manager (APM)
  • Jdemers_204143's avatar
    Jdemers_204143
    May 02, 2017

    No need to go further.

     

    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.

     

Jdemers_204143's avatar
Jdemers_204143
Icon for Cirrus rankCirrus
May 02, 2017

No need to go further.

 

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.

 

Zuke_254875's avatar
Zuke_254875
Icon for Altostratus rankAltostratus
May 30, 2017

Jdemers, what health monitor do you use for your Windows Server 2016 pool? I'm currently using a standard TCP monitor, but I'd prefer something that was more robust and indicative of the service working. The deployment guides and iApp only list Server 2008/2012/2012R2.