Business article search

How do I migrate ESET Remote Administrator (5.x) from an old server to a new one?

Before migration

  • 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:

  1. Upgrade your ESET Remote Administrator (ERA) to the latest 5.x build.  
     
  2. Install ESET Remote Administrator Console and Server on your new server. You can skip the entry of your license, username, password, etc. during installation. You will import the settings from your existing installation later.
     
  3. On your new server, create a Windows Firewall Exception for ERA. See the appropriate example below for programs to exclude:
    • 32-bit systems
      C:\Program Files\ESET\ESET Remote Administrator\Server\era.exe
      C:\Program Files\ESET\ESET Remote Administrator\Server\ehttpsrv.exe
       
    • 64-bit systems
      C:\Program Files (x86)\ESET\ESET Remote Administrator\Server\era.exe
      C:\Program Files (x86)\ESET\ESET Remote Administrator\Server\ehttpsrv.exe

       
  4. Stop the ERA server service on your new server.
     
  5. Stop the ERA server service on your old server.
     
  6. 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 Settings\All Users\Application Data\ESET\ESET Remote Administrator\Server\
       
    • Windows Server 2008, 2011/ Windows 7, 8: C:\ProgramData\ESET\ESET Remote Administrator\Server\
       
    • Windows Server 2012: C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\
       
  7. 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.
     
  8. 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
     
  9. 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).
    • 32-bit systems
      "C:\Program Files\ESET\ESET Remote Administrator\Server\era.exe" -server_name_repair
       
    • 64-bit systems
      "C:\Program Files (x86)\ESET\ESET Remote Administrator\Server\era.exe" -server_name_repair

    Default locations

    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.

  10. On your new server, start the ERA server service.
     
  11. On your new server, open ESET Policy Manager and replace all instances of your old server's hostname and/or IP address with the hostname and/or IP address of your new server.
    1. Open ESET Remote Administrator Console.
       
    2. Click ToolsPolicy Manager.
       
    3. Select your default policy for clients and click Edit policy.
       
    4. Replace all instances of your old server's hostname and/or IP address with the hostname and/or IP address of your new server.
       
    5. Click ConsoleYes when you are finished.
       
    6. Repeat steps c-e for any additional policies that clients subscribe to.
       
  12.  
  13. On your new server, replace all instances of your older server's hostname in your existing Installation packages with the hostname of your new server.
    1. Open ESET Remote Administrator Console.
       
    2. Select the Remote install tab.
       
    3. Click Actions→ Manage packages.
       
    4. Use the Type and Name drop-down menus to select an installer package.
       
    5. Click Edit under Edit/Select configuration associated with this package.
       
    6. Replace all instances of your old server's hostname and/or IP address with the hostname and/or IP address of your new server.
       
    7. Repeat steps d-f for all existing installation packages.
  14. On your old server, start the ERA server service.
     
  15. On your old server, configure your clients to report to the new server.

Suggested step

You should consider performing the following steps to improve your migration experience.

 


Was this information helpful?