Skip to main content
NOT AVAILABLE IN SAAS.
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 Exposure Management secrets and certificates

If the Endpoint Exposure Management module is not installed, skip this step.
  • On the source computer, open a command prompt and navigate to the <Syteca Server Installation Folder>\EEM directory.
  • Run the following command: eem_configtool secrets backup [--with-config=true]
    • The --with-config parameter 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=false if you only need to transfer the Endpoint Exposure Management binaries or plan to configure the new environment manually.
  • When prompted, specify a password to protect the backup archive.
  • The backup file, eem_<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.
4

Restore Endpoint Exposure Management secrets and certificates

If the Endpoint Exposure Management module is not installed, skip this step.
  • On the new computer, open a command prompt and navigate to the <Syteca Server Installation Folder>\EEM directory.
  • Run the following command: eem_configtool secrets restore [--with-config=true] [--force] <moved archive path>
  • When prompted, enter a password to extract data.
5

Update Clients if the address changed

If the new computer has a different hostname or IP address, update every Client to point at it.
1

Disable Protected mode first

This step can’t be done while Protected mode is enabled — disable it before continuing.
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).
3

Restart the Client computer

Restart to apply the change.
To avoid updating every Client manually, reinstall them instead using the .exe + .ini installation package pointed at the new address.
6

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.
EkranMasterCertificate and HKEY_LOCAL_MACHINE\SOFTWARE\EkranSystem\Client are literal system identifiers, preserved verbatim from source.

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.