How to monitor software licensing compliance

On this page

Monitoring license compliance means comparing the software that inventory finds on your computers with the software licenses you own. An administrator sets up the inventory import from AlloyScan or Alloy Discovery, which also keeps the software catalog current. In the Web App, you then make sure that discovered installations are allocated to licenses and read the compliance status and usage counters of each license and each Tracked Software item. At the end, you know for every license whether it is compliant, how many entitlements are used and available, and how many more are required.

Before you begin

  • A license and a software product are related only through a Tracked Software item. Record the licenses you want to monitor and link them, with the software products they cover, to a Tracked Software item; see Link licenses and products to a Tracked Software item. The whole setup is in How to set up and allocate software licenses.
  • A new database contains no AlloyScan job: there is none until an administrator creates one.
  • For an AlloyScan import, you need the AlloyScan site's URL and the Client ID and Client Secret of an AlloyScan app registration.
  • The AlloyScan administrative permission opens Services > AlloyScan in the Settings App and Services and Integrations > AlloyScan in the Admin Center (see Permissions Reference).
  • In the Web App, the View permission of Software License and of Tracked Software allows browsing and viewing any such record, and View if Owner the records you own (see Permissions Reference).

Import inventory data

An AlloyScan synchronization job imports the devices that AlloyScan has audited as Computer and Hardware records and, as its Import software option allows, the software detected on computers. The job is an Automation Server job and runs on a schedule; a new job runs every 60 minutes. One job imports from one AlloyScan site.

Set up the job as Create or edit a job describes; that procedure is written for the Settings App. For compliance, the Import software choice matters most:

  • For all platforms: software is imported for Windows, Linux, and macOS computers.
  • For selected platforms only: software is imported for the platforms you select; the detected software of computers on the other platforms is cleared.
  • Do not import software: the detected software of imported computers is cleared.

AlloyScan imports software only for its Windows, Linux, and Mac computer types, and only from groups marked for tracking.

To run the job at once in the Admin Center:

  1. In the Admin Center, go to Services and Integrations > AlloyScan. The Synchronization tab opens first.
  2. Select one job, and click Run. Run needs an active Automation Server.

The job is queued, enabled or not, and the Admin Center shows "Your job will be started as soon as possible, typically within a few minutes. Please check the job status later." The page also has a Logs tab. In the Settings App, the AlloyScan log shows for each run the numbers of created computers, created hardware, updated computers, updated hardware, and errors; see Check the results.

If your computers are audited by Alloy Discovery, an Alloy Discovery Synchronization job imports computers, hardware, and Chromebooks from it; see Alloy Discovery Synchronization.

When AlloyScan imports a computer, the installed software arrives with the computer's audit. The computer's discovered software is brought in line with the audit: changed rows are updated, rows no longer detected are deleted, and new rows are inserted. The computer's license allocations are then recalculated. Alloy Discovery updates the discovered software of each computer it imports, except a Chromebook, and recalculates license allocations only for the computers it imports. Neither import writes discovered software for a hardware item.

Keep the software catalog current

The software catalog follows the imports:

  • An AlloyScan import adds unknown products, manufacturers, and platforms to the software catalog.
  • On every run, Alloy Discovery first copies the manufacturers, platforms, software product groups, and categories that Alloy Navigator lacks. It then adds and updates products in the software catalog but deletes none. This product comparison is skipped when nothing in the Alloy Discovery database has changed since the last catalog synchronization and no conflict is Scheduled. It adds a product whose software group in Alloy Discovery is empty or marked for synchronization, when the catalog holds no product with the same name, version, and manufacturer. Because those three values are the match, a product renamed in Alloy Discovery arrives as a second product.
  • At the end of each AlloyScan or Alloy Discovery run, every product in the software catalog that no discovered installation refers to and that is not tracked is removed from the catalog, including a product that AlloyScan or an administrator added.

To keep a product in the catalog that no installation names, link it to a Tracked Software item on the item's Products tab, inside General. Deleting a product row there removes only the link; the next run then removes the product if no discovered installation names it.

Let automatic allocation cover installations

When an Alloy Discovery or AlloyScan import loads a computer's software, Alloy Navigator allocates licenses to the computer's installations that have no allocation yet. Alloy Discovery does this for computers only, not for Chromebook audits or hardware items. Automatic allocation tries, in order: the installation's serial number and install key, the device's name against the license's device name restrictions, the device's owner, the device's organization and location, and last the license marked as the Main License of the installation's Tracked Software. These matches never pick a license whose policy tracks By User. The full rules are in Automatic allocation.

When Alloy Discovery loads a computer, automatic allocation matches only the licenses and Tracked Software items that exist at that moment. A license or a Tracked Software item created after a synchronization is allocated to the computers already imported the next time Alloy Discovery loads their software, or when you allocate it.

Reconcile installations that have no license

Reconcile allocates the devices that hold selected discovered installations to a license you pick. In the Web App, it is on the Discovered Installations tab of a computer (under Software), of a Software Product, and of a Tracked Software item.

  1. On the Discovered Installations tab, select one or more installations.
  2. Click Reconcile.
  3. In the license picker, choose a license. The devices of all selected installations are allocated to it.

