Manage, Allocate or Limit the Licenses for Monitored Devices (License Provisioning)

Use License Provisioning to limit the number of allowed devices reporting to Aternity, by controlling the Aternity device licenses, or you can manually allocate a license to a specific user/device. Aternity automatically assigns a license to a device which wants to report its performance.

For example, if you purchase 1000 device licenses, use License Provisioning to limit up to 500 monitored mobile devices. You can also manually allocate specific hostnames or usernames to guarantee that they would have a license reserved for them.

There are four types of licenses, one for each type of device:

Types of Aternity licenses depending on the type of reporting device
  • A Physical Device license is occupied by a single Windows or Mac computer (laptop, desktop, surface and so on).

  • A Mobile Device license is occupied when a mobile device runs a monitored mobile app (iOS or Android) and reports a unique device ID.

  • A Virtual Device license is occupied by a single virtual desktop (VDI), where the desktop image contains the Aternity Agent.

  • A Virtual App Session license is occupied by four frontline clients which run a virtual application from an virtual application server, where the server is running the Aternity Agent.

    Important

    A single virtual app session (frontline client) uses only a quarter of a license.

By default, the system reserves your manually allocated licenses, and automatically grants requests from any device type until it reaches the total licenses allowed.

Manually allocate a license, or allow the system to automatically allocate from the available licenses

You can also limit the number of licenses for each type of device. For example, if you purchase 1000 licenses, you can set a limit of up to 300 mobile devices.

Set a limit for each type of device
Note

After manually or automatically allocating a license, it remains occupied until the user/device stops reporting to Aternity for 14 consecutive days (non configurable). After that, the system automatically releases the license, making it available for another user/device.

If a device stops reporting to Aternity for any reason, including unavailable licenses, you can continue viewing its data by setting the dashboard's timeframe to cover its active reporting. Its reporting state or Agent status would show as Disconnected.

