Sophos Central Migration Tool › central › Migrator › help › en-us › PDF › sc_migrator_h.pdfSophos updates the rules automatically, for example if Sophos Central adds support

Sophos Migration Tool

help

ContentsAbout Sophos Central Migration Tool......................................................................................................1How does Sophos Central differ from on-premise management?...........................................................2How does migration work?...................................................................................................................... 3

Assessment................................................................................................................................... 3Migration........................................................................................................................................ 4

Get started with migration........................................................................................................................7Consider possible issues with migration..................................................................................................8

Computers are unprotected during migration............................................................................... 8Policy settings may change.......................................................................................................... 8Computers may update differently................................................................................................ 9

Check the requirements for migration................................................................................................... 10Sophos Central license............................................................................................................... 10Supported operating systems......................................................................................................10Uninstall unsupported features....................................................................................................11Uninstall unsupported management tools...................................................................................12

Install Sophos Central Migration Tool....................................................................................................14Check which computers can be migrated............................................................................................. 15

Computer readiness and migration states.................................................................................. 16Migration states displayed in the on-premise console................................................................ 18Warnings for computers that are "Ready".................................................................................. 19

Set up new policies................................................................................................................................21Exclude computers from migration........................................................................................................ 22Migrate computers..................................................................................................................................23View migrated computers in Sophos Central........................................................................................ 25Migrate the on-premise management server.........................................................................................26Troubleshooting...................................................................................................................................... 27

Migration error............................................................................................................................. 27"Error (Timed out)"...................................................................................................................... 27"Migrated with error (Installation failed)"..................................................................................... 28Temporary "Installation failed" errors.......................................................................................... 29"Sophos Central agent installer error"........................................................................................ 29"Not ready": Endpoint Security or AutoUpdate required............................................................. 29

Uninstall Sophos Central Migration Tool............................................................................................... 31Roll back to on-premise management...................................................................................................32

Rollback requirements.................................................................................................................32Download and run the script.......................................................................................................32Post-rollback tasks...................................................................................................................... 33

View a computer readiness report.........................................................................................................34View a computer readiness report in Excel................................................................................ 34

View the logs..........................................................................................................................................35Change which columns are displayed................................................................................................... 36Get additional help................................................................................................................................. 37Legal notices.......................................................................................................................................... 38

autorest.java, Json.NET.............................................................................................................. 38BCrypt.Net................................................................................................................................... 38Boost............................................................................................................................................39Log4net........................................................................................................................................ 39

(2020/07/01)

Sophos Central Migration Tool

1 About Sophos Central Migration ToolSophos Central Migration Tool helps administrators to move management of protected computersfrom Sophos Enterprise Console 5.0 and later to Sophos Central.

Getting started

To get started right away, see Get started with migration.

To read more about the background, see How does migration work?

Upgrading?

You can't upgrade directly from earlier versions of the tool. You must uninstall the old version of thetool before you install a new version.

Do you need our advanced guide?

If any of the following apply to you, read our advanced guide as well.

• You have a remote Sophos Update Manager.

• You have a remote Sophos database.

• You have a large number of computers to migrate.

• You want to migrate by sub-estate.

• You want to migrate to multiple accounts.

Related conceptsGet started with migration (page 7)How does migration work? (page 3)Related informationSophos Central advanced guide

Copyright © Sophos Limited 1

https://docs.sophos.com/central/Migrator/advancedguide/en-us/index.html


2 How does Sophos Central differ from on-premise management?Sophos Central differs from on-premise management in three ways.

Management in the cloud

The Sophos Central console is hosted in the cloud by Sophos. You don’t need a management serverand you don’t have to install and update the management console.

User-based policies

On-premise management applies policies to computer groups. Sophos Central gives you a choice.You can set policies for:

• Users or user groups. These policies apply to all a user's computers or other devices.

• Computers or computer groups.

Dedicated protection for servers

On-premise management manages workstations and servers the same way. Sophos Centralmanages servers separately. Server policies apply to specific servers, no matter who logs on. Serverprotection also automatically recognizes certain common server applications, so you don’t need toset complicated scanning exclusions.

For more information about Sophos Central, see knowledge base article 119598.

For help with the Sophos Central console and policies, see the Sophos Centralhelp .

Related informationknowledge base article 119598Sophos Centralhelp

2 Copyright © Sophos Limited

https://community.sophos.com/kb/en-us/119598

http://docs.sophos.com/central/Customer/help/en-us/index.html


3 How does migration work?You install and run Sophos Central Migration Tool on the server where Sophos Enterprise Console(management server) is installed.

NoteTo install and run the tool, you must be a member of the administrators group on the server andhave impersonation rights.

You can use Sophos Central Migration Tool to:

• Assess computers to see whether they can be migrated to Sophos Central.

• Migrate computers.

Related conceptsAssessment (page 3)Migration (page 4)

3.1 AssessmentWhen you run Sophos Central Migration Tool, it gets the list of managed computers from the SophosEnterprise Console database.

Sophos Central Migration Tool then checks whether the computers are ready for migration toSophos Central. To do this, it uses a set of rules (for example, rules for the supported operatingsystem).

NoteSophos updates the rules automatically, for example if Sophos Central adds support for newfeatures.

Sophos Central Migration Tool can do the check in one of two modes: basic assessment or fullassessment. Full assessment requires a Sophos Central account.

During a basic assessment, Sophos Central Migration Tool checks that a computer:

• Runs an operating system supported in Sophos Central.

• Has only those features enabled or installed that are supported in Sophos Central.

• Has no unsupported server software or component installed.

• Has an Sophos Endpoint Security and Control version that can be migrated.

