Migration scenario 2

This scenario covers migration to ESET Remote Administrator 6.x running on the same computer as ERA 4.x / 5.x. All ERA data should be backed up (using the ESET Maintenance tool) and ERA services in the operating system should be stopped before the migration of any data.

Watch our Knowledgebase instructional video, or visit our Knowledgebase article for illustrated step-by-step instructions to complete installation using the All-in-one installer.


Download the ESET Remote Administrator migration tool and then follow the steps below.

validation-status-icon-infoNOTE: If you receive a system error, ensure that you have installed the required Microsoft Redistributable Package.

1.After running the ESET Remote Administrator Migration tool on the ERA 4.x / 5.x machine, the administrator selects the Export option to save the data from ERA 4.x / 5.x to an intermediate database file. Migration wizard is able to transfer specific data only:


validation-status-icon-infoNOTE: It is not possible to transfer parametric groups and tasks from ERA 4.x / 5.x, because of the new design and functions of dynamic groups in ERA 6.x.


2.After selecting a save folder for the temporary database, the wizard will display the status of archival of the ERA 4.x / 5.x database.


3.All data is exported to an intermediate database.

After the successful data export and before ERA 6.x deployment, ERA 4.x / 5.x must be uninstalled. We recommend to restart the machine prior to continue with installation of ERA 6.x.

When new ERA 6.x is installed, exported database can be imported using the Migration tool. Administrator is prompted to enter the IP address of the machine (the one that was displayed concerning ERA Console in the Installation successful screen) into the Host field, the administrator password configured during installation and to select the saved database file.

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.