Hi @Rafael Komatsu
This thread discussed the same issue as yours, please check the solution below: Exchange 2013 e-Discovery not working after disabling TLS 1.0 and 1.1
Add the following registry keys to make WinHTTP and .NET Framework use TLS 1.2
ENABLING TLS 1.2 ON EXCHANGE SERVER 2013 & 2016
WinHTTP:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
“DefaultSecureProtocols”:dword:00000a80
2. HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
“DefaultSecureProtocols”:dword:00000a80
.NET Framework:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
“SystemDefaultTlsVersions”=dword:00000001
2. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
“SystemDefaultTlsVersions”=dword:00000001
I used IISCrypto to disable TLS 1.0/1.1 and enable TLS 1.2 on my Exchange server, after that, when I performed an eDiscovery search by EAC or the command "New-MailboxSearch" in EMS, I got a similar error. Finally, I tried to enable TLS 1.2 for WinHTTP and .NET Framework, after rebooting my server, eDiscovery can work without any error in EAC and EMS.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.