Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 3 subscribers
  • Views 4078 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos SEC to Central migration issue

Abhijeet Nawale

Hello All,

I am trying to migrate sophos SEC to Central via migration tool, however getting an error while doing that.

While checking the logs it says :

2022-01-19T12:24:12.7697292Z INFO : Target path: C:\\Program Files (x86)\\Sophos\\CloudInstaller
2022-01-19T12:24:12.7697292Z INFO : Migration.csv file: C:\\ProgramData\\Sophos\\AutoUpdate\\Cache\\savxp\\migration.csv
2022-01-19T12:24:12.7697292Z WARNING : Endpoint is not listed in migration.csv
2022-01-19T12:24:12.7697292Z ERROR : Exception: Not migrating endpoint

Any suggestions here please?



This thread was automatically locked due to age.
Parents
  • 0

    Hello Abhijeet Nawale,

    have not yet migrated so I'm not sure what migration.csv contains or should contain and how the computer is identified (name, id, ...). What does the said file contain. This is apparently the first computer you try to migrate, as it should do no harm could you try with another one?
    And please give the name of the log and ideally post the complete log. There's a number of logs and it's not always easy to determine from which one a snippet is. Furthermore the final error message is not always an indication of the actual underlying cause in which case usually some other part of the log contains the important and significant information..

    Christian

Reply
  • 0

    Hello Abhijeet Nawale,

    have not yet migrated so I'm not sure what migration.csv contains or should contain and how the computer is identified (name, id, ...). What does the said file contain. This is apparently the first computer you try to migrate, as it should do no harm could you try with another one?
    And please give the name of the log and ideally post the complete log. There's a number of logs and it's not always easy to determine from which one a snippet is. Furthermore the final error message is not always an indication of the actual underlying cause in which case usually some other part of the log contains the important and significant information..

    Christian

Children
Unfiltered HTML