Procedure

  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 Select the Gear Icon > License Provisioning.
    License Provisioning page

    At the top of the screen it displays the current license status in your deployment:

    Field Description
    Total Licenses

    Displays the total number of licenses of all types which are available before any are allocated.

    Tip

    Your organization may be in the phase of gradually rolling out licenses. This is a normal part of license deployment, as more licenses are made available for allocation over time. Contact your enterprise's Aternity administrator if you need more licenses for allocation immediately.

    Gradual rollout of licenses
    Currently In Use

    Displays the total number of licenses of all types which are occupied, and the percentage of this number out of the Total Licenses.

    Rejected in the Last 24 Hours

    Displays the number of times the system rejected a device's request for a license during the past 24 hours. To troubleshoot individual rejections and their reasons, select Provisioning Events.

    The screen displays the number of licenses per device type:

    Field Description
    License Type

    Select a license type to manually allocate licenses for this type of device:

    • A Physical Device license is occupied by a single Windows or Mac computer (laptop, desktop, surface and so on).

    • A Mobile Device license is occupied when a mobile device runs a monitored mobile app (iOS or Android) and reports a unique device ID.

    • A Virtual Device license is occupied by a single virtual desktop (VDI), where the desktop image contains the Aternity Agent.

    • A Virtual App Session license is occupied by four frontline clients which run a virtual application from an virtual application server, where the server is running the Aternity Agent.

      Important

      A single virtual app session (frontline client) uses only a quarter of a license.

    Limit

    If you already defined a limit, it displays the maximum number of licenses allowed for allocation for this type of device.

    Currently In Use

    Displays the number of licenses currently occupied by devices of this type, and if you defined a limit, it displays its percentage out of the limit imposed for this device type.

    Rejects (Last 24 Hours)

    Displays the number of times the system rejected a device's request for a license during the past 24 hours. To troubleshoot individual rejections and their reasons, select Provisioning Events.

  3. Step 3 To limit the number of devices reporting to the system for each type of device, select Edit Limits.

    Select Limited To to enter the maximum number of reporting devices or sessions allowed for devices of this type.

    Define a limit for each type of license
    Field Description
    Total Licenses

    Displays the total number of licenses of all types which are available before any are allocated.

    Tip

    Your organization may be in the phase of gradually rolling out licenses. This is a normal part of license deployment, as more licenses are made available for allocation over time. Contact your enterprise's Aternity administrator if you need more licenses for allocation immediately.

    Gradual rollout of licenses
    Deployment License Limit

    (Aternity on-premise administrators only) Enter the maximum number of licenses you wish to deploy.

    If this value is less than the total purchased, the system displays that you are in the phase of Gradual Rollout of Licenses.

    Limited to

    Select this to set the maximum number of reporting devices or sessions for this type of license.

    Remember to multiply the licenses by four to find the maximum number of virtual app sessions.

  4. Step 4 To manually allocate a license to a username or hostname/device ID, select the type of license in the License Type column, then select Manual Allocation.
    Note

    After manually or automatically allocating a license, it remains occupied until the user/device stops reporting to Aternity for 14 consecutive days (non configurable). After that, the system automatically releases the license, making it available for another user/device.

    Manually assigning a named license
    Field Description
    Device Name (for a physical device)

    Enter a device hostname to reserve a license for a physical Windows laptop or desktop.

    Device ID (for a mobile device)

    Enter a device ID to reserve a license for a physical mobile device running a monitored mobile app.

    User Name (for virtual devices or virtual app sessions)

    Enter a username for a license to monitor a virtual application session or virtual desktop (VDI) session.

    Alternatively, to specify several devices/users at once, create a CSV file containing a single column which lists all the hostnames (or usernames for virtual sessions) which you want to allocate. Then select Bulk Allocation to upload it to the system.

  5. Step 5 To release all occupied licenses from one or more device types, select those rows, then select Release Licenses.
    Release all the occupied licenses of one type

    For example, if there are no more available licenses, and you know there are users or devices which occupy a license needlessly as part of their 14 day grace period, you can release all licenses of that device type, to allow other devices to be assigned to an available license to report their performance.

  6. Step 6 To release a specific manually allocated license, select the type of device, select the device/user to release, and select Release Licenses.

    Use the search box in the top right corner to jump to a specific username or device.

    Freeing a specific license
  7. Step 7 To troubleshoot why Aternity does not monitor a device, to determine if it was not granted a license, select Provisioning Events.

    View the recent licensing events, where each entry shows only the latest event for that user or device.

    To jump to a specific hostname, device ID or username, enter it in the search box on the top right of the screen.

    Log of provisioning events for automatic and manual allocation
    Field Description
    Last occurred at

    Displays the time and date when the last licensing-related event took place for this user or device.

    Name / ID

    Displays the username (virtual session), hostname (computer) or device ID (mobile) which requested the license.

    License Type

    Displays the type of license for this event. There are four types of licenses:

    • A Physical Device license is occupied by a single Windows or Mac computer (laptop, desktop, surface and so on).

    • A Mobile Device license is occupied when a mobile device runs a monitored mobile app (iOS or Android) and reports a unique device ID.

    • A Virtual Device license is occupied by a single virtual desktop (VDI), where the desktop image contains the Aternity Agent.

    • A Virtual App Session license is occupied by four frontline clients which run a virtual application from an virtual application server, where the server is running the Aternity Agent.

      Important

      A single virtual app session (frontline client) uses only a quarter of a license.

    Event Type

    Displays if the license was Approved or Rejected.

    Details

    Describes the reason for the rejection of a license request. For example:

    • Monitored session limit exceeded indicates that the system already assigned the maximum number of virtual sessions for that server. By default you can have up to 50 simultaneous monitored sessions on a single server.

    • No license available indicates that the system already reached its full quota of licenses.

    License Used

    Displays whether the requested license was indeed occupied as a result of this event.

    Serving Hostname

    (For virtual sessions only) In CItrix XenApp sessions, it displays the hostname of the XenApp server. For VDI sessions, it displays the hostname of the virtual desktop used in this session.