When purchasing a ThinLinc subscription, some have the need to divide the associated ThinLinc licenses over multiple separate ThinLinc clusters. This article describes how that can be done.
Dividing a license bundle
When buying a ThinLinc subscription, you will get a ZIP archive with your licenses. Typically, this ZIP is installed to /opt/thinlinc/etc/licenses on the master server (or both master servers in an HA pair).
However, this ZIP can also be unpacked, revealing several .license files. These files are valid for either 1 or 10 users, as made evident by their file names, and can be installed instead of the license ZIP. These .license files can be spread over multiple separate clusters.
When doing this, be cautious to not use the same .license file in more than one cluster. Similarly, make sure to not install the license ZIP archive when using the individual .license files. For more information, see the Cendio End User License Agreement.
.license file sizes
.license files primarily come in sizes of 10 concurrent users. Files for 1 concurrent user are then used to cover up the remainder to reach the total license count.
To exemplify, a license ZIP for 35 concurrent users will contain:
- 3 files valid for 10 users
- 5 files valid for 1 user
In case another distribution of license files is desired, we can arrange that. In such cases, please let us know as early as possible so we don’t get to a point where licenses with the wrong distribution are issued.
Community licenses
In contrast to the licenses associated with a paid ThinLinc subscription, the free 10-user community licenses cannot be split.
Notable mention: Subclusters
In case there is no need for a user to have access to more than one of the multiple clusters, and a hard separation between the clusters is not a requirement, it is also possible to set up a single cluster with multiple subclusters.
With this approach, you will get to reap the license pooling benefits of a single cluster while still getting some of the benefits of multiple clusters.