Migration scenario 1

This scenario covers migration to ERA 6.x running on a different computer than ERA 4.x / 5.x. For more details and instructions, see Knowledgebase article for illustrated step-by-step instructions to complete installation using the All-in-one installer.

1.The first step in the migration process is to have ERA 6.x installed and running on another computer.

2.Start the ESET Remote Administrator Migration tool on the ERA 4.x / 5.x machine and select Export to save the data from the old ERA to an intermediate database file.

3.Migration wizard is able to transfer specific data only. Select the data you want to transfer and click Next.

migrationtool02

After you have selected a folder in which to save the temporary database, the wizard will display the status of archival of the ERA 4.x / 5.x database.

All data is exported to an intermediate database.

4.When data is finished exporting, there are two options you can choose from:

One option is to Finish the export, Copy the temporary database file to a server that is running ESET Remote Administrator 6.x, and import the data using the ERA Migration tool on that server.

A second option is to click Import now and import the data directly to ESET Remote Administrator 6.x over the network. Specify the connection and logon details of the new ERA Server.

validation-status-icon-infoNOTE: Static groups synchronized from Active Directory are ignored and will not be exported.

If server settings won’t allow for importation of specific data, the ESET Remote Administrator Migration tool will let you choose whether you want to change settings in ERA 6.x for specific components.

Each of the components is then imported. An import (migration) log is available for each component. After the import is complete, the Migration tool will display the results of the import process.

If you chose to migrate users, their passwords were reset and replaced with randomly generated passwords. These passwords can be exported in the .CSV format.

The migration tool wizard also generates a script that can be used to preconfigure ERA Agents on client machines. This script is a small executable .bat file distributable to client computers.

We recommend that you review migrated settings and data to make sure that importation was successful. After checking, use this script to deploy the ERA Agent on a small group of computers to check if they are connecting to the server correctly.

After the successful connection of the test group, you can deploy the Agent to the remaining computers (either manually or using an AD synchronization task).

validation-status-icon-infoNOTE: If any of the migration steps fail you should roll back changes for ERA 6.x, setup the computers to connect to ERA 4.x / 5.x, recover the backup data from ERA 4.x / 5.x and contact ESET customer care.