This is true in Exchange Online and might be the case for on-premises too, depending on your configuration. Once the script completed, you can close PowerShell and restart the ShareGate migration tool (make sure you close the app from the system tray if it is active).įor more troubleshooting information, see Microsoft's article Authentication errors occur when client doesn't have TLS 1.2 support.# Enable TLS 1. Probably need to force PowerShell to use TLS 1.2. Según el artículo Configuración TLS-SSL, para que TLS 1.1 y 1. Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v9' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord Requirements Windows 7+ / Windows Server 2003+ PowerShell v2+ (Not PowerShell Core yet though)(minimum is v3 for install from this website due to TLS 1.2. Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v9' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord Please try the script below: # Set strong cryptography on 64-bit. Troubleshooting Force the newer version of TLS on your machineĪ PowerShell script from the Microsoft DevBlog that forces the newer version of TLS on your machine should resolve the connection issue. How to check for TLS1.2 Readiness on Azure DevOps Build/Release agents (Self hosted agents) Step 3: Add a Powershell task and choose the script as shown below. Microsoft deprecated TLS 1.0 and TLS 1.1, which can cause connection failures when using the app. Net.ServicePointManager::SecurityProtocol Net.SecurityProtocolType::Tls12. Force the newer version of TLS on your machine Fortunately the fix was easyonce you knew what it was.
0 kommentar(er)
