Retired Licenses with Active Payment Schedules Report

IT Asset Management (Cloud)

The Retired Licenses with Active Payment Schedules report lists licenses that are marked as retired, but which still have active payment schedules. Generate this report on a regular basis to optimize your license position by identifying licenses which your enterprise may be paying for unnecessarily. Operators with a focus on purchasing or licensing may choose to run this report to identify where money is being wasted, or to identify licenses which have been inappropriately retired. These operators may choose to run the report monthly or any other regular time period which aligns with payment schedules.

Generating the report

1. Go to the Retired Licenses with Active Payment Schedules page.
2. Click Run report to display the results for all enterprise groups.

Limiting the report results

In the top left corner is a search field titled Enterprise. Click the search icon and choose the enterprise(s) to include in this report. For help with the search, see To Use a Fly-Down.

Reading the report

The following columns (listed alphabetically) are available in this list. By default, some are available through the column chooser.

Compliance status

Whether or not the current use of software under this license complies with the license terms and conditions. Values may be:

• At risk — Consumption exceeds entitlements. Consider uninstalling some software, or finding more purchase records, or making new purchases to cover the shortfall.
• Compliant — The calculated consumption is less than or equal to the total recorded entitlements (these may be recorded in one or many purchases linked to this license). If your data input is complete and accurate, this license is in good shape.
• Not tracked — This is the initial (default) value for CAL Legacy, Oracle Legacy, and Concurrent User licenses, because the compliance status of these license types is not calculated by license reconciliation process. However, you can manually set the compliance status value in the Compliance tab of the properties for these licenses. Custom Metric licenses also start out as Not tracked, but for Custom Metric licenses you may manually set the value only if you first set the Set Compliance status manually check box in the Identification tab of the license properties.
• Unknown — Inventory data cannot be used to determine the compliance status of this license. Typical reasons may include:
  • Missing calculations — You haven't yet run a compliance calculation (called a Reconcile, available in the Reconcile page, or run automatically overnight).
  • Missing applications — The license has no application linked. You can identify the installed software and link it to the license; or as a short-term workaround, you can switch to the Consumption tab, allocate the license to specific computers (or end-users, depending on license type), provided that in the Use rights & rules tab you expand the License consumption rules section and select the Allocations consume license entitlements check box.
  • Missing inventory details — This license may require details from hardware inventory that are currently not available. For example, Microsoft Server Core and Microsoft Server Processor licenses require the number of threads and cores or processors from hardware inventory. All inventory tools do not include these details. Prior to the 2012 release, Microsoft Endpoint Configuration Manager (previously Microsoft SCCM) did not provide information on cores; and threads may be missing from various sources, and the license compliance cannot be accurately calculated without this information. Unless the license is already at risk, it is given a status of Unknown. To correct this, identify the computers linked to this license that are missing the necessary hardware properties, and set the values manually until you can change to an inventory tool that provides all required data. Consider augmenting the inventory on these computers with direct inventory gathering by IT Asset Management through an inventory beacon.

Contract name

The name (or brief description) of the contract.

Editable in the Description field in the General tab of the contract properties.

Contract number

The identifying code for the contract.

Editable in the Contract no. field in the General tab of the contract properties.

Corporate unit

The corporate unit responsible for this license.

Editable in the Ownership tab of the license properties.

Cost center

The cost center responsible for this license.

Editable in the Ownership tab of the license properties.

Location

The location within your enterprise that is responsible for this license.

Editable in the Ownership tab of the license properties.

Name

The license name may be:

• Copied from the first-linked software product
• Derived from the License Name field of the SKU in the first-linked purchase (or if there is no SKU, from the purchase Description field)
• Created manually.

The Name value is editable in the Identification tab of the license properties.

Next installment

The date planned for payment of this installment.

Set up when the payment schedule is created, and then not editable.

Next installment amount (currency)

The budget projection for this scheduled payment.

Set when creating the payment schedule, and then editable in the Installments tab of the payment schedule properties.

Payment schedule

The name given to this payment schedule at creation (or at last edit). Click to open the properties page for this payment schedule.

Set in the Create a Payment Schedule page. Editable in the General tab of the payment schedule properties.

Payment schedule end date

The last day of operation for this payment schedule.

Set when the payment schedule is created, and then not editable.

Tip: The End date is adjusted automatically if you later delete the last installment on the payment schedule, or if you add a new installment to the payment schedule.

Payment schedule start date

The beginning of the first period for this payment schedule.

Set when the payment schedule is created, and then not editable.

Payment schedule type

The kind of payments being scheduled, as determined when the payment schedule was created.

Not editable. If you need to change the type of a payment schedule, create a new one of the new type, check that any payments recorded against the old one are copied onto the new one, and then delete the old one.

Publisher

The name of the publisher of this software, responsible for its development and distribution.

Editable in the Identification tab of license properties.

Type

The kind of license, which determines what properties are available for the license, and how compliance is calculated for the license. For details of an individual license type, please see the appropriate entry in the glossary.

Editable in the License type field in the Identification tab of the license properties.