Upgrade the Tricentis License Server

If you are already using an earlier version of the License Server and you want to upgrade your software to the version 7.0, this topic is for you.

This topic offers a step-by-step guide on how to upgrade to License Server version 7.0.

Upgrade to version 7.0

To upgrade your License Server to version 7.0, follow these steps:

The License Server version 7.0 is not able to read usage data produced in version 6.2 or the ones before. For this reason, we advise you to retrieve and save any usage data (opens in new tab) you wish to keep from your earlier License Server version before you upgrade.

  1. Create a backup of your trusted storage in case you run into issues during the upgrade.

  2. Create a backup of the LicenseUsageStatistics.dll.config file in <your installation directory>/License Usage Tracking. This is only necessary if you have changed values or added custom values to the file.

    When you uninstall the Tricentis License Server, the system automatically deletes the file. If you create a backup, you can populate the new file with the values from your backup after you install the new server.

  3. If you intend to install the new license server on a different machine than the old license server, deactivate your licenses from the old machine.

  4. Download the setup file Tricentis License Server<version number>.msi from the Tricentis Support Hub.

  5. Uninstall the old license server.

  6. Make sure that your machine has the required versions of the following software:

    • Microsoft® .NET Hosting Bundle (64-bit required)

    • Microsoft® Visual C++ Redistributable package

    • Oracle Java Runtime Environment or OpenJDK

  7. Run the setup file of the new license server and follow the installation process described in Install an on-premise license server.

  8. Populate the values of appsettings.json file in your License Server version 7.0 installation with the corresponding custom values from your backup of the LicenseUsageStatistics.dll.config file.

    After a default installation, the appsettings.json file is located at C:\Program Files\TRICENTIS\Tricentis License Server\License Usage Statistics\Tracking.

    Don't replace the new file with your backup or overwrite the entire content of the new file.

  9. If you installed the new Tricentis License Server on a different machine than the old license server, activate your licenses on the new machine:

Changed functionality

This section explains changed functionality of Tricentis License Server, compared to previous versions.

New Tricentis License Usage Statistics service

We introduced the Tricentis License Usage Statistics service that tracks license usage and produces license usage reports. This service combines the functionality of Tricentis License Usage Reporting and Tricentis License Usage Tracking from the previous versions of License Server (opens in new tab) which we deprecated. This update comes with the following notable changes:

  • The default port for Tricentis License Usage Statistics service is 7071. Where the Tricentis License Usage Tracking database default port was 9200.

  • The default Tricentis License Usage Statistics data retention period is 365 days. By default, Tricentis License Usage Tracking database saved data indefinitely.

  • We now store the Tricentis License Usage Statistics settings in the appsettings.json file. After a default installation, you can find this file at C:\Program Files\TRICENTIS\Tricentis License Server\License Usage Statistics\Reporting for reporting settings, and at C:\Program Files\TRICENTIS\Tricentis License Server\License Usage Statistics\Tracking for tracking settings. The settings for the deprecated services were in the LicenseUsageStatistics.exe.config file at C:\Program Files\TRICENTIS\Tricentis License Server\License Usage Tracking.

  • The License Server can only fetch data from the machine you installed it on.

New account set up behavior

The new administrator account you create during the setup of the License Server version 7.0 will always admin as its username.