Hi everyone, I'm migrating my clients from sophos enterprise console to sophos central.I have no problems migrating main office computers, I have problems with brench offices that have a Remote update manager.I'm following this guide which seems pretty clear to me but it doesn't work.
I go to the remote update manager, open an elevated CMD and go to: c: \ program files (x86) \ sophos \ MigrationAgentthen I issue the command:SophosMigrationAgent.exe –p "\\ sophos \ SophosUpdate \ CloudMigrationPackage"
(\\sophos is my SEC server)
I also tried to copy the folder "\\ sophos \ SophosUpdate \ CloudMigrationPackage" to "c:\CloudMigrationPackage" and then launched the command:SophosMigrationAgent.exe –p "c: \ CloudMigrationPackage"
in any case I get this error that I am attaching to you
what am I doing wrong?
Thank you for reaching us, kindly share with us the logs for the Sophos migration tool. You can collect this on the below path.C:\ProgramData\Sophos\Cloud Migration Tool\Logs\CloudMigration.log
sorry for the delay, I attach the log.
ON the logs I'm seeing below error.
2021-05-03T11:19:57.509Z  ERROR HttpHelper.DoOperationAndRetryIfTooManyRequests Central API call exception: Central API call failed. Status: TimedOut2021-05-03T11:19:57.509Z  ERROR MigrationCoordinator.UpdateAvailableCloudFeatures Failed to update available Central features list. Endpoint migration ability may not be accurate or up-to-date.
Are you using the latest Migration tool on your branch office? If not? then please uninstall this Migration tool and install the latest one. Once done please perform another migration and let us know if issue still occurs.
The migration tool is installed only in the SEC server in the main office, downloaded from this website last week: https://www.sophos.com/en-us/lp/migrating-to-sophos-central.aspx
From the guide I understood it must be installed on the sec server, then from the "remote update manager" launch the migration agent making it point to "\\ secserver \ sophosupdate \ cloudmigrationpackages"
that's right isn't it?
You are right, to further check and isolate the issue, can you please raise a support case and share it with me through DM Collect replicate the issue and collect the logs then attached it to the case.
Just checking if you we're able to create a case for this one? If so? Please let us know.
I haven't been able to create it yet, because the client decided to finish the migration of the main office, and then focus on the branch offices. So I have to wait a couple of days