Issue with Sophos Cloud Migration Tool

Question

Hello All, 
 When I open my CMT I get an error at the bottom indicating that there is a "Problem downloading latest cloud readiness assessment data". 
 I have scoured all I can and looked through the log files, but I am admittedly naive when it comes to determining what could even be the root cause for this. We've been using the tool for over a month now to migrate clients and this issue just started on Monday. 
 Thanks for the help, 
 -Tim

Chris Haydon · Accepted Answer

Hi All

Ok so I now have a work around from support that fixes this issue with hardcoded certificate checking in 1.0.1 Cloud Migration Tool

Please add the following lines to

"C:\Program Files (x86)\Sophos\Cloud Migration Tool\CloudMigration.exe.config"

before the closing </configuration> element

    <appSettings>
        <add key="SkipNamePinning" value="true"/>
    </appSettings>

If you save the file and then rerun the migration tool again you should find it proceeds without the error.

This has moved us from having 5 migratable computers to having 208!!!

Share this issue seem to have lost Sophos at least customer!

Hope that helps

Chris

Anton Kraus · Answer

I was also running this on Server 2012R2. After speaking to Sophos, I understand there is a version 2.0 of the Migration Tool being released soon. Maybe to fix this issue? In any case, this was enough to persuade me to cease my trial of Sophos Central and go in a different direction. Hope they find a fix for you guys soon.

Gowtham Mani · Answer

Hi Tim Osting & Victoria Cleaton, 
 Please give a try to the KBA Sophos Cloud Migration - Windows 2003 root certificate not installed . If the KBA doesn't resolve/ Apply to your environment, please collect the below logs and contact our support . 
 1) Install Wirehshark from www.wireshark.org 2) Capture the traffic of the network adapter used by the DBArchive Server to connect to the Sophos Cloud 3) Reproduce the issue of the Sophos Migration Utility 4) Save the wireshark log with the extension pcapng and compress it 5) Create a new SDU Log for us to investigate. 6) Send the SDU and the Wireshark Log to us.