During a full assessment, Sophos Central Migration Tool does the basic checks, but also comparesall features active on the computers against your Sophos Central license. It alerts you if there areany features enabled that you aren't licensed to use in Sophos Central.



Sophos Central Migration Tool then displays evaluation results, showing whether the computers areready for migration and, if they aren't, the reasons why they can't be migrated.

Related conceptsCheck the requirements for migration (page 10)Related tasksCheck which computers can be migrated (page 15)

3.2 MigrationThis section describes how computers are migrated and how they are handled by Sophos Centralafterwards.

How computers are migrated

When you choose to migrate computers:



• The migration tool downloads the Sophos Central agent software and places it in the update share(bootstrap location).

• The computers on the migration list get the agent software during their next scheduled update.(You set this in the Updating policy, on the Schedule tab).

• The Sophos Remote Management System (RMS), used for communications between the computerand the on-premise console, is uninstalled.

• The Sophos Central agent software is installed. This includes Sophos ManagementCommunication System (MCS), used for communications between the computer and SophosCentral.

NoteThe migration process may take up to a couple of hours, depending on the computers’ updatinginterval and network connection.



What happens after migration

When a computer is migrated to Sophos Central, it is treated either as a user’s workstation, if itis running a Windows client operating system, or as a server, if it is running a Windows serveroperating system.

When a workstation is migrated:

• A Sophos Central user account is created based on the last known user of the computer at the timeof migration, and is added to the Sophos Central users list.

• Policies are applied to the computer (by default, the Base policy for each feature).

When a server is migrated:

• The server is added to the Servers list in Sophos Central.

• Server policies are applied to the server (by default, the Base policy for each feature).

Related tasksMigrate computers (page 23)



4 Get started with migrationMigrate your computers to Sophos Central by following these key steps.

1. Conside possible issues with migration.

2. Check the requirements for migration.

3. Install Sophos Central Migration Tool (if you haven't already done so).

4. Check which computers can be migrated.

5. Set up new policies.

6. Migrate computers.

7. Migrate the on-premise management server (if you have already migrated all the managedcomputers).

Related conceptsConsider possible issues with migration (page 8)Check the requirements for migration (page 10)Install Sophos Central Migration Tool (page 14)Set up new policies (page 21)Related tasksCheck which computers can be migrated (page 15)Migrate computers (page 23)Migrate the on-premise management server (page 26)



5 Consider possible issues with migrationBefore you start migration, consider these issues, which may affect your planning.

• Computers are unprotected during migration.

• Policy settings may change.

• Computers may update differently.

Related conceptsComputers are unprotected during migration (page 8)Policy settings may change (page 8)Computers may update differently (page 9)

5.1 Computers are unprotected during migrationYour computers are unprotected for a time during migration. This happens when the on-premiseagent software has been uninstalled but the Sophos Central agent software has not yet beeninstalled.

We recommend that you do as follows:

• Migrate the computers when they aren't being used.

• Advise your users to save all their work before migration and leave their computers turned on.

• After migration, go to Sophos Central to check whether computers need to be restarted.Sometimes a restart is needed for full protection.

• Run a full system scan of the computers to ensure that they haven’t been compromised.

5.2 Policy settings may changeWhen you migrate computers, the policy settings used on them may change.

The migration tool doesn't migrate your policy settings to Sophos Central. Instead, it applies SophosCentral policies as follows:

• Migrated computers get the Sophos Central policies you set for the computer (or server) group thatthe computers are placed in.

NoteComputers are placed in groups by Sophos Central AD Sync.

• If a migrated computer is not associated with a group, or is in a newly-created group, it gets thebase (default) Sophos Central policies.

• Even when migrated computers get group policies, other policies, such as user-based policies, canoverride them.

You should review your Sophos Central policies and check how your policy settings will change afterthe migration, especially if you have modified the default on-premise policies.



For more information on how policy settings will change, see knowledge base article 122041 .

For information about Sophos Central policies, see the Sophos Central help.

Related informationknowledgebase article 122041Sophos Central help

5.3 Computers may update differentlyWhen you migrate computers, the way they get updates may change.

In Sophos Central, computers download their updates directly from Sophos by default. This canincrease your bandwidth usage.

You should consider using the Update Cache feature in Sophos Central. This enables you to set up"update caches", which store endpoint updates on a server on your network from which computerscan download them. We recommend that you do this before migration to avoid spikes in bandwidthusage.





6 Check the requirements for migrationTo be migrated to Sophos Central, computers must run a supported operating system and nothave any Sophos security features that aren't supported in Sophos Central. See the full list ofrequirements and actions you can take in the following subsections.

NoteThe list of Sophos Central readiness conditions against which the migration tool checks computersis updated automatically, for example when a new operating system or feature becomes availablein Sophos Central.

6.1 Sophos Central licenseYou must have a Sophos Central account with a valid license to migrate computers to SophosCentral.

You also need a Sophos Central account to carry out a full assessment of computers beforemigration. If you log in to the account, the migration tool can compare the features on yourcomputers with your Sophos Central license and alert you if there are any features enabled that youaren't licensed to use in Sophos Central.

NoteYou don't need a Sophos Central account if you want to run the tool in the basic assessmentmode.

What to do if you have unlicensed features

If Sophos Central Migration Tool detects an active feature that you aren't licensed to use in SophosCentral, you can:

• Change your Sophos Central license to include the feature. For more information about availablelicenses, see www.sophos.com/en-us/products/enduser-protection-suites/how-to-buy.aspx andwww.sophos.com/en-us/products/server-security/how-to-buy.aspx.

• Disable the feature in the on-premise console or uninstall the feature.

To see details of your Sophos Central license or licenses, go to Sophos Central.

6.2 Supported operating systemsComputers running the following operating systems can be migrated to Sophos Central usingSophos Central Migration Tool, provided that all the other conditions are met.

All Windows client operating systems starting from Windows 7.

All Windows Server operating systems starting from Windows Server 2008 R2.


https://www.sophos.com/en-us/products/enduser-protection-suites/how-to-buy.aspx

https://www.sophos.com/en-us/products/server-security/how-to-buy.aspx

https://central.sophos.com/


At the time of this release, the migration tool can't migrate other operating systems that aresupported by Sophos Central. To migrate computers that run those operating systems, uninstall theon-premise endpoint software and install the Sophos Central agent software.

For a full list of operating systems supported by Sophos Central, see knowledge base article121027.

For information about how to uninstall Sophos products, see knowledge base article 118849 .

For information about how to install Sophos Central endpoint software, see knowledge base article119265 and knowledge base article 120611 .

Related informationknowledge base article 121027knowledgebase article 118849knowledge base article 120611knowledge base article 119265

6.3 Uninstall unsupported featuresCheck whether you need to uninstall unsupported features.

Introduction

Sophos Central does not support the features shown in the table below.

If you currently use any of these features, you may have to uninstall software before you migratecomputers.

Feature What to do

Sophos Client Firewall You don't need to do anything. The feature isuninstalled automatically during migration.

Sophos Patch You don't need to do anything. The feature isuninstalled automatically during migration.

Network Access Control Uninstall the feature. See Uninstall NetworkAccess Control.

Full Disk Encryption Uninstall the feature. See Uninstall Full DiskEncryption.

Uninstall Network Access Control

We don't support this feature any more. If it is still on a computer selected for migration, thecomputer is shown as "Not ready".

Go to the computer and uninstall the feature as follows:

1. If tamper protection is on, turn it off. For details, see Tamper protection is active.


https://www.sophos.com/en-us/support/knowledgebase/121027.aspx





2. Make sure that an update is not in progress. To do this, right-click the Sophos shield in thenotification area and ensure View updating status is grayed out.

If an update is in progress, wait for it to finish.

3. Stop the AutoUpdate service:

a) Open Windows services. (On Windows 10, search for "Services" in the Windows taskbar.)

