Admin Tasks: Allocation Accounts

This section, too, deals with admin-only tasks.

Note: The “License Server Access Token”, needed on the PC (see section6.9.1), must not be mapped to license servers.

account.

Each device (PC) running TEMS Investigation belongs to one and only one allocation account, as does each license server. However, an allocation account may hold multiple license servers, among which the entitlements are distributed. See the diagram below for an example.

6.18.2. Creating a New Allocation Account

• Navigate to Administration  Manage Groups. A list of existing allocation accounts appears.

• Click the button Create New Allocation Account.

• Define the following parameters:

Name Enter a name for the allocation account.

Note Free-text field.

Chapter 6. GLS Licensing

• Click the button Add Allocation Account at the bottom of the page. The new account is now created and added to the list.

• If you need to change the account parameters later on, navigate to Administration  Manage Groups again and click the account of interest. On the screen that appears, edit parameter values as needed.

6.18.3. Switching Between Allocation Accounts

• To switch from one allocation account to one another in the GLS web interface, click the Switch Account link at the top of the page. Select the account you wish to use.

6.18.4. Transferring Entitlements Between Allocation Accounts

Here is how to transfer an entitlement, or a part of it, from one allocation account to another.

6.18.4.1. Transferring a Whole Entitlement

• Navigate to Entitlements  Entitlement History. A list of entitlements appears.

• On the Transfer Order screen, in the To Account drop-down box, select the account the entitlement should be moved to. Then click Submit.

Transferring an entitlement in its entirety also moves its associated devices (that is, all devices currently having add-ons from that entitlement mapped) to the new allocation account.

If a device has add-ons mapped from more than one entitlement, none of these entitlements can be transferred to a different allocation account. For an entitlement to be transferable, all devices that are using add-ons from it must first have any add-ons from other entitlements unmapped.

End Date, Maximum Borrow Interval

Here you define the license validity parameters explained in section6.9.4. All license servers belonging to an allocation account will use the same values for these parameters.

Locate the entitlement you want to transfer, and hover over its Actions icon on the far right. Click Transfer in the bubble that appears.

• On the Split Line Item screen, do the following:

– In the To Account drop-down box, select the account the item should be moved to.

– Under Quantity to Allocate, specify how many of these items you want to move.

• Then click the Submit button.

• Repeat for any other items you wish to transfer.

6.18.5. Using Allocation Accounts to Control User Privileges

A special application of allocation accounts is to controlling user privileges in GLS.

Each person who is going to install and use TEMS Investigation must have a user in the GLS web interface to be able to register their PC with the licensing system. However, in a scenario where regular TEMS Investigation end-users are not supposed to perform any other tasks directly through the GLS web interface, their GLS users should have their privileges restricted accordingly.

Here is a suitable way to set this up:

• Create a special allocation account for the purpose and call it something like “<company name> – Device Registration”. Do not transfer any part of the entitlements to this account.

• Create users as needed within the “registration” account (Administration

 Manage Groups  Add New Member button). With no entitlements present, the users’ privileges will be limited to registering PCs on the

the far right. Click Split in the bubble that appears.

Chapter 6. GLS Licensing

• After each user has registered, move the user’s device to a “regular”

allocation account (like one of those in the diagram in section6.18.1) where the user can map add-ons through License Control Center.

6.18.6. Moving Devices Between Allocation Accounts

6.18.6.1. Node-locked Licenses

A device can be moved to a different allocation account without further ado provided that all of its add-ons are in state “License generated”, that is, the set of add-ons is not being modified.

If you move a device while some add-on is being mapped (add-on in state

“License not generated”), then the mapping can no longer complete and will be canceled. You will be notified of this fact in the GLS web interface. The add-on will remain with the old allocation account and will be available there.

If you move a device while some add-on is being unmapped (add-on in state

“Copies decreasing”), then the unmapping will be completed before the move, so that the add-on is returned to the old allocation account.

6.18.6.2. Floating Licenses

If you want to move a device to a different allocation account, you must first return any and all floating add-ons currently mapped to the device:

• Navigate to Device Management  Search Servers, and click the relevant license server.

• Click the View Served Clients link, and locate the device you want to move.

• Click the device to expose the Features list. In that list, check that all floating add-ons have a zero in the Count column. Return them if necessary.

Note: GLS performs no validation in this regard, so you must yourself ensure that all floating licenses are returned before you move the device.

TEMS Investigation and how it is handled in practice.