Īccording to the response from Microsoft from 2017 it should work, but as others already pointed out it still doesn't because of the windows internal database being TLS 1.0 only. Therefore my question: Is it possible to configure the windows internal database to use tls 1.2 and how is that done?Įdit: There is even a UserVoice Entry. For now we have re-enabled tls 1.0 on the remote desktop connection broker, but we need to disable it again or we will not pass the certification. ![]() We're only allowed to use modern protocols like tls 1.2 or tls 1.3, therefore we've disabled all others within schannel. The windows internal database and therefore also the remote desktop connection broker do *not* support anything newer than tls 1.0. ![]() This post will walk through the steps required to force TLS encryption on all RDP connections. In a shocking oversight this connection does not use strong encryption by default. After downloading and installing the update these protocols can be enabled by setting the registry keys described in KB4019276. Forcing RDP to use TLS Encryption Windows Remote Desktop Protocol (RDP) is widely used by system administrators trying to provide remote operators access. ![]() ![]() For compliance reasons we've to disable tls 1.0 on our systems and thereby encountered an unexpected error. For application compatibility purposes, these protocols will be disabled by default in a manner similar to the TLS 1.1/TLS 1.2 support that was disabled by default in Windows 7 and Windows Server 2008 R2.
0 Comments
Leave a Reply. |