b) Right-click Sophos AutoUpdate Service and select Stop.

Doing this prevents the service from reinstalling the feature before uninstallation is complete.

4. Open Apps & Features or Programs and Features. (On Windows 10, search for "Settings" in theWindows taskbar and then select Apps > Apps & Features.)

5. Select Sophos Compliance Agent and click Uninstall.

6. Restart the computer.

7. Check that the IP and subnet are the expected values. To do this, open a command prompt andtype ipconfig.

Related informationTamper protection is active

Uninstall Full Disk Encryption

We don't support this feature any more. If it is still on a computer selected for migration, thecomputer is shown as "Not ready".

Go to the computer and uninstall the feature as follows:

1. If tamper protection is on, turn it off. For details, see Tamper protection is active.

2. Make sure that an update is not in progress. To do this, right-click the Sophos shield in thenotification area and ensure View updating status is grayed out.

If an update is in progress, wait for it to finish.

3. Stop the AutoUpdate service:

a) Open Windows services. (On Windows 10, search for "Services" in the Windows taskbar.)

b) Right-click Sophos AutoUpdate Service and select Stop.

Doing this prevents the service from reinstalling the feature before uninstallation is complete.

4. Open Apps & Features or Programs and Features. (On Windows 10, search for "Settings" in theWindows taskbar and then select Apps > Apps & Features.)

5. Select Sophos SafeGuard 5.61.0 Client and click Uninstall.

6. Select Sophos SafeGuard 5.61.0 Preinstall and click Uninstall.

7. Restart the computer.

6.4 Uninstall unsupported management toolsYou can't use Sophos Central Migration Tool to migrate a computer that:

• Has Sophos Enterprise Console management server installed.

• Has Sophos Update Manager installed.

• Acts as a message relay between endpoint computers (running Sophos Endpoint Security andControl) and the Sophos Enterprise Console management server.




• Has one of the following installed: PureMessage for Microsoft Exchange, Sophos for MicrosoftSharePoint, or PureMessage for Lotus Domino.

How to deal with computers running management tools

If you want to migrate these computers, ensure that the Sophos management components are nolonger needed and then uninstall them, as follows:

• Sophos Enterprise Console management server: Uninstall this only after you migrate all thecomputers it manages.

• Sophos Update Manager: Uninstall this only after you migrate all computers that update from it.

• Message relays: Uninstall these only after you migrate all computers communicating through them.

Related informationknowledge base article 122033


https://www.sophos.com/en-us/support/knowledgebase/122033


7 Install Sophos Central Migration Tool

Requirements

You must install Sophos Central Migration Tool on the computer where the Sophos EnterpriseConsole management server is installed.

You must be a member of the administrators group on the server and have impersonation rights.

You also need:

• Windows Installer Framework 4.5 or later. If you don’t have it, install it before you install the tool.

• NET 4.7.2 or later. If you don't have it, install it before you install the tool.

Extra requirements for complex networks

If any of the following apply, see the advice in our Sophos Central Migration Tool advanced guide .

• You have a remote Sophos Update Manager.

• You have a remote Sophos database.

• You have a large number of computers to migrate.

• You want to migrate by sub-estate.

• You want to migrate to multiple Sophos Central accounts.

Get the installer and run it

Go to knowledge base article 122264. This includes a link to the installer and advice on installation.

Related tasksUninstall Sophos Central Migration Tool (page 31)Related informationSophos Central Migration Tool advanced guideknowledge base article 122264





8 Check which computers can be migratedTo check whether your computers can be migrated to Sophos Central:

1. Open Sophos Central Migration Tool.

