License Optimizer


This is an old version of the Getting Started help. The latest version has been moved into the main License Optimizer help.


We've had a look at the hardware records that we imported, so now let's look at the software records that we imported. After that, we'll do some software teaching – matching unrecognized phrases in the software titles that you imported to a specific product in the Definitive Software Library.

The Software page

The Software page lists all of the software instances in your IT estate.

To view the Software page:

1.On the navigation bar, under Estate Management, click Software.
The Software page appears. Initially, it is empty because you never want to see a complete list of all your software titles, as this would be so large that it would be unmanageably slow and too large to work with. The first step is to filter this list to a more manageable size.

2.We want to focus our initial investigations on Microsoft, so we are going to use the filter bar towards the top of the page to select just software from Microsoft. Click Vendors/Products.

The Select Vendors, Products and Editions dialog appears.

3.From the tree, select the check box alongside Microsoft.

4.Click Apply Now.
The list updates to show only software from Microsoft. Note that the filter you have applied persists until your login session ends or you change it. As with other data grids, you can sort and filter the list to help you to understand your data more easily.

There are two tabs, one for software that is associated with an OSI, and one for software that isn't. Software records listed in the Unassigned to OSIs tab are still used in reconciliation. You can use the Unassigned to OSI functionality to capture summary software liability that you don't want to create manually or can't import (for example, if you can't get data from beyond a firewall).

There is a lot of data here for you to explore. much of it is self-explanatory, but there are two columns worth noting.


It is time to start thinking about some of the features of licenses. Some license agreements allow you to use a different product or version from that named on the license: licenses can be associated with a suiteClosed(a collection of software products that have their own executables and which are covered by a single license) or a bundleClosed(a collection of software products covered by a single license that has an executable for the primary product as well as for the supporting products), so that several executables are covered by a single license; or they might allow downgradingClosed(the allowed use of a license for an earlier version of a product)  or (more rarely) upgradingClosed(the allowed use of a license for a later version of a product), so that different versions are covered by a single license.

Click a Yes link in the Overlapped column to see a list of all the software overlapped by a product. In the example below, the Office 2010 installed on the OSI AC-TWIST-TT is covered by a downgrade from an Office 2013 license:

Policy State

You can create policies that distinguish between software that is on an approved list, a mandatory list, or an unapproved list. The Policy State column identifies if software is in one of these lists. For more information, see the link provided below.

What next?

Only software that has been matched to items in the DSL can be reconciled, so we now need to teach the system to recognize any unmatched software records: Software teaching.

More information

Software – further information on the License Optimizer help

Policy management – further information about creating software policies on the License Optimizer help

Was this article useful?