-
Titre
How to configure TLS 1.2 for Migration Manager for Exchange 8.15.9.x -
Description
Although it is discourages by Microsoft to explicitly set TLS version in .Net code for modern frameworks, there is some handshake issue with the TLS .NET code is being called from MMEX. Auto negotiation for TLS version does not work unless the specific registry values are set according to MS article: https://learn.microsoft.com/en-us/dotnet/framework/network-programming/tls#systemdefaulttlsversions.
-
Cause
TLS 1.2 is require for Migration Manager for Exchange 8.15.9.x -
Résolution
The following Registry keys need to be created and/or modified per the Microsoft Documentation to force TLS 1.2 on the MMEX console.
[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
[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
Once each key has been created, or updated, a system restart is required.