Views:

To address the issue, check the following

TLS Version

 
The issue is encountered because the WFBS on-premise is using a different version of TLS. The WFBS-SVC Server only supports TLS 1.2.
 
  1. Check if the WFBS On-Premise Server is using TLS 1.2 for its protocols. To check, see registry hive below:
    DefaultSecureProtocols ValueProtocol Enabled
    0x00000008Enable SSL 2.0 by default
    0x00000020Enable SSL 3.0 by default
    0x00000080Enable TLS 1.0 by default
    0x00000200Enable TLS 1.1 by default
    0x00000800Enable TLS 1.2 by default
     
    For more information on updating the TLS version, refer to this Microsoft KB article: Enabling TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows
     
    • For 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\DefaultSecureProtocols
    • For 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\DefaultSecureProtocols
  2. Check if TLS 1.2 is enabled for both client and server. Change the following SCHANNEL registry hives to the indicated values below:
    Always back up the whole registry before making any modification. Incorrect changes to the registry can cause serious system problems.
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
      DWORD name: DisabledByDefault
      DWORD value: 0
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server
      DWORD name: DisabledByDefault
      DWORD value: 0
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
      DWORD name: Enabled
      DWORD value: 1
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server
      DWORD name: Enabled
      DWORD value: 1
  3. Alternatively, you may download and run IIS Crypto.
    • Click Best Practices.
    • Click Apply.
  4. Reboot the machine after making the changes.
  5. Run the migration tool again.


Download size error

When checking %temp%\wfbssvc_migration_toolkit.log, the actual size of the package from the WFBS-SVC server does not match the downloaded package.

[1020 : 1f10][OpenUrl] OpenURL https://wfbs-svc-dl-emea.trendmicro.com/filer/aal/packages/6.7.1538/WFBS-SVC_Agent.exe successfully [.\Migration.cpp(4781)]
[1020 : 1f10][CMigration::DownloadModule_WinHttp] DownloadModule HTTP status code: 200 [.\Migration.cpp(5035)]
[1020 : 1f10][CMigration::DownloadModule_WinHttp] HTTP content size: 157516424 [.\Migration.cpp(5108)]
[1020 : 1f10][CMigration::DownloadModule_WinHttp] new download. [.\Migration.cpp(5196)]
[1020 : 1f10][CMigration::DownloadModule_WinHttp] Size Error DownloadModule()iDownSize =89856221,iSize=157516424 [.\Migration.cpp(5236)]
[1020 : 1f10][CMigration::DownloadFullPackage] Auto retry number(1) [.\Migration.cpp(2960)]
To address the issue:
  1. Get the affected URL based on the log.​ As an example, https://wfbs-svc-dl-emea.trendmicro.com/filer/aal/packages/6.7.1538/WFBS-SVC_Agent.exe
  2. Manually download the package using a web browser.
  3. Save the package.
  4. Replace the problematic package located on %temp% with the newly downloaded package.
  5. Run the migration tool again.