1
Back up and import the master certificate
Back up the master certificate on the original computer, and import it on the new one.
2
Back up Endpoint Risk & Compliance Control secrets and certificates, if you have not done it during installation
If the Endpoint Risk & Compliance Control module is not installed, skip this step.
- On the source computer, open a command prompt and navigate to the
<Syteca Server Installation Folder>\ERCCModuledirectory. - Run the following command:
riskscore_configtool secrets backup [--with-config=true]- The
--with-configparameter is optional. Use it to include all Endpoint Exposure Management server module configuration settings in the backup when migrating to a new environment. The default value istrue. - Set
--with-config=falseif you only need to transfer the Endpoint Exposure Management binaries or plan to configure the new environment manually.
- The
- When prompted, specify a password to protect the backup archive.
- The backup file,
ercc_<date>.backup, is created. - Copy the backup file to the destination computer.
3
Install Syteca on the new computer
Run the installer and select the same database already in use. If binary data is stored in a folder rather than the database, transfer that folder to the new computer first and point the installer at it.During installation, if the Endpoint Risk & Compliance Control Module is selected, select the secrets backup location and enter the password.
4
Update Clients if the address changed
If the new computer has a different hostname or IP address, update every Client to point at it.
- Windows
- Linux
1
Disable Protected mode first
2
Update the registry
Open Registry Editor, go to
HKEY_LOCAL_MACHINE\SOFTWARE\EkranSystem\Client, and set RemoteHost to the new IP address or hostname (or both, separated by a semicolon).If you are using Endpoint Risk & Compliance Control, make sure that the hostname is entered.
3
Restart the endpoint or Client service
To apply the changes, restart this endpoint or Client service.
5
Confirm the data is intact
All monitored data and Syteca settings remain in the database — the new Application Server just needs to connect to the existing one.
Related
Moving the MS SQL Database
Move the database itself to a new computer instead of (or alongside) the Application Server.
Master certificate
Back up, export, and import the master certificate.
Client Troubleshooting
Diagnose Clients that lose connection after a migration.