Software inventory problems

Catalog problems can be related to incorrect discovery of the installed software.

Part numbers are not matched with products after you upload the part numbers file.

The problem might be related to the outdated application data.

In application update 9.2.20 and earlier, ensure that the you run the import of data after the upload of the part numbers file.
Ensure that the list of discovered software is up-to-date. Log in to the BigFix® console and check the date of the last scan in the Software Scan Status analysis. To update the inventory data, run the Initiate Software Scan fixlet. Set up a single scan by clearing the Reapply this action check box on Execution tab.

After applying any changes, upload the part numbers file again and run the import of data.

The <not set> value appears under the Product Name column on the Software Classification panel

The product name is not set if the component does not have any product relation defined in the software catalog. The component is detected on its own. To resolve this issue, ensure that you have the latest version of License Metric Tool installed. If not, upgrade the License Metric Tool server to the latest version. If the problem persists, contact the relevant product team and ask them to register the product. You can use custom bundling to create a new relation as a temporary workaround. For more information, see: Assigning components to products and Cloud Paks according to custom bundling relations.

Utilization of license metrics is not calculated for a product or a Cloud Pak or FlexPoint bundle

To calculate metric utilization, ensure that the following criteria are met.

Capacity data is collected from the computer on which components that belong to the product are installed. For more information, see the following links.
Relation between the discovered components and the product is charged. To check whether the relation is charged, perform the following steps.
1. Go to Reports > Software Classification.
2. Hover over Configure, and click Configure View.
3. Select Charged.
If the value in the column is No, the component does not contribute to utilization of the license metric by the product. If the product is assigned to a FlexPoint or Cloud Pak bundle, it does not contribute to utilization of the license metric by that bundle. To change the relation between the component and product to charged, reassign the component. For more information, see: Assigning components to products and Cloud Paks.

Raw utilization of a license metric is shown on the Resource Utilization report but corresponding license usage is not shown on the All Metrics report

Raw data about utilization of license metrics is collected for software that delivers .slmtag files. The data is shown on the Resource Utilization report and is usually reported for software components, not software products. Software components can be assigned to various products. For example, the component: IBM SPSS Modeler Desktop - IBM SPSS Modeler Professional can be installed as part of the following products:

IBM Maximo APM for E&U On-premise - Standard User
IBM SPSS Modeler Professional

The component contributes to license metric utilization of the product to which it is assigned. For example, if you assign the component IBM SPSS Modeler Desktop - IBM SPSS Modeler Professional to the product IBM Maximo APM for E&U On-premise - Standard User, this product and its license metric utilization are shown on the All Metrics report. The report does not show utilization for the product IBM SPSS Modeler Professional (unless a different component or a different instance of the component IBM SPSS Modeler Desktop - IBM SPSS Modeler Professional is assigned to this product).

If the software item that is reported on the Resource Utilization report is a component, check to which product it is assigned. Perform the following steps.

In the top navigation bar, hover over Reports, and click Resource Utilization. Copy the name of the software item that you want to check, and the name of the computer on which it was discovered.
In the top navigation bar, hover over Reports, and click Software Classification.
To filter the report, hover over Configure, and click Configure View. In the filters section, select the following filters. Then, click Submit.
- Component Name, contains, and provide the name of the software item that is reported on the Resource Utilization report
- Computer Name, contains, and provide the name of the computer on which the software item was discovered

If the component is assigned to a product with a different name and the assignment is in line with your license agreement, the report is correct. The software item that is shown on the Resource Utilization report should not be shown on the All Metrics report.

If the component is assigned to a product with the same name, it might be assigned to a license metric other than the one that is reported in the .slmtag file. If the license metric that is reported in the .slmtag file is in line with your license agreement, perform the following steps. Otherwise, the report is correct and the software item that is shown on the Resource Utilization report should not be shown on the All Metrics report.

Check what license metric is assigned to the product. The information is available in the Metric column on the Software Classification report.
Check what license metric is reported in the .slmtag file.
1. In the top navigation bar, hover over Reports, and click Resource Utilization.
2. To filter the report, hover over Configure, and click Configure View. In the filters section, select Software Name, contains, and provide the name of the product. Then, click Submit.
3. Check what license metric is reported in the Metric Type column.
If the license metrics do not match, and the metric that is reported in the .slmtag file is in line with your license agreement, reassign the component to a product with the right metric.
1. In the top navigation bar, hover over Reports, and click Software Classification.
2. Select the component.
3. Hover over Assign, and click Choose from Catalog.
4. From the list of available products, select the product with the metric that is reported in the .slmtag file.

If the software item that is reported on the Resource Utilization report is a product, the product might deliver the .slmtag file but not deliver the .swidtag file that is needed to discover the product. Open a case, so that the Support Team can analyze the problem and submit it to the right product team.

Backups of software directories are reported as separate products.

If you store backups of software directories on the endpoints, they might be reported as separate software instances which results in false discoveries and incorrect license consumption. To avoid this problem, either exclude the backups from scanning or compress them with a data compressor, such as ZIP or RAR.