Troubleshoot falsely recognized inventory

[#1]

If an application that has been removed is falsely recognized on a device, you can begin troubleshooting by checking the date the application evidence was collected and the source that collected the evidence.

Check the inventory source and date

1. Navigate to Discovery and inventory > All inventory and search for the device.

2.  Select the device with the falsely recognized application, then select the Evidence tab.

3. On the Installer evidence tab, search for the application in the Recognized application column.

4. Note the information in the Inventory source and Inventory date columns. The following sections will help you interpret this information.

Inventory source

The Inventory source column shows the source that provided the inventory details. FlexNet Manager Suite will be listed as the source if the FlexNet inventory agent or an inventory rule sourced the application evidence. If the source is from a third-party, such as Microsoft System Center Configuration Manager (SCCM)/Systems Management Server (SMS), the application name will be listed in this column.

Inventory date

If all the inventory dates are current on the device, it suggests there is still evidence for the application. You can review the NDI file for more details if the FlexNet inventory agent is the inventory source.

If the inventory dates are outdated for all evidence from one source, it suggests that there might be an issue gathering inventory in your environment. Check the source connection to ensure it's bringing in inventory. If your source is the FlexNet inventory agent, you can check the tracker log on the device to see if the inventory agent is running and uploading correctly.

• If you select an inventory device, you can see the Last inventory date and Last inventory source in the General tab.

If you find outdated evidence and current evidence, it could suggest the following:

• If you're using the FlexNet inventory agent

You may have out-of-date inventory in the inventory database. You can check by running the following query on your inventory database:

SELECT * FROM Computer c JOIN InventoryReport ir ON c.ComputerID = ir.ComputerID. WHERE c.ComputerCN like '%nameofdevice%'

• If you see multiple entries for the same device, determine if the HWDdate value for any entry is significantly older. Any inventory associated with an older entry will stay in the system since the entry isn't being updated. This can manifest as false positives.
• Note the values in the agentID columns and determine if they are different from one another. These values should not change. The agentID is an identifier, so if the values have changed, it can lead to multiple entries for the same inventory item.

• If you're using a third-party source

A mix of outdated and current evidence dates often means out-of-date inventory is present in the source connection. For example, if your inventory source is Microsoft SCCM and it hasn't scanned the device in a month, it may have an old Last inventory date, even if the connection is running and other evidence display current dates. To correct this issue, check your third-party source application to confirm that the inventory device is up to date.