NoteOnly one instance of the tool can run on the same computer at the same time.

2. In the Connect to Sophos Central dialog, choose from:

• Full assessment and migration. You are prompted to sign in to Sophos Central and set up amigration password (see next step).

• Basic assessment.

A basic assessment checks the computers’ operating systems, enabled features, and so on.A full assessment also checks whether your Sophos Central license covers the features youcurrently have.

3. If you selected Full assessment and migration, you see the Create Sophos Central Tokendialog.

a) Click the link to go to Sophos Central and sign in.

b) The API Token Management page is displayed, and you're prompted to add a token. Enter atoken name and passphrase. Click Copy.

c) Go back to the migration tool dialog and Paste the token in.

From now on, you'll use the migration passphrase when you log on to use the migration tool.

NoteIf you keep the migration tool open for more than 24 hours, you'll need to re-enter yourpassphrase.

4. Sophos Central Migration Tool retrieves the list of computers from the on-premise managementdatabase, checks them for readiness, and displays the list of results.

5. Sophos Central Migration Tool displays a list of your computers, Review the list to see whichcomputers are ready to be migrated and which are not.

There are three main readiness states:

• Ready. The computer can be migrated. If there are warnings, see Warnings for computers thatare "Ready".

• Not ready but can be remediated. The computer can't be migrated in its present state, butyou can take actions that will enable migration. For example, you can disable features thataren't supported in Sophos Central.

• Not ready and cannot be migrated. The computer can't be migrated and no remediationactions are available. For example, the computer is running an operating system that isn'tsupported in Sophos Central.

For more information about computer readiness and migration states, see Computer readinessand migration states.

The results of computer assessment for readiness may look like this:



6. Optionally, you can click Report to generate a more detailed report on computer readiness.

If you are ready to migrate your computers to Sophos Central, see Migrate endpoints.

Related conceptsWarnings for computers that are "Ready" (page 19)Computer readiness and migration states (page 16)Related tasksView a computer readiness report in Excel (page 34)Migrate computers (page 23)

8.1 Computer readiness and migration statesAfter being assessed by the migration tool, computers may end up in or go through the followingstates.



NoteFor more information about the status and remediation actions, if any (for example, for computersthat are not ready), click on the computer in the list and view the details in the right pane.

Icon Status Description

Ready The computer can be migrated. If there are warnings, see Warningsfor computers that are "Ready".

Not ready(fixable)

The computer can't be migrated in its present state, but you cantake actions that will enable migration. For example, you can disablefeatures that aren't supported in Sophos Central.

Not ready The computer can't be migrated.

Not ready(excluded)

The computer has been excluded from migration by theadministrator.

Pending The administrator has chosen to migrate the computer, but migrationhasn't started yet.

Migrating The computer is being migrated.

Migrated The computer has been migrated and has been found in the list ofcomputers managed by Sophos Central.

Error An error has occurred during migration. The computer isn't yetmanaged by Sophos Central.

Migratedwith error(Installationfailed)

The computer has been migrated and is managed by SophosCentral, but an installation error has occurred that has most likely leftthe computer unprotected.


The computer has been migrated and is managed by SophosCentral, but an installation error hasn’t been resolved, and thecomputer has remained unprotected for more than a predefined timeinterval (by default, 24 hours).

Related conceptsWarnings for computers that are "Ready" (page 19)Troubleshooting (page 27)"Migrated with error (Installation failed)" (page 28)Related tasksExclude computers from migration (page 22)



8.2 Migration states displayed in the on-premiseconsoleWhen a computer has started migration, its migration state is displayed in the on-premisemanagement console, in the Computer description column, for example:

The following table shows the correspondence between the migration state shown in Sophos CentralMigration Tool and the computer description in the on-premise console.

Migration state Computer description / Status in on-premiseconsole

Description

Pending {SC:Pending:<jobid>} The computer has beenadded to the migration listand is awaiting migration.<jobid> is a uniqueinteger associated with themigration request, here andbelow.

Migrating {SC:Migrating:<jobid>} The computer is beingmigrated.

In Central {SC:InCentral:<jobid>} The computer hasbeen found in the list ofcomputers managed bySophos Central and hassuccessfully updated atleast once since then.

Error {SC:Error:<jobid>;<error code>} An error has occurredduring migration.

Timed out {SC:Timeout:<jobid>} The computer has been inthe “Pending” or “Migrating”state for longer than apredefined timeout interval.For more information, seeError (Timed Out).



Migration state Computer description / Status in on-premiseconsole

Description

In Central (error) {SC:FailedInstallation:<jobid>} The computer hasbeen found in the list ofcomputers managed bySophos Central, but theinstallation of the SophosCentral agent software hasfailed.

In Central(critical error)

{SC:NotProtected:<jobid>} A Sophos Central agentsoftware installation errorhasn’t been resolved andthe computer has remainedunprotected for more thana predefined time interval(by default, 24 hours).

Pending offlinetimeout

{SC:OfflineTimeout:<jobid>} The computer has beenin the "Pending" statefor longer than 24 hours.During this time it has notsent any RMS messages.

Migratingtimeout

{SC:XMigratingTimeout:<jobid>} A computer has been inthe "Migrating" state formore than 3 hours. It hasnot reported a successfulupdate to Sophos Central.

For more information about these states and what actions to take, if necessary, see the details inSophos Central Migration Tool, in the View the logs, or in Sophos Central.

For information about resolving errors, see Troubleshooting.

Related concepts"Error (Timed out)" (page 27)View the logs (page 35)Troubleshooting (page 27)

8.3 Warnings for computers that are "Ready"You may see warnings beside computers that are "Ready" for migration. Check the table below tosee what the warning means and whether you need to take action.

