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 10 or newer
Administrator privileges
Firewall access for the chosen port (default is
20000
)An internet connection for activation and daily license checks.
Preparation
Download and install the Local License Server application:
https://downloads.hedge.video/licenseserver/LocalLicenseServerWindows.zip
Extract the contents to a directory of your choice (e.g.,
C:\LocalLicenseServer
)Ensure you have the following files in the directory:
LocalLicenseServer.exe
TurboActivate.dat
LocalLicenseServer.xml
Configuration
Open
LocalLicenseServer.xml
in a plain text editorSet the port number:
<bind port="20000"/>
(change20000
to your desired port)Set the log location (required for Linux):
<log file="tfs-log.txt" level="warning" />
Save the configuration file
License Installation
Open an elevated command prompt, run as Administrator if you're not already doing so.
Navigate to the Local License Server directory
Run the following command:
Starting the Server
Run the Server as a Windows Service to ensure it's always up and running.
Open an elevated command prompt
Navigate to the Local License Server directory
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.
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.
Open an elevated command prompt
Navigate to the Local License Server directory
Shut down the service by running the following command:
Update the license information by running the following command:
On Windows, restart the service by running the following command:
Deinstallation
Open an elevated command prompt
Navigate to the Local License Server directory
Run the following command:
License Deactivation
Open an elevated command prompt
Navigate to the Local License Server directory
Make sure the service is uninstalled
Run the following command:
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:
Switch back to Remote Activation:
Last updated