![]() New-ItemProperty -Path "$HklmSoftwarePath\Policies\Microsoft\Cryptography\Configuration\SSL\00010002" -Name "Functions" -PropertyType String -Value ("TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384") You can also add these cipher suites by directly editing the registry settings. Make sure that you list your current cipher suites and prepend any missing from the following list: How to enable TLS 1.2 on the site servers and remote site systemsĬipher Suites: Specifically Configuring TLS Cipher Suite Order ![]() If you want to set system-wide TLS 1.2 for your environment, follow the guidelines in these documents: To set TLS 1.2 for the current PowerShell session, type: $TLS12Protocol = 'Ssl3, Tls12' Configure TLS 1.2 for current PowerShell sessionÄo the following steps to configure TLS 1.2 on your client. ![]() The guidelines provided here are based on testing performed on a client running Windows Server 2016. This article provides resources and guidelines to configure TLS 1.2 on your Windows client. If you are using a Windows client to access your Azure Stack Edge Pro device, you are required to configure TLS 1.2 on your client. APPLIES TO: Azure Stack Edge Pro - GPU Azure Stack Edge Pro 2 Azure Stack Edge Pro R Azure Stack Edge Mini R
0 Comments
Leave a Reply. |