Warning Comments

{productname} is not supported by SophosCentral and will be uninstalled during migration

You don’t need to take action. After migration,the computer won't have the named productinstalled.



Warning Comments

Primary update location is not a UNC path. Depending on your Sophos Enterprise Consolesetup, migration may not work with this non-UNC path.

Primary update location is not updated by thelocal Sophos Update Manager.

The computer gets updates from a remoteSophos Update Manager. You must makechanges on that Sophos Update Managerbefore you migrate. See the Sophos CentralMigration Tool advanced guide.

Some policy settings may change aftermigration.

See Policy settings may change.

The computer has the exploit prevention featureinstalled. You may need to restart it during themigration.

Restart the computer (if necessary).

Related conceptsPolicy settings may change (page 8)Related informationSophos Central Migration Tool advanced guide




9 Set up new policiesSophos Central Migration Tool doesn't migrate your policy settings to Sophos Central.

If you don't want migrated computers to get your default Sophos Central policies, you should takeaction.

Before migration, apply custom policies to the Sophos Central computer (or server) group that youwill migrate computers to. This ensures that computers get the right policies as soon as you migratethem.

NoteComputers are placed in Sophos Central groups by the migration tool's Preserve Group Layoutsoption (which is on by default), or by Sophos Central AD Sync.

Alternatively, you can create and apply custom policies after you migrate computers.

Related conceptsPolicy settings may change (page 8)



10 Exclude computers from migrationIf you don’t want to migrate a computer to Sophos Central, you can add it to the migration exclusionlist. That way, it won’t be accidentally selected for migration and migrated.

NoteComputers that are already managed by Sophos Central can't be excluded from migration. Anysuch computers that have been selected aren't added to the exclusion list.

To exclude computers from migration:

1. Select the computer or computers in the computer list, right-click and click Add to Exclusion List.

2. In the Exclude computers from migration dialog box, type in the reason for the exclusion, if youwish, to serve as a reminder. Click OK.

Excluded computers’ status will change to “Not Ready” with a padlock icon

.

If you later change your mind and decide to migrate the computers, you can remove them from theexclusion list. After you re-include computers in the migration process, they may appear as either“Ready” or “Not Ready”, depending on their Sophos Central readiness assessment.



11 Migrate computers

WarningYour computers are unprotected for a time during migration.

To migrate your computers to Sophos Central, do as follows:

1. Open Sophos Central Migration Tool, connect to Sophos Central, and check which computers canbe migrated.

If you haven't set up your migration password for access to Sophos Central yet, you select a "Full"assessment to get set up.

2. Remediate computers that can't be migrated in their present state. For example, disable featuresthat aren't supported in Sophos Central.

3. Select the computers that are ready.

To view only the computers that are ready, click Ready at the top of the screen.

4. Filter the computers before migration. You can:

• Click on the funnel icon in a column header (for example, Group) and type the term you wantto filter for.

• Display different columns that you can use for filtering. Right-click in the table header andselect from the menu.

When you filter computers, the Ready number doesn't change, but the number in the lower rightof the UI shows how many you have filtered.

To clear filters, use View > Filters > Clear All.

5. Highlight computers and click Select to select them for migration.

6. Click Migrate, and then click Yes in the confirmation message.The computers go into the Pending state until their next scheduled update.

NoteIf computers are in the Pending state for too long, you'll see a timeout warning.

When the migration starts, the computers change their state to Migrating

NoteMigration may take up to two hours, depending on the computers’ updating interval and networkconnection. It may take longer for computers that update from a remote Sophos Update Manager.

NoteSome computers may display a Windows Action Center alert, saying that the computers areunprotected. The alert disappears after migration.

NoteDuring migration, you may see a computer in Sophos Central while you can still see and manage itin Sophos Enterprise Console too.



When migration is complete, computers are moved to the In Central view.

If migration isn't successful, the affected computers are moved to the Error view, where you can finddetails.

You can now view migrated computers in Sophos Central.

You should do as follows:

• Go to Sophos Central to check whether the computers need to be restarted. The migration tooldoesn’t show this.

• Run a full system scan of the computers to ensure that they were not compromised duringmigration.

• Check that the computers have the right Sophos Central policies applied.

After migrating all the managed computers, you can migrate the on-premise management server.

NoteAfter migration, we recommend that you delete the Sophos Central API Token that you set up.

Related conceptsComputers are unprotected during migration (page 8)"Error (Timed out)" (page 27)Related tasksCheck which computers can be migrated (page 15)View migrated computers in Sophos Central (page 25)Migrate the on-premise management server (page 26)



12 View migrated computers in SophosCentralWhen a computer has been migrated to Sophos Central, its details in Sophos Central Migration Toolaren't updated. For up-to-date information about the computer, including any protection alerts, go toSophos Central.

1. In Sophos Central:

• To view the details for a migrated workstation, go to the Computers page.

• To view the details for a migrated server, go to the Servers page.

2. In the list of computers or servers, click on the name of the computer to view its full details.

Related informationSophos Central help




13 Migrate the on-premise managementserverIf you have migrated all endpoint computers, you can migrate the on-premise management server toSophos Central.

1. Uninstall Sophos Central Migration Tool.

2. Uninstall Sophos Enterprise Console. Uninstall components in this order:

• Sophos Management Console

• Sophos Management Database

• Sophos Management Server

• Sophos Update Manager

NoteUninstalling the Sophos Management Database component doesn't remove the databasesattached to the SQL Server instance. For a list of databases associated with each console,see knowledge base article 17323. If you are planning to leave the SQL Server instance, thedatabases remain attached.

See also knowledge base article 116912.

3. Run the Sophos Central agent installer to migrate the server.

