˄˅

Partial Migration from ESET PROTECT (or ESMC 7.x) to ESET PROTECT Cloud

The migration from ESET PROTECT (or ESMC 7.x) Server to ESET PROTECT Cloud is partial—see the table below:

You can migrate:	You cannot migrate:
•ESET Management Agents (managed computers) •policies •dynamic group templates •report templates •mobile devices (Android only)	•the whole database •dynamic groups (but you can migrate dynamic group templates) •detections •audit logs •notifications •tasks and triggers •installers •scheduled/generated reports (but you can migrate report templates) •tags •iOS mobile devices

You can migrate:

You cannot migrate:

•ESET Management Agents (managed computers)

•policies

•dynamic group templates

•report templates

•mobile devices (Android only)

•the whole database

•dynamic groups (but you can migrate dynamic group templates)

•detections

•audit logs

•notifications

•tasks and triggers

•installers

•scheduled/generated reports (but you can migrate report templates)

•tags

•iOS mobile devices

ESET PROTECT Cloud does not support ESET Inspect but supports ESET Inspect Cloud. If you migrate from ESET PROTECT to ESET PROTECT Cloud, you will not be able to manage ESET Inspect from ESET PROTECT Cloud, but you can manage ESET Inspect Cloud from ESET PROTECT Cloud.

Follow the steps below to migrate from ESET PROTECT (or ESMC 7.x) to ESET PROTECT Cloud:

If you have an MSP account, follow the steps for MSP migration to Cloud.

I. Create a new ESET PROTECT Cloud instance

II. Migrate Policies from the on-premises ESET PROTECT to ESET PROTECT Cloud

III. Migrate Dynamic Group Templates from the on-premises ESET PROTECT to ESET PROTECT Cloud

IV. Migrate Report templates from the on-premises ESET PROTECT to ESET PROTECT Cloud

V. Migrate ESET Management Agents (managed computers) from the on-premises ESET PROTECT to ESET PROTECT Cloud with Migration Policy

VI. Migrate mobile devices

VII. Set up ESET PROTECT Cloud users in ESET Business Account

VIII. Add ESET Business Account users to ESET PROTECT Cloud Web Console

IX. Decommission the on-premises ESET PROTECT Server

If you manage devices encrypted with ESET Full Disk Encryption, follow these steps to avoid the loss of recovery data.

1.Before the migration - Navigate to Status Overview > Encryption. Here you can Export your current ESET Full Disk Encryption Recovery Data.

2.After the migration - Import the ESET Full Disk Encryption Recovery Data on your new management console.

If you are unable to perform these steps, you need to decrypt the managed devices before the migration. After the migration, you can encrypt the managed devices from the ESET PROTECT Cloud Web Console.

Do not export any ESET Management Agent policies.

Ensure you fully unassign all active Agent policies before the migration.

I. Create a new ESET PROTECT Cloud instance

Prerequisites

•A Superuser account in ESET Business Account.

•An eligible license for ESET PROTECT Cloud.

If your EBA and EMA2 accounts are registered to the same email address, the ESET PROTECT Cloud can be activated only from one account. The account (EBA or EMA2) you choose to create the ESET PROTECT Cloud instance from will be the only one you can use to activate or delete the instance.

Create a new ESET PROTECT Cloud instance

1.Open the ESET Business Account and log in (or create a new account).

2.Click Licenses > Enter License Key.

eba_welcome

3.In the Add License window, type your ESET PROTECT Cloud license key and click Add License.

eba_add_license

4.You will receive a verification email (if you do not receive the email, follow the Knowledgebase article instructions). Click Verify license.

eba_verify_license

5.In the Dashboard, click Activate under ESET PROTECT Cloud.

Check the language setting of your ESET Business Account. Some ESET PROTECT Cloud main program window elements are defined the first time you set the language in your ESET Business Account language settings, and cannot be changed later.

6.An Activate ESET PROTECT Cloud window will open. Read the Terms of Use and select the check box if you agree.

7.Select a data center location for your ESET PROTECT Cloud instance that is the closest to the location of your managed network and click Continue.

After selected, you will not able to change the data center location of your ESET PROTECT Cloud instance.

8.Your ESET PROTECT Cloud instance will be created. You can wait for a few minutes until it is created or you can log out and you will be notified by email when the ESET PROTECT Cloud instance is available.

9.Click Continue. Alternatively, click Dashboard, click Open in the ESET PROTECT Cloud tile to open a new tab with ESET PROTECT Cloud Web Console.

ESET PROTECT Cloud synchronizes your ESET Business Account structure to the Static Group tree in Computers in the Web Console.

II. Migrate Policies from the on-premises ESET PROTECT to ESET PROTECT Cloud

1.Log in to your on-premises ESET PROTECT.

2.In your on-premises ESET PROTECT, select Policies > All > select the check box in the table header (or select the check boxes next to policies you want to export) and click Actions > Export.

Do not export any ESET Management Agent policies.

Ensure you fully unassign all active Agent policies before the migration.

export_policies

