Local License Server

We offer an on-premise license server solution for facilities with air-gapped computers. Available for Linux, FreeBSD, macOS, and Windows, the Local License Server acts as a floating license server for client licenses.

Preliminaries

A Local License Server consists of a client license enabled for local license usage and a machine or VM in your local network running the Local License Server application. An MDM solution is recommended for bulk setting changes on client apps and distribution of app updates.

When you need a Local License Server deployed, contact our team first. We'll help you set up your licenses and guide you through the (straightforward) deployment process.

Setting Up The Server

A Local License Server can run on a different operating system than your workstations. For example, a common scenario is having the server running on Linux, and workstations run on a combination of Windows and macOS.

Important: any instance of the Local License Server manages a single license. If you need to deploy multiple licenses or apps, you'll need to deploy multiple instances for the Local License Server.

Requirements

The Local License Server will run on almost all hardware, requiring practically no resources.

Windows

• Windows 10 or newer

• Administrator privileges

• Firewall access for the chosen port (default is 20000)

• An internet connection for activation and daily license checks.

Linux

• Ubuntu 18.04 or higher. Other distributions may work just as well, but we tested Ubuntu.

• sudo or root privileges

• unzip and wget

• An internet connection for activation and daily license checks.

Preparation

1. Download and install the Local License Server application:

Windows

https://downloads.hedge.video/licenseserver/LocalLicenseServerWindows.zip

1. Extract the contents to a directory of your choice (e.g., C:\LocalLicenseServer)

2. Ensure you have the following files in the directory:

   • LocalLicenseServer.exe

   • TurboActivate.dat

   • LocalLicenseServer.xml

Linux

https://downloads.hedge.video/licenseserver/LocalLicenseServerWindows.zip

1. Extract the contents to a directory of your choice, e.g., ~/LocalLicenseServer

2. Ensure you have the following files in the directory:

   1. bin-linux

   2. LocalLicenseServer.xml

Configuration

1. Open LocalLicenseServer.xml in a plain text editor

2. Set the port number: <bind port="20000"/> (change 20000 to your desired port)

3. Set the log location (required for Linux): <log file="tfs-log.txt" level="warning" />

4. Save the configuration file

License Installation

1. Open an elevated command prompt, run as Administrator if you're not already doing so.

2. Navigate to the Local License Server directory

3. Run the following command:

.\LocalLicenseServer.exe -a="XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX" -config="LocalLicenseServer.xml"

Starting the Server

Windows

Run the Server as a Windows Service to ensure it's always up and running.

1. Open an elevated command prompt

2. Navigate to the Local License Server directory

3. Run the following command: .\LocalLicenseServer.exe -i -config="LocalLicenseServer.xml"

The server starts automatically with Windows. When running as a service, firewall rules are added automatically to allow incoming connections on the configured port.

Linux

Linux has many approaches to keep services or daemons running. At this point, we don’t offer a full installation that autostarts after a reboot. You can create an autostart script yourself for Crontab, Systemd, system V init, Upstart, or whatever your using.

Start the process using the following command:

.\LocalLicenseServer -config="LocalLicenseServer.xml"

License Changes

The commands are equal for Linux and Windows. Just ensure you use the right program name: on Windows, LocalLicenseServer has a .exe extension.

1. Open an elevated command prompt

2. Navigate to the Local License Server directory

3. Shut down the service by running the following command:

.\LocalLicenseServer.exe -u -config="LocalLicenseServer.xml"

4. Update the license information by running the following command:

.\LocalLicenseServer.exe -a="XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX" -config="LocalLicenseServer.xml"

5. On Windows, restart the service by running the following command:

.\LocalLicenseServer.exe -i -config="LocalLicenseServer.xml"

Deinstallation

1. Open an elevated command prompt

2. Navigate to the Local License Server directory

3. Run the following command:

.\LocalLicenseServer.exe -u -config="LocalLicenseServer.xml"

License Deactivation

1. Open an elevated command prompt

2. Navigate to the Local License Server directory

3. Make sure the service is uninstalled

4. Run the following command:

.\LocalLicenseServer.exe -deact -config="LocalLicenseServer.xml"

Troubleshooting

• Check the LocalLicenseServer.log file in the server directory for error messages.

• Ensure access to the server is allowed through the firewall.

• Verify that the specified port is open and not in use by other applications.

The Client

The client app can be installed like a regular app, or via MDM. After installation, switch the licensing method from Remote Activation to Local Activation. Each of our apps using dedicated API calls, in this example we use mimiq.Simply replace mimiq:with the app name you are deploying the Local License Server for.

Switch to Local Activation:

mimiq://licenseactivation?mode=local&ipAddress=192.168.1.1&port=8080

Switch back to Remote Activation:

mimiq://licenseactivation?mode=remote