The license picker is filtered using the first selected installation. On a computer, the picker is Select License, it offers only licenses of the installation's Tracked Software whose policy does not track By User, and the allocation asks for confirmation where needed.

Cover a license that runs short

When a license runs short and you add another license of the same Tracked Software, you can move some of its devices to the new license in one step, in the Web App. Allocate offers Associate Devices with another License under a policy whose tracking type is not By User.

  1. Open the license the devices are allocated to, and go to its Allocation tab.
  2. Select the allocations of the devices you want to move.
  3. Click Allocate, and then click Associate Devices with another License.
  4. In Select License, select the license to move the devices to, and then click Select.

The selected devices are allocated to the chosen license and removed from the current one. The move is not checked against the compliance terms first, and no confirmation is asked. Select License lists only the other licenses of the same Tracked Software.

Read a license's compliance

Alloy Navigator calculates a license's compliance status and usage counters in one place and stores the result for each license. Every place that shows license compliance, the Web App included, reads that same stored result, so the figures are identical wherever you see them. When Allocate or Deallocate succeeds on a license's Allocation tab, the tab, the form, and the license summary are refreshed.

The entitlement of a license is its license quantity and nothing else. The usage counters are calculated as follows:

  • Quantity: the license quantity, or 0 if the license is retired.
  • Allocated: under a policy that tracks usage by user, the allocations to people who are not Inactive; under a policy that tracks usage by device owner, the number of distinct owners of the allocated computers and hardware items, skipping retired ones; under any other policy, the allocations to computers or hardware items that are not retired.
  • Reconciled: the number of matches between an allocation to a non-retired computer or hardware item and a detected installation, on that device, of a product mapped to the license's Tracked Software. One allocation counts once for each matching installation. It is 0 under a by-user policy.
  • Unreconciled Allocations: Allocated minus Reconciled, never less than 0; 0 under a by-user policy.
  • Upgraded: the sum of Allocated over every license that upgrades this one and belongs to the same Tracked Software.
  • Used: Allocated plus Upgraded.
  • Available: Quantity minus Used, never less than 0.
  • Required: Used minus Quantity, never less than 0.

When the license is retired, or its policy's tracking type is None, every usage count is zero.

The status comes from a fixed series of checks, and the first check that applies decides the result. A license is not compliant, for example, when it has no policy, when its license count is exceeded (Required is greater than 0), when an allocated device or person does not match its restrictions, or when an allocated computer has more CPUs or CPU cores than its licenses allow. A license whose expiration date is in the past shows as not compliant, with the reason that the license expired. A license with the No License Required policy always shows as compliant. The full order is in Compliance checks.

Read a Tracked Software item's compliance

A Tracked Software item's figures add up the stored results of its licenses. The item is not compliant when at least one of its licenses is not compliant, counting expiration. When its licenses use at most one tracking type other than None, and none of them tracks usage by user, the item is also not compliant when:

  • it has no licenses, but installations of its software have been discovered; or
  • an installation of its software is on a device that has no allocation at all, and none of its licenses has a policy whose tracking type is None.

Its counters include Discovered, the non-retired installations of all products mapped to the Tracked Software, and the unreconciled installations, Discovered minus Reconciled where reconciliation applies. Its Required is the sum of the licenses' Required counters, plus Discovered minus Reconciled when reconciliation applies and Discovered is greater than Reconciled. When any of its licenses has a policy whose tracking type is None, only Discovered, the total license quantity, and the number of licenses keep their values; see Tracked software compliance.

Find non-compliant records with the Default Workflow views

A new database created with the Default Workflow (see Default Workflow Configuration) contains Web App views for following compliance across records. The views Non-Compliant Licenses, Compliant Licenses, and by Compliance are defined both for software licenses and for tracked software. Two shared Web App chart reports on tracked software, Software Licensing Compliance and Non-Compliant Software by Required, complete the set.

The supplied configuration contains no workflow rule that sends an e-mail when a license is not compliant; such a notification is something an administrator builds. An upgraded database need not contain these views and reports, and an administrator may have changed them.

Keep the figures current

A license's stored result is recalculated when something it depends on changes: among others, when a license is created or its quantity, expiration date, status, policy, or Tracked Software changes; when an allocation is added or deleted; when an Organization, Location, Device Name, or person restriction row is added, changed, or deleted; when a product is mapped to or unmapped from a Tracked Software item; when an installation is added or deleted; and when a computer's name, organization, location, status, CPU count, or core count changes. When an import adds or deletes an installation, every license allocated to that device is recalculated. The full list is in When the figure is recalculated.

No recalculation runs when a device's owner changes, or when a person's organization or location changes. The owner-based counters and checks, and the by-user location and organization checks, keep their previous values until another event recalculates the license.

Result

Inventory imports keep the discovered software and the software catalog current, automatic allocation and reconciliation link installations to licenses, every license carries a stored compliance status with usage counters that show what is used, what is available, and what is required, and every Tracked Software item adds up the stored results of its licenses.