How to enable TLS 1.2 on the site servers and remote site systems

Applies to: Configuration Manager (Current Branch)

When enabling TLS 1.2 for your Configuration Manager environment, start by enabling TLS 1.2 for the clients. Then, enable TLS 1.2 on the site servers and remote site systems. Finally, test client-to-site system communications before potentially disabling the older protocols on the server side. The following tasks are needed to enable TLS 1.2 on the site servers and remote site systems:

• Ensure that TLS 1.2 is enabled as a protocol for SChannel at the operating system level
• Update and configure the .NET Framework to support TLS 1.2
• Update SQL Server and client components
• Update Windows Server Update Services (WSUS)

For 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

For the most part, protocol usage is controlled at three levels, the operating system level, the framework or platform level, and the application level. TLS 1.2 is enabled by default at the operating system level. After you ensure that the .NET registry values are set to enable TLS 1.2 and verify the environment is properly using TLS 1.2 on the network, you might want to edit the SChannel\Protocols registry key to disable the older, less secure protocols. For more information about disabling TLS 1.0 and 1.1, see Configuring Schannel protocols in the Windows Registry.

Update and configure the .NET Framework to support TLS 1.2

Determine .NET version

First, determine the installed .NET versions. For more information, see Determine which versions and service pack levels of .NET Framework are installed.

Install .NET updates

Install the .NET updates so you can enable strong cryptography. Some versions of .NET Framework might require updates to enable strong cryptography. Use these guidelines:

• .NET Framework 4.6.2 and later support TLS 1.1 and TLS 1.2. Confirm the registry settings, but make no other changes.

  Note

  Starting in version 2107, Configuration Manager requires Microsoft .NET Framework version 4.6.2 for site servers, specific site systems, clients, and the console. If possible in your environment, install the latest version of .NET version 4.8.

• Update .NET Framework 4.6 and earlier versions to support TLS 1.1 and TLS 1.2. For more information, see .NET Framework versions and dependencies.

• If you use .NET Framework 4.5.1 or 4.5.2 on Windows 8.1, Windows Server 2012 R2, or Windows Server 2012, Microsoft recommends that you install the latest security updates for the .NET Framework 4.5.1 and 4.5.2 to ensure TLS 1.2 can be enabled properly.

  For your reference, TLS 1.2 was first introduced into .NET Framework 4.5.1 and 4.5.2 with the following hotfix rollups:

  • For Windows 8.1 and Server 2012 R2: Hotfix rollup 3099842
  • For Windows Server 2012: Hotfix rollup 3099844

Configure for strong cryptography

Configure .NET Framework to support strong cryptography. Set the SchUseStrongCrypto registry setting to DWORD:00000001. This value disables the RC4 stream cipher and requires a restart. For more information about this setting, see Microsoft Security Advisory 296038.

Make sure to set the following registry keys on any computer that communicates across the network with a TLS 1.2-enabled system. For example, Configuration Manager clients, remote site system roles not installed on the site server, and the site server itself.

Update the following subkey values for 32-bit applications that run on 32-bit operating systems and for 64-bit applications that run on 64-bit operating systems:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001

Update the following subkey values for 32-bit applications that run on 64-bit operating systems:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
      "SystemDefaultTlsVersions" = dword:00000001
      "SchUseStrongCrypto" = dword:00000001

Update SQL Server and client components

SQL Server versions currently supported by Configuration Manager support TLS 1.1 and TLS 1.2. Dependent libraries might still require updates. For more information, see KB 3135244: TLS 1.2 support for Microsoft SQL Server.

Secondary site servers need to use at least SQL Server 2017 Express with Cumulative Update 2 (CU2) or later.

SQL Server Native Client

Ensure you update the SQL Server Native Client to at least SQL Server 2012 SP4 (11.*.7001.0). This requirement is a prerequisite check (warning).

Configuration Manager uses SQL Server Native Client on the following site system roles:

• Site database server
• Site server: central administration site, primary site, or secondary site
• Management point
• Device management point
• State migration point
• SMS Provider
• Software update point
• Multicast-enabled distribution point
• Asset Intelligence update service point
• Reporting services point
• Enrollment point
• Endpoint Protection point
• Service connection point
• Certificate registration point
• Data warehouse service point

Enable TLS 1.2 at-scale using Automanage Machine Configuration and Azure Arc

Automatically configure TLS 1.2 across both client and server for machines that run in Azure, on-premises, or multicloud environments. To get started configuring TLS 1.2 across your machines, connect them to Azure by using Azure Arc-enabled servers, which comes with the Machine Configuration prerequisite by default.

After you connect, configure TLS 1.2 with point-and-click simplicity by deploying the built-in policy definition in Azure portal: Configure secure communication protocols (TLS 1.1 or TLS 1.2) on Windows servers. Assign the policy scope at the subscription, resource group, or management group level, and exclude any resources from the policy definition.

After the configuration has been assigned, you can view the compliance status of your resources by navigating to the Guest Assignments page and scoping down to the impacted resources.

For a detailed, step-by-step tutorial, see Consistently upgrade your server TLS protocol using Azure Arc and Automanage Machine Configuration.

Update Windows Server Update Services (WSUS)

WSUS supports TLS 1.2 by default on all currently supported versions of Windows Server.

To support TLS 1.2 in earlier versions of WSUS, install the following update on the WSUS server:

• For WSUS servers that run Windows Server 2012, install update 4022721 or a later rollup update.

• For WSUS servers that run Windows Server 2012 R2, install update 4022720 or a later rollup update.

Next step

• Common issues when enabling TLS 1.2