4. Detaching a license#
In some scenarios it may be required to detach a license from the license server for a limited time:
You need to plan a flight with MISSIONPLANNER but you will not have a connection to the license server.
Important
Only software licenses can be detached!
Hint
Detaching a license is recommended when the license should be on a different machine for a couple of days/weeks. When the license needs to be on a different machine for longer, then perform a license transfer.
4.1. Preparation#
Before detaching the license, visit http://localhost:1947/_int_/config_detach.html on the license server and configure it to company policies:
Enable/Disable detaching
Set max duration
Set number of reserved licenses (they stay on the license server)
There are two ways to detach a license from the license server: Online and Offline.
4.2. Online#
4.3. Offline#
This method works when the remote machine is not connected to the license server (e.g. the machine is in the field and a license is needed).
Offline detaching involves additional risk since the license is written to a file. If this file is lost before being attached to the remote machine, the license remains blocked until the configured detachment expiration date. Therefore, it is recommended to first test offline detaching for a short time period (e.g. 1 day). After this period expires, the license is automatically removed from the remote machine and becomes available again on the host.
4.4. Follow-up#
The products page displays that a license is detached:
When clicking on the number in the detached column, more information about the detached license is available: