To perform a server migration, you will first need to back up your settings and reactivate the Impero Server license code.
Note: log files for the Log Viewer are encrypted to each server and will require additional steps to migrate to a new server.
Please contact Impero Support to make sure the log files can be used on the new server before installing the new Impero Server
Note for non-US customers: the file cleverconfiguration.dat must be deleted to perform a successful migration.
The default location of the cleverconfiguration.dat file is C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Data
- On the old server
- Stop and disable ImperoServerSVC service from the Windows Services
- Navigate into C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Data
- Delete the following files: clients.txt, licence.xml, licence.xmlx, softwarelicencing.xml
- For non-US customers only: delete cleverconfiguration.dat as well
- Make a backup copy of the following folders in the new server/shared drive:
- C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Data
- C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Recordings
- C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\ConsoleLogs
- C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Inventory
- C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Patch
- C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\ScheduledReports
- C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Exam
- On the new server
- Install Impero Server
- Stop ImperoServerSVC service from the Windows Services
- Paste the backup folders into the Impero Server directory
- Navigate in C:\Program Files (x86)\Impero Solutions Ltd\Impero Server\Data\Logs (or wherever the admin has decided to store the logs) and delete the text folder.
- Start the service again
- Register the server
Your activation code will need to be reactivated, you can do this through the support portal or via email at support@imperosoftware.com.
Once done, we recommend creating/changing the new DNS entry.