On older Windows versions, you may additionally need the SCHANNEL settings. For PowerShell Scripts, like my PRTG script to check Office 365 services, setting the. Key 4: Finally you can enable TLS 1.1 and 1.2 in Internet Explorer:ĭepending on your needs, you may need to enable more than just one of the registry keys above. NET Framework (like PowerShell), use these settings (see Microsoft TLS best practice for. Key 2: To enable TLS 1.2 (and 1.1) as security provider for applications using WinHttp, apply the following registry settings: Key 1: To generally enable TLS 1.2 as client and server protocol, use the following registry keys: So if you still have trouble getting TLS 1.2 to work, here are some registry keys that will aid you. That is why I couldn’t reproduce the error mentioned above with my testing on Windows Server 2019.
Any currently supported Windows (Server) version – even Windows Server 2008 without R2 – should support modern TLS versions, most of them even out of the box. The easiest answer would be: Use a current Windows Version.
Having a closer look it turned out to be Microsoft restricting connections to Office 365 services to using only TLS 1.2. Just recently I got feedback about my PRTG script for monitoring Office 365 health suddenly stopped working.
0 kommentar(er)