You can download the installer for Server Protection for Windows from the Protect Devicespage in Sophos Central.

Related tasksUninstall Sophos Central Migration Tool (page 31)Related informationknowledge base article 17323knowledge base article 116912





14 Troubleshooting

14.1 Migration errorIf an error occurs before a computer has been migrated to Sophos Central, you will see:

•

A yellow warning sign:

• The word "Error" in the Status column next to the computer.

See computer details for more information about the error.

Related concepts"Error (Timed out)" (page 27)

14.2 "Error (Timed out)"If a migration action has timed out on a computer before the computer could be migrated to SophosCentral, you will see:

•

A yellow warning icon:

• "Error (Timed out)" in the Status column next to the computer.

This error appears when:

• The computer has been in the “Pending” state for more than a predefined timeout interval.The timeout occurs in two hours (by default) if the computer is connected to the network andcommunicating with the on-premise management console. If the computer is offline, the timeout willoccur in 24 hours.

• The computer has been in the “Migrating” state and hasn't been found in the list of computersmanaged by Sophos Central for more than a predefined timeout interval (by default, one hour).

There are several possible reasons for the timeout error. For example, there may be a connectionproblem between Sophos Central and the server on which Sophos Central Migration Tool is running.

Check in Sophos Central to see if the computer has been migrated and appears in Sophos Central.

NoteA computer appears in Sophos Central as soon as it has registered, but it doesn’t appear inSophos Central Migration Tool until it has updated at least once after that and is protected.

If the computer appears in Sophos Central, wait several minutes and check the computer entry inSophos Central Migration Tool again. If it still shows the error, try restarting the tool and signing in toyour Sophos Central account again.

If the computer hasn’t appeared in Sophos Central, go to that computer and check the SophosEndpoint Security and Control installation status. Try running the Sophos Central agent installermanually on the computer.



14.3 "Migrated with error (Installation failed)"If an installation error occurs after migration, and a computer might not be protected, you see one ofthe following icons next to the computer:

Icon Status Description


The computer has been migrated and is managed by SophosCentral, but an installation error has most likely left the computerunprotected.

Migrated with error(Installation failed)

The computer has been migrated and is managed by SophosCentral, but an installation error hasn’t been resolved. The computerhas been unprotected for more than a predefined time interval (bydefault, 24 hours).

These errors can occur:

• If the migrated computer needs to be restarted.

• If the installation takes more than ten minutes (the default time allowed). In this case, the error isdisplayed only temporarily.

You can go to Sophos Central to investigate the cause, as described below.

Check for errors in Sophos Central

WarningIn Sophos Central, these error events may not be escalated to a warning and displayed in theAlerts right away.

To check the events for a computer, do one of the following:

• For a workstation, go to Computers, click on the computer name and go to the Events tab.

• For a server, go to Servers, click on the server name and go to the Events tab.

• To view events for all computers, go to Logs & Reports > Events, and filter the events by the typeProtection > Failed to protect computer or server.

If you see an event “Failed to install savxp: a reboot is required before the installation cansucceed”, you must restart the computer to ensure it is protected successfully following themigration.

Related conceptsTemporary "Installation failed" errors (page 29)Related informationSophos Central help




14.4 Temporary "Installation failed" errorsThe "Migrated with error (Installation failed)" error can be displayed temporarily if installation ofthe Sophos Central agent takes more than ten minutes (the default time allowed before an error isreported).

This section tells you how to resolve the error and how to prevent it occurring in future.

To resolve the error:

• Go to Sophos Central and check that the computer is listed as a managed device.

• Restart the computer. The error should then be replaced by a successful "Migrated" status.

To prevent this timeout problem in future migrations, you can use a registry setting to change thetime allowed for installation. See knowledge base article 126789.


14.5 "Sophos Central agent installer error"The Sophos Central agent installer may report an error preventing migration.

In this case, in Sophos Central Migration Tool, you will see "Sophos Central agent installer" error inthe Status column next to the computer.

In Sophos Enterprise Console, you will see the following status in the Computer descriptioncolumn:

{SC:Error:<jobid>;<error code>}

where <jobid> is a unique integer associated with the migration request and <error code> is anerror code returned by the Sophos Central agent installer.

You can look up the error by its error code and read about remediation steps in knowledge basearticle 122157 .


14.6 "Not ready": Endpoint Security or AutoUpdaterequiredSophos Central Migration Tool requires that SophosSophos Enterprise Console and SophosAutoUpdate are installed and running on the migrated computer. If either can't be detected, yousee the error “The migration requires that you install Sophos Enterprise Console” or “The migrationrequires that you install Sophos AutoUpdate”.

To resolve the error, re-protect the endpoint computer.

1. In Sophos Enterprise Console, select the computers you want to re-protect, right-click, and thenclick Protect Computers.





2. Follow the steps in the Protect Computers Wizard.

Remember not to select any of the features that are not supported in Sophos Central, such asEncryption software, Firewall or Patch.

Related informationSophos Enterprise Console help: Protect computers automatically


https://docs.sophos.com/esg/enterprise-console/5-5-2/help/en-us/esg/Enterprise-Console/tasks/protect_09_wizard.html


15 Uninstall Sophos Central Migration ToolBefore you uninstall Sophos Central Migration Tool, complete any migration tasks that are running. Ifyou don't, you may lose information about the progress of migration.

To uninstall the tool, use the setup program, as follows.

NoteWe don't recommend that you use Add/Remove Programs or Programs and Features. If UAC isenabled, this type of uninstallation may not remove the migration tool's data schema.

1. Open a command prompt with administrator rights (right-click Start and select Run asAdministrator).

2. Go to the Sophos Central Migration Tool installation files on the server:

C:\scmt_210

