Complete script (run as admin): $suites = , It properly showed that 1.0, 1.1 and 1.2 were available for Windows Server 2012.Īdd the cipher suites for TLS 1.0/1.1. It says only TLS 1.2 is allowed both before and after the change.

(I also tried dword:00000001 instead of dword:ffffffff - no difference) I included this as a startup task such that necessary changes are imported into the registry. I found this answer which suggests that I change the registry keys Windows Server 2012 is configured such that IIS allows TLS 1.0, TLS 1.1 and TLS 1.2 by default but Windows Server 2019 has IIS configured to only allow TLS 1.2 This may break some of the clients so I'd like to temporarily enable TLS 1.0 and 1.1 in Windows 2019 and then later talk to the clients and disable all but TLS 1.2 NET Framework 4.7.2 and Windows Server 2019. NET Framework 4.5.2 and configured to run on Windows Server 2012. I have an ASP.NET MVC web service hosted in Microsoft Azure Cloud Services (as a web role) currently targeting.

.net app to test tls 1.2