Home > Matrix42 Compliance > Software Asset Management Guide > License Management > Use Cases in License Management > License Requirements > Checking Possible Entitlement for License Requirements

Checking Possible Entitlement for License Requirements

25 Oct 2017Last updated
0votes
2updates
16views

Overview

Sometimes a license requirement is not licensed despite the fact that the system contains matching licenses. In this case you can analyze the possible entitlement chart for a license requirement. The chart gives you transparency about possible entitlement of a license requirement. It groups all relevant licenses that are not used for this requirement according to the corresponding reason.

Analyzing Possible Entitlement with Licenses

To view entitlement analysis for a license requirement:

  1. Open the Licenses application and go to License Requirements > All.
  2. Click any license requirement. If the selected license requirement has matching licenses, the Possible Entitlement with Licenses chart is displayed in the preview.

The chart displays relevant licenses which are or are not used for entitlement of the license requirement by grouping them according to their status in relation to the selected license requirement (reason why the entitlement has not been performed).

If the software of the license requirement is a downgrade, the license requirement can be entitled with a license for a later version of software. In this case upgrade licenses are also included in the chart.

The chart displays the following values:

  • Invalid Licenses. Number of licenses for the relevant software and its upgrade that have the same license model and license pool as the license requirement, but with the Invalid status.
  • Expired Licenses. Number of licenses for the relevant software and its upgrade that have the same license model and license pool as the license requirement, but with the Expired status.
  • Unreleased Licenses. Number of licenses for the relevant software and its upgrade that have the same license model and license pool as the license requirement, but with the Not Released status.
  • License Pool Mismatch. Number of licenses for the relevant software and its upgrade that have the same license model as the license requirement and the Unused status, but their license pool differs from that of license requirement.
  • License Model Mismatch. Number of licenses for the relevant software and its upgrade that have the same license pool as the license requirement and the Unused status, but their license model differs from that of license requirement.
  • Restriction Mismatch. Number of licenses for the relevant software and its upgrade that have the Unused status, the same license pool and license model as the license requirement, but mismatching restrictions.
  • Used Licenses. Number of licenses for the relevant software and its upgrade that have the Used status, the same license model and license pool as the license requirement, but no available usage rights.
Note

The restriction mismatch occurs when the System Restrictions page of a license contains assets and the consumer of the license requirement is not included in this list of assets.

You can click in each chart area to drill down to the details and see the chart data.

You must to post a comment.
Last modified

Tags

Classifications

DE translation needed
Customer
Checked
icons-access-c.png