2012 server, pointing to the posts date, supports TLS But does it also apply to 2012R2? Out of TLS 1.0 and TLS 1.2 - TLS 1.0 is the only one mentioned.Īt the same time though, this blog: - seems to indicate that RDP on at least Win. But I find it quite hard to get a solid understanding on how things exactly are.įor example: (v=ws.10).aspx - applies to Win. In order to understand possible scenarios and what RDS in Win. Correct?Ĭrawled through forums, Wikipedia, blogs and search-machine results. Therefore the same certificate would have to support SHA1, as the communication with a TLS 1.0 client would require SHA1. If TLS 1.2 isn't manually enabled on, let's say a Windows 7 client, would the RDS server and the client be able to negotiate the use of TLS 1.0 instead - now that the certificate is SHA256? Because as I understand it, SHA256 is not supported by TLS 1.0. Would it be necessary to manually enable TLS 1.2 on these clients, in order for them to be able to negotiate the use of TLS 1.2? But am I right that clients ranging from Windows XP SP3 up to Windows 8.1 supports this scenario? So I could buy a certificate that uses the SHA256 hash algorithm. That TLS 1.2 is supported and enabled by default on Windows Server 2012R2. I'm becoming increasingly confused on how well, and exactly under what requirements Windows Server 2012 R2 running the RDS role, supports the use of TLS 1.2 with clients ranging from Win. Hi fellow Remote Desktop Services admins,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |