Migrating or Renaming Seeq Server

Instructions for moving Seeq to another computer or changing its name; may be done concurrently with an upgrade.

Changing the Seeq Server Hostname

Changes to the hostname of any Seeq server, requires updating the license and may require updating the HTTPS settings.

Updating License

1. Request an updated license file from Seeq by creating a licensing ticket with us here. Please be sure to provide the new server name.

2. Copy the new license to the C:\ProgramData\Seeq\licenses folder.

3. Restart the Seeq service.

Updating HTTPS settings

You only have to update these settings if you use HTTPS and if you use the server's hostname or FQDN when accessing Seeq's user inteface in a browser.

If Seeq Server's configured hostname is set to something that's not the server's hostname or FQDN (such as an alias), you don't have to make any updates here.  To check:

• Check the value of the Network/Hostname option as described in Configuring Seeq.

To update HTTP settings, follow these steps:

1. Update the configured hostname to the server's new hostname on the Seeq server and all Remote Agent servers

   • Update the Network/Hostname option as described in Configuring Seeq.

2. Create a new certificate and key for the server tied to the server hostname (either with the server's name or an applicable wildcard). If the old certificates are wildcarded to match the new server as well, you don't have to update the certificate files.

3. Make sure the certificate and key are the correct format and have the names seeq-cert.pem and seeq-key.pem.

4. Move the two PEM files to the keys folder in the Seeq data directory (by default located in C:\ProgramData\Seeq\data\keys).

5. Copy the two PEM files to the keys folder on all remote agent servers.

6. Restart Seeq.

Migrating Seeq to a New Server

The following steps have to be done for all migrations to a new server:

1. Install Seeq on the new server. Please make sure to use the same version (check this link if you need to download an older version of Seeq not available on the main downloads page) or a newer version than what was previously installed. If you are upgrading as part of this process, please make sure to upgrade all Remote Agent servers as well.

2. Copy the data directory to the new server; to find it:

   • Check the Folders/Data option as described in Configuring Seeq.

3. Copy the global configuration file (the global_config.json file in your global folder) to the new server.

4. If the data folder location will be different on the new server, update the Folders/Data option as described in Configuring Seeq.

5. In Windows Services, under properties for the Seeq Server service, make sure the Seeq Service is set to startup Automatically.

6. Change the account running Seeq (under the Log On tab) to the service account that was running Seeq on the older server. Please be aware that Windows does not verify the password for the account when you enter it, so be sure it is the correct one.

   1. If you are changing the service account that will run Seeq, make sure it has the same access to historians and data sources that the old account had.

7. Double check that the service account has Full Access permissions to the seeq data directory on the new server and any sub-directories and files (you may have to apply permissions recursively).

If the new server will have the same hostname as the old server, you won't have to make any further changes. If the hostname will be different, please also follow the steps in the Changing the Seeq Server Hostname section to update the license and HTTPS settings (if applicable).

Migrating Seeq DataLab (SDL) to a New Server

The following steps have to be done for all migrations to a new server:

1. Install Seeq DataLab on the new server. Please make sure to use the same version (check this link if you need to download an older version of Seeq DataLab not available on the main downloads page) or a newer version than what was previously installed.

2. Copy the data directory to the new server.

   • To find the data directory check the Folders/Data option by running seeq config get Folders

3. Copy the global configuration file to the new server.

   • This is the global_config.json file in your global folder listed in the output from the command in step 2.

4. If the data folder location will be different on the new server, please be sure to change it to reflect this.

   • Update the Folders/Data option as described in Configuring Seeq.

5. If the Seeq Server URL changed as part of the move you will need to follow the “Configure” steps on the SDL Installation page.