Incorrect TLS is displayed when you use RDP with SSL encryption
This article provides a solution to an issue where SSL (TLS 1.0) is displayed as the Security Layer protocol instead of the actual TLS 1.2 protocol.
Applies to: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019
Original KB number: 3097192
Consider the following scenario:
- You have a computer that's running Windows Server operating system.
- You have the Remote Desktop Connection Broker (RDCB) role configured on this computer.
- You try to secure the RDP connections to the target computers by using SSL encryption (Transport Layer Security (TLS)).
In this scenario, you may notice that the Security Layer list displays SSL (TLS 1.0), even though it's actually using TLS 1.2:
You may also notice similar behavior when you try to configure the Security Layer settings by applying the following Group Policy setting:
Require use of specific security layer for remote (RDP) connections
You can find this setting in the following location:
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
This issue is caused by a bug in the Windows Server GUIs. You can safely ignore the TLS version that's displayed in the GUI because this does not reflect the version of TLS that's being used for client connections.
The following required hotfix introduces support for TLS 1.2 on a Windows Server 2008 R2 Session Host server. This fix complies with recent PCI DSS security standards.
3080079 Update to add RDS support for TLS 1.1 and TLS 1.2 in Windows 7 or Windows Server 2008 R2
If the client machine is running Windows 7, it must have the RDC 8.0 update installed in order to use TLS 1.2. Without the RDC 8.0 update, the Windows 7 client can only use TLS 1.0.