3.Save the .dat file with the list of Policies.

4.In ESET PROTECT Cloud, click Policies > Actions > Import and select the .dat file with the list of policies exported from ESET PROTECT in step 2 and click Import to import them to ESET PROTECT Cloud.

cloud_import_policies

5.The imported policies will appear under Custom Policies. After the migration of computers from ESET PROTECT to ESET PROTECT Cloud, policies that were assigned to computers in ESET PROTECT are not preserved. After importing Policies to ESET PROTECT Cloud, you can assign them to imported computers in ESET PROTECT Cloud.

Be careful when applying policies to computers:

a)In your on-premises ESET PROTECT: Make the list of applied policies and their order for each managed computer.

b)In ESET PROTECT Cloud: Apply policies to each computer based on the policy setup from the on-premises ESET PROTECT.

III. Migrate Dynamic Group Templates from the on-premises ESET PROTECT to ESET PROTECT Cloud

1.In your on-premises ESET PROTECT, select More > Dynamic Group Templates.

2.Select the check boxes next to the dynamic group templates you want to export and click Actions > Export.

export_dg_templates

3.Save the .dg file with the exported dynamic group templates.

4.In ESET PROTECT Cloud, click More > Dynamic Group Templates > Import and select the .dg file with the dynamic group templates exported from ESET PROTECT and click Import to import them to ESET PROTECT Cloud.

cloud_import_dg_templates

5.The imported dynamic group templates will appear in the list of all dynamic group templates, and you can use them to create dynamic groups (you cannot migrate dynamic groups).

IV. Migrate Report templates from the on-premises ESET PROTECT to ESET PROTECT Cloud

1.In your on-premises ESET PROTECT, select Reports.

2.Click the gear icon next to a report category or an individual report template and click Export.

export_reports

3.Save the .dat file with the exported report templates.

4.In ESET PROTECT Cloud, click Reports > Import Report Templates and select the .dat file with the report templates exported from ESET PROTECT and click Import to import them to ESET PROTECT Cloud.

Repeat the steps above to migrate more individual report templates or more report categories.

cloud_import_reports

5.The imported report templates will appear in Reports. You can use the report templates to schedule and generate reports.

V. Migrate ESET Management Agents (managed computers) from the on-premises ESET PROTECT to ESET PROTECT Cloud with Migration policy

Before the migration of Agents, ensure that your firewall settings meet the ESET PROTECT Cloud network prerequisites.

1.In ESET PROTECT Cloud Web Console, click Quick Links > Download Migration Policy and save the .dat file.

cloud_dwn_mig_pol

2.In your on-premises ESET PROTECT, select Policies > Import. Select the downloaded .dat file from the previous step and click Import.

policy_import

3.Navigate to Custom Policies and select your imported migration policy.

mig_pol_assign

4.Click the migration policy > Edit.

5.In Settings > Connection, set the Force flag for Servers to connect to and Certificate.

6.Click Finish.

Test the migration on a few machines

We recommend migrating a few computers to which you have physical access. Ensure they can connect to ESET PROTECT Cloud and then migrate all computers.

7.Click Assign > Assign groups.

8. Select the All Static Group and click OK.

•Apply the migration policy to the All Static Group to ensure that you migrate managed computers.

•After the migration, all computers will appear in the Lost & found Static Group in ESET PROTECT Cloud.

•If you are a Managed Service Provider with a multi-tenant setup, repeat these steps for each Static Group to ensure that migrated computers are in their original Static Groups:

a)Select the Static Group.

b)Allow computers to migrate.

c)Move the migrated computers to the corresponding Static Group in ESET PROTECT Cloud.

cloud_select_targets_all

9. Click Finish to apply the policy.

10. Log in to your ESET PROTECT Cloud Web Console. In Computers, you will see the computers migrated from ESET PROTECT. You may need to wait a few minutes until all computers from ESET PROTECT start connecting to ESET PROTECT Cloud.

11. After you migrate computers from ESET PROTECT to ESET PROTECT Cloud, you must re-activate ESET security products on the managed computers with cloud licenses managed by ESET PROTECT Cloud:

a.In ESET PROTECT Cloud Web Console, click Computers > click the gear icon next to the All Static Group > select Tasks > New Task.

b.Select Product Activation in the Task drop-down menu.

c.Select the ESET security product license in Settings, review the target computers in Target and click Finish.

If the computers run various ESET security products, you must repeat the activation steps and select the appropriate license for each ESET security product category.

d.Wait a few minutes until the ESET security products are activated.

VI. Migrate mobile devices

VII. Set up ESET PROTECT Cloud users in ESET Business Account

VIII. Add ESET Business Account users to ESET PROTECT Cloud Web Console

IX. Decommission the on-premises ESET PROTECT Server

After successfully migrating to ESET PROTECT Cloud, decommission the on-premises ESET PROTECT Server.

If you keep the on-premises ESET PROTECT Server, disable the Delete Not Connecting Computers task to prevent the possible deactivation of ESET security products on computers managed by ESET PROTECT Cloud.

˄˅