3. Run Setup.exe/u.



16 Roll back to on-premise managementAfter you migrate computers to Sophos Central, you can roll them back to the on-premise software.

Introduction

You use a Sophos script to roll computers back. The script does as follows:

• Finds the Sophos Central endpoint product on computers and uninstalls it.

• Runs the on-premise installer from a central directory to reprotect the computers.

Rollback requirements

The requirements for using the script are as follows:

• Only run the script on computers managed by Sophos Central. These appear in the migration toolwith the status "In Cloud", "In Cloud (error)", or "In Cloud (critical error)".

• Turn off Server Lockdown (if you use it on your servers).

• Ensure the script is run on the computers as Administrator.

• Use cscript or wscript to call the script. The only difference is the logging:

wscript outputs errors and details to the console

cscript outputs errors and details to the default log file %temp%\SophosCloudRollback.log

NoteUse cscript on Windows Server Core because no UI is available.

Download and run the script

To use the script, do as follows:

1. Get the rollback script from https://sophserv.sophos.com/repo_kb/122211/file/rollback.vbs.txt

2. Make sure you rename the file to rollback.vbs

3. Run the script with the command to run the on-premise installer, including the update path andcredentials.

cscript C:\RollbackScript\rollback.vbs\\myServer\SophosUpdate\CIDs\S000\SAVSCFXP\setup.exe -user administrator -pwd admin -s -mng yes

This example connects to the central directory as user "administrator" with password "admin",runs the installer silently, and confirms the computer is managed.

For details of all the parameters, see Sophos Endpoint: Command line parameters used bysetup.exe.


https://sophserv.sophos.com/repo_kb/122211/file/rollback.vbs.txt


We recommend that you obfuscate the credentials with the -ouser and -opwd parameters.

If you see this message, go to Sophos Central and turn off Server Lockdown. Go to a server'sdetails page and click Unlock or turn off the Server Lockdown policy.

After you run the script, you must do the post-rollback tasks described below.

Related informationSophos Endpoint: Command line parameters used by setup.exe

Post-rollback tasks

When the rollback is complete and the computer shows as managed in Sophos Enterprise Console, doas follows:

1. Delete the computers from Sophos Central.

a) In Sophos Central Admin , select Devices.

b) Select the checkbox next to each computer you rolled back.

c) Click Delete and then OK.

2. In Sophos Enterprise Console, update the computers.

a) In Computer View, find the computers.

b) Right-click the computers and select Update Computers Now.




17 View a computer readiness reportA computer readiness report shows you whether computers are ready to migrate.

• To generate a report, click the Report button (in the lower left of the user interface).

An HTML report is displayed, containing details of all computers (not just computers you haveselected), their readiness state, and required remediation actions, if any.

Related tasksView a computer readiness report in Excel (page 34)

17.1 View a computer readiness report in ExcelThe Report button in the migration tool generates an HTML report that is displayed to you, but alsogenerates an XML copy of the report, report.xml, in the following location:

C:\ProgramData\Sophos\Cloud Migration Tool\

The file report.xml is updated every time you click Report.

If you want to view the computer Sophos Central readiness report as an Excel spreadsheet, followthese steps:

1. Open Excel.

2. In Excel, on the File menu, click Open. Browse to C:\ProgramData\Sophos\CloudMigration Tool\ and open the file report.xml.

NoteProgramData or Application Data are hidden folders. Therefore, you have to either typein the full path when browsing for the file or disable hidden folders in Windows Explorer.

3. When prompted, choose to open the file without applying the stylesheet. Click OK.

4. When prompted, choose to open the file as an XML table. Click OK.

5. In the message saying that no schema is present, click OK or Cancel.

This produces an Excel table with the computers you selected before you clicked Report and theirreadiness status. You can sort and group the entries in the table.



18 View the logsYou can find the Sophos Central Migration Tool log file in the following location.

C:\ProgramData\Sophos\Cloud Migration Tool\Logs\CloudMigration.log

NoteProgramData is a hidden folder. Therefore, you have to either type in the full path when browsingfor the file or disable hidden folders in Windows Explorer.

The logs created during installation or uninstallation of the tool can be found under C:\Windows\Temp. The logs are:

• mtc-dbinstall.log

• mtc-dbuninstall.log

• mtc-install.log

• mtc-setup.log

• scmtcl_<timestamp>.log



19 Change which columns are displayedYou can add columns to the computer list view in Sophos Central Migration Tool to display moreinformation about the computers, such as the computer description, operating system, or server role.

The Name, Domain/workgroup, Status, and Group columns are always displayed. You can't hidethem.

To change which columns are displayed:

1. On the View menu, click Columns (or right-click anywhere in the table header) and then click onthe name of the column you want to display or hide. The columns that are displayed in the viewhave check marks next to their names.

2. After you have added the columns to the view, you can:

• Drag and drop the column headings to rearrange the order in which the columns are displayed.

• Change the width of a column by dragging the boundary on the right side of the columnheading.

• Sort the list of computers by any column by clicking on its heading.

NoteIf you generate a computer readiness report, it includes all information about computers,irrespective of the columns displayed in the computer list when the report is generated.



20 Get additional helpTo get help from Sophos Support:

• Visit the Sophos Community at community.sophos.com/ and search for other users who areexperiencing the same problem.

• Visit the Sophos support knowledgebase at www.sophos.com/en-us/support.aspx.


http://community.sophos.com/

http://www.sophos.com/en-us/support.aspx


21 Legal noticesCopyright © 2020 Sophos Limited. All rights reserved. No part of this publication may be reproduced,stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical,photocopying, recording or otherwise unless you are either a valid licensee where the documentationcan be reproduced in accordance with the license terms or you otherwise have the prior permissionin writing of the copyright owner.

Sophos and Sophos Anti-Virus are registered trademarks of Sophos Limited and Sophos Group.All other product and company names mentioned are trademarks or registered trademarks of theirrespective owners.

autorest.java, Json.NETMIT License

Copyright (c) Microsoft Corporation. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the "Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantialportions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE

BCrypt.NetNew BSD License (BSD)

Copyright (c) 2006, 2010, Damien Miller <[email protected]>, Ryan Emerle

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permittedprovided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and thefollowing disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions andthe following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of the <organization> nor the names of its contributors may be used to endorseor promote products derived from this software without specific prior written permission.



THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "ASIS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSEARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSEDAND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BoostPermission is hereby granted, free of charge, to any person or organization obtaining a copy ofthe software and accompanying documentation covered by this license (the "Software") to use,reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works ofthe Software, and to permit third-parties to whom the Software is furnished to do so, all subject to thefollowing:

The copyright notices in the Software and this entire statement, including the above license grant,this restriction and the following disclaimer, must be included in all copies of the Software, in wholeor in part, and all derivative works of the Software, unless such copies or derivative works are solelyin the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENTSHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLEFOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

Log4netApache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as definedby Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that isgranting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, arecontrolled by, or are under common control with that entity. For the purposes of this definition,"control" means (i) the power, direct or indirect, to cause the direction or management of suchentity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of theoutstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by thisLicense.



"Source" form shall mean the preferred form for making modifications, including but not limited tosoftware source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of aSource form, including but not limited to compiled object code, generated documentation, andconversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made availableunder the License, as indicated by a copyright notice that is included in or attached to the work(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on(or derived from) the Work and for which the editorial revisions, annotations, elaborations, orother modifications represent, as a whole, an original work of authorship. For the purposes of thisLicense, Derivative Works shall not include works that remain separable from, or merely link (orbind by name) to the interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Workand any modifications or additions to that Work or Derivative Works thereof, that is intentionallysubmitted to Licensor for inclusion in the Work by the copyright owner or by an individual orLegal Entity authorized to submit on behalf of the copyright owner. For the purposes of thisdefinition, "submitted" means any form of electronic, verbal, or written communication sent tothe Licensor or its representatives, including but not limited to communication on electronicmailing lists, source code control systems, and issue tracking systems that are managed by, oron behalf of, the Licensor for the purpose of discussing and improving the Work, but excludingcommunication that is conspicuously marked or otherwise designated in writing by the copyrightowner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom aContribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributorhereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocablecopyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform,sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributorhereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable(except as stated in this section) patent license to make, have made, use, offer to sell, sell, import,and otherwise transfer the Work, where such license applies only to those patent claims licensableby such Contributor that are necessarily infringed by their Contribution(s) alone or by combinationof their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institutepatent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) allegingthat the Work or a Contribution incorporated within the Work constitutes direct or contributorypatent infringement, then any patent licenses granted to You under this License for that Work shallterminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof inany medium, with or without modifications, and in Source or Object form, provided that You meetthe following conditions:

a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

b) You must cause any modified files to carry prominent notices stating that You changed thefiles; and

c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright,patent, trademark, and attribution notices from the Source form of the Work, excluding thosenotices that do not pertain to any part of the Derivative Works; and

d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Worksthat You distribute must include a readable copy of the attribution notices contained within



such NOTICE file, excluding those notices that do not pertain to any part of the DerivativeWorks, in at least one of the following places: within a NOTICE text file distributed as partof the Derivative Works; within the Source form or documentation, if provided along with theDerivative Works; or, within a display generated by the Derivative Works, if and whereversuch third-party notices normally appear. The contents of the NOTICE file are for informationalpurposes only and do not modify the License. You may add Your own attribution noticeswithin Derivative Works that You distribute, alongside or as an addendum to the NOTICEtext from the Work, provided that such additional attribution notices cannot be construed asmodifying the License. You may add Your own copyright statement to Your modificationsand may provide additional or different license terms and conditions for use, reproduction, ordistribution of Your modifications, or for any such Derivative Works as a whole, provided Youruse, reproduction, and distribution of the Work otherwise complies with the conditions stated inthis License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionallysubmitted for inclusion in the Work by You to the Licensor shall be under the terms and conditionsof this License, without any additional terms or conditions. Notwithstanding the above, nothingherein shall supersede or modify the terms of any separate license agreement you may haveexecuted with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, servicemarks, or product names of the Licensor, except as required for reasonable and customary use indescribing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor providesthe Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUTWARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, withoutlimitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY,or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining theappropriateness of using or redistributing the Work and assume any risks associated with Yourexercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence),contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligentacts) or agreed to in writing, shall any Contributor be liable to You for damages, including anydirect, indirect, special, incidental, or consequential damages of any character arising as a result ofthis License or out of the use or inability to use the Work (including but not limited to damages forloss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercialdamages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Worksthereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity,or other liability obligations and/or rights consistent with this License. However, in accepting suchobligations, You may act only on Your own behalf and on Your sole responsibility, not on behalfof any other Contributor, and only if You agree to indemnify, defend, and hold each Contributorharmless for any liability incurred by, or claims asserted against, such Contributor by reason of youraccepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the fieldsenclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!)The text should be enclosed in the appropriate comment syntax for the file format. We alsorecommend that a file or class name and description of purpose be included on the same "printedpage" as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner]



Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except incompliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License isdistributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress or implied. See the License for the specific language governing permissions and limitationsunder the License.


Sophos Central Migration Tool › central › Migrator › help › en-us › PDF › sc_migrator_h.pdfSophos updates the rules automatically, for example if Sophos Central adds support

Documents