Otherwise, you can inadvertently orphan them. With the patch installed, create the following registry values:Įnable these settings on all clients running earlier versions of Windows before enabling TLS 1.2 and disabling the older protocols on the Configuration Manager servers. For these earlier versions of Windows, install Update 3140245 to enable the registry value below, which can be set to add TLS 1.1 and TLS 1.2 to the default secure protocols list for WinHTTP. Windows 8.1, Windows Server 2012 R2, Windows 10, Windows Server 2016, and later versions of Windows natively support TLS 1.2 for client-server communications over WinHTTP.Įarlier versions of Windows, such as Windows 7 or Windows Server 2012, don't enable TLS 1.1 or TLS 1.2 by default for secure communications using WinHTTP. NET Framework to support TLS 1.2įor more information about dependencies for specific Configuration Manager features and scenarios, see About enabling TLS 1.2. Ensure that TLS 1.2 is enabled as a protocol for SChannel at the operating system level.There are three tasks for enabling TLS 1.2 on clients: When enabling TLS 1.2 for your Configuration Manager environment, start by ensuring the clients are capable and properly configured to use TLS 1.2 before enabling TLS 1.2 and disabling the older protocols on the site servers and remote site systems.
Applies to: Configuration Manager (Current Branch)
0 kommentar(er)
