CARIS Onboard : CARISĀ® Licensing Guide : Commuter Licenses : How It Works
 

How It Works

A commuter license allows a network license to temporarily be used as a local license. This is ideal for users working away from their local workstation without access to a license server.

A commuter license is created by performing a check-out from a license server. A check out creates a license file on the local machine containing the details of the license. This license file is then applied in the application and functions as a local license.

During check out, the user selects which licensed modules to include in the commuter license. This can be any module license that would normally be available on the license server with a network commuter license. The license server contains a limited number of licenses for each module. When a license has been checked out, the License Manager will show that the license is in use and is not available to other users. If all licenses for a module are already in use, this module cannot be checked out. Hovering the mouse cursor over the In Use column in License Manager will display a tooltip identifying which users are using the selected license. The tooltip also indicates if the license is being used as a commuter license.

Commuter licenses are meant to be for temporary use only. When creating a commuter license, the user must specify the number of days that the license will be needed. Licenses can be checked out for a maximum of 90 days. If the commuter license is no longer needed, it can be checked back into the license server at any time during the specified time period, making the module licenses available to other users. At the end of the specified time period, the commuter license will automatically be revoked if it has not already been checked in by the user.

To check in a license, the physical license file on the local computer is required. If a license file is lost or corrupted while checked out, the module licenses in that file will be unavailable until the license expires and is automatically revoked. For example, if the laptop containing the license file experiences a hard drive failure and the license file cannot be recovered, there is no way to check that license back into the license server. In this situation, the module licenses will remain locked in use until the license expires.