Migration scenario 3

This scenario covers a migration to ESMC 7.x where endpoints connect to old ERA 5.x until the ESET Management Agent is deployed by ESMC 7.x. This scenario is useful if you wish to see how ESMC 7.x would look like with your data from ERA 5.x, but still have endpoints connecting to your ERA 5.x.



This scenario is for highly skilled users only. We do not recommend this type of migration unless there is no other option.

1.Download and run the ESET Remote Administrator Migration Tool.

Install Microsoft Visual C++ 2017 x86, it is required for Migration Tool to work properly. You can find it in the .zip file containing the Migration Tool.

Run the Migration Tool as Administrator, locally on your old ERA 5.x sever. It is not possible to run Migration Tool from a remote machine.

2.Selects the Export option to save the data from ERA 5.x to an intermediate database file. Migration wizard is able to transfer specific data only:


3.Select a save folder for the intermediate database.


4.The wizard displays the status of archival of the ERA 5.x database.


5.All data is exported to an intermediate database.

6.If ESMC 7 will be installed on the same computer as ERA 5.x, you must perform the following actions:

Change your ERA ports in the ERA Console: Tools > Server Options > Other Settings tab.

Change the port 443 in C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\era_http_server.xml.

Rename the InstallDir registry key located in: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ESET\ESET Remote Administrator\Server\CurrentVersion\Info\

7.ESET Remote Administrator 5.x should be started again following the export of your data.

8.Install ESMC 7 and import the intermediate database using the Migration tool. You will be prompted to enter the IP address of the machine (that was displayed for ESMC Console in the Installation successful screen) in the Host field, the administrator password configured during installation and to select the saved database file.

9. If server settings do not allow the import of specific data, the ESET Remote Administrator Migration tool lets you choose whether you want to change settings in ESMC 7.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 selected to migrate users, their passwords are reset and replaced with randomly generated passwords. These passwords can be exported in the .CSV format.

10. You can use the Migration Tool to generate a script that can be used to preconfigure ESET Management 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 import was successful. After checking, use this script to deploy the ESET Management 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 to add the computers in Web Console and then deploy the Agent to them).



If any of the migration steps fail, you should roll back changes for ESMC 7.x, set the computers to connect to ERA 5.x, recover the backup data from ERA 5.x and contact ESET customer care.



This type of migration results in no logs exported between the process of backing up the ERA 5.x database and deploying the Agent on a client computer. However, the logs remain present on your old copy of ERA 5.x.