[KB2683] How do I migrate ESET Remote Administrator (5.x) from an old server to a new one?
End of support for version 5.2 and 5.3 of ESET Remote Administrator
This article applies to version 5.x of Remote Administrator. ESET Remote Administrator version 5.3 is currently in limited support status and will soon be in Basic support status.
ESET Remote Administrator version 5.2 is currently in Basic support status and will soon reach End of Life status. End of life status for both of these versions is expected to occur in December 2019. After this date, the products will no longer receive detection updates to protect against malware.
Make sure that you have sufficient free disk space and temporary disk space to perform this migration (the migration process requires 3-4 times more free disk space than the actual size of the database). Insufficient disk space is a common cause of migration failure.
Do not deactivate the older server until you are sure that your client workstations are communicating with the new server.
To migrate ESET Remote Administrator from an old server to a new one, complete the following step-by-step process:
On your old server, back up all files in the ERA Server directory (copy them to a safe location, preferably a portable medium such as a USB Flash drive or portable hard drive). The default location for the ERA Server directory varies depending on your operating system. Use the appropriate directory from the examples below:
Windows Server 2003 / Windows XP: C:Documents and SettingsAll UsersApplication DataESETESET Remote AdministratorServer
Windows Server 2008, 2011/ Windows 7, 8: C:ProgramDataESETESET Remote AdministratorServer
Windows Server 2012:C:ProgramDataESETESET Remote AdministratorServerconfiguration
Navigate to the ERA Server directory on your new server and copy the files from your old server (the files that you backed up in step 6) into the new ERA Server directory. Overwrite any duplicate files with the backups from your old server.
On your new server, navigate to the ERA Server directory (see step 6) and locate the file ERA.xml. Open ERA.xml using a text editor (for example, Notepad) and replace all instances of the hostname used by your old server with the hostname used by your new server
On your new server, modify the hostname in the database by starting the ERA server service using one of the following commands from an administrative command prompt (quotation marks should be included when you submit these commands).
"C:Program FilesESETESET Remote AdministratorServerera.exe" -server_name_repair
"C:Program Files (x86)ESETESET Remote AdministratorServerera.exe" -server_name_repair
The locations listed above are default locations. If ERAS was installed to a different location, adjust the commands above to use the new location of era.exe.