Migration scenario 3

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

validation-status-icon-infoNOTE: This scenario is for highly skilled users only. We do not recommend this type of migration unless there is no other option.

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:

migrationtool02

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.

migrationtool04

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.

migrationtool05

3.All data is exported to an intermediate database.

4.If ERA 6 will be installed on the same computer as 4.x / 5.x, you must change your old ERA ports and rename the server service (sc config ERA_SERVER DisplayName= “ESET Remote Administrator g1”).

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

6.Install ESET Remote Administrator 6 and import the intermediate database using the Migration tool. You will be prompted to enter the IP address of the machine (the one that was displayed for ERA Console in the Installation successful screen) in 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.

The consequence of this type of migration is that there won’t be any logs exported between the process of backing up the ERA 4.x / 5.x database and deploying the Agent on a client computer. However that data will still be present on your old copy of ERA 4.x / 5.x.