Points to remember before the migration.

  • eG License file tied up with MAC ID/IP address of the eG Manager server, so before migrating to the new eG server please fill the attached change IP/MAC request form attached with this document. Download the form, fill it, sign it, scan it and send it across to us. Once you have the updated license for the new manager, then start the migration procedure.
  • During the time of eG Agent installation on your environment, all the eG Agent has been configured with the eG manager Hostname/IP. And so if you are planning to migrate eG manger to the a different server, make sure to retain the IP and Hostname of the old eG manager server to the New Manager.
  • Example: on the current eG manager, If the ip address is and hostname is ‘eGtool’. Then you have modified the same IP and hostname on the new eG manager server.
  • Incase if you can’t retain the Hostname/IP address of the current eG manager, then please contact your AD Team to create a DNS mapping for the new manager hostname to old manager hostname. So that if communication from the eG Agent comes to the old manager will be automatically redirected to the New eG manager.

If the above points are satisfied, please following the step by step instruction in the same order to complete the eG Migration.


Current Manager Server:

  • During the migration, current eG Manager and Agent services must be down. Hence Stop the eG Manager and Agent as Administrator on the windows Start Menu
  • Just to be on the safer side, please take backup of the egurkha folder on the current eG manager server into a different drive. Also, take back up of eG database or snapshot of the eG Database server. 

New Manager Server:

  • On the new eG Manager server, please make sure you have the same or more hardware and software specification as that on the old manager. 
  • Go to the new server and do a fresh eG Manager Installation. During the new installation, eG manager installation process can’t be completed by creating a new DB and user. But we must use the existing old DB and user. Hence during the new installation continue to process by providing a new Database and user. Once the installation is completed, we can point to the new eG Manager to the existing database and user. Then you can delete the dummy database and user that you have created at the time of installation.
  • For installing a Fresh manager, please follow the instruction on the given link ( eG Manager installation procedure)
  • Once the installation is completed you can copy the new license file that should have received from eG before the installation to an egurkha\bin folder
  • Reboot the New Manager server and when it is up, open the eG console using the browser
  • Once you get the eG Manager console, then Stop the manager using windows start menu.
  • Take a backup of the entire egurkha folder in a different location.

Migration - Configuration:

  • From the old eG manager server, copy the config folder located on the egurkha\manager folder, and move it to the new eG Manager server. On the new eG manager server got the same location egurkha\manager folder. Then replace the config folder that you have taken from the old manager (Overwrite all the files).
  • As mentioned earlier, the new eG manager server has to be configured with the old eG Manager server hostname/ip addressMake. Hence note of the IP and hostname of the old eG Manager server, then change the IP & Hostname and the shut down the server.
    • Example: The old manager server ip address: and hostname: ‘currentmanagerserver’. Make a note of those details. Now change the hostname on the current eG manager from to, then again change the hostname from ‘currentmanagerserver’ to ‘oldmanagerserver’.
    • Once the changes are done. Shut down the current eG Manager.
  • On the new eG Manager server modify the IP & Hostname of the new manager server same as old server and reboot the server.
    • Example: New eG Manager ip: and hostname is ‘newmanagerserver’. Change the new Manager IP from to Likewise, change the hostname from ‘newmanagerserver’ to ‘oldmanagerserver’
  • Now reboot to new eG Manager in order to make the changes take effect.
  • Once the server is up, stop the eG manager using the start menu.
  • Open a command prompt as administrator. Go to egurkha\lib and run the file ChangeManagersetting.bat. Then provide New manager server information as given on the example screenshot below.

  • On the same command prompt run the file mgrdebugoff.bat as administrator on the egurkha\lib folder.
  • Finally, start the new eG Manager using the windows menu as an administrator.