What evidence is shown as being the raw data used for recognizing the Acrobat X installation on the Evidence tab when you view the inventory device record in the web UI? ... View more

Try taking a look at the information on the Evidence tab when viewing the inventory device record in the web UI. The information there may help to identify what specific evidence is being used to recognize the Acrobat X installation. With that information you can consider whether that evidence is represented in the NDI file, or whether it may be coming from somewhere else. ... View more

Here are some further comments to expand on @erwinlindemann's good answer: I'm not entirely confident from the way this question is phrased exactly what you are looking at. Are you looking at raw file and installer evidence records (i.e. the actual raw data that has been imported from your inventory source(s)), or are you looking at evidence recognition rules configured in the ARL settings? I suspect you're probably looking at recognition rules (since I'm not sure how you would be counting the volume of raw evidence, unless you're directly querying the database). When looking at rules, consider: Recognition rules configured in the published ARL more commonly use installer evidence than file evidence, as installer evidence is generally more useful to work with. If you are looking at file paths shown on evidence rules, these do not represent an installation path of the file on any particular device. The path shown on a rule is a common path that the file is found in, but is only one path out of all the actual paths the file is found in across all the inventory that has been imported. File paths won't necessarily be populated on file evidence recognition rules, especially if the rule does not match any actual files that have been found in your environment. ... View more

Could you post the SQL script you've used to create the relevant records here? Somebody may be able to spot something missing by looking at the script. ... View more

The NDI file attached contains a range of evidence that suggests Acrobat DC is installed. For example, here are some extracts: <Key Path="HKLM32\Software\Microsoft\Windows\CurrentVersion\Uninstall"> <Key Path="{AC76BA86-1033-FFFF-7760-0C0F074E4100}" Value=""> <Key Name="DisplayVersion" Value="21.001.20155"/> <Key Name="InstallLocation" Value="C:\Program Files (x86)\Adobe\Acrobat DC\"/> <Key Name="Publisher" Value="Adobe Systems Incorporated"/> <Key Name="DisplayName" Value="Adobe Acrobat DC"/> </Key> </Key> <Package Name="Adobe Acrobat DC" Version="21.001.20155" InstallDate="20210513T000000" Evidence="MSI"> <Property Name="InstalledProductName" Value="Adobe Acrobat DC"/> <Property Name="Publisher" Value="Adobe Systems Incorporated"/> </Package> I note the NDI file has a date of 8 June. Was the software uninstalled after this date? If so, you may find the information shown in FlexNet Manager Suite gets updated once fresh inventory is gathered and imported - check a more current NDI file to see if it continues to show details of an Acrobat installation. ... View more

The error message "The system cannot find the file specified" here suggests that the target device is unable to access the following file share on your beacon: \\FLEXBEACON\mgsRET$. A couple of possible reasons for this are: The target device is unable to resolve the name FLEXBEACON to an IP address Permissions on the \\FLEXBEACON\mgsRET$ do not allow the SYSTEM account on the target device to access the share ... View more

The "cURL" tool referred to on the Generating an Access Token from Refresh Token page is the following tool: https://curl.se/ The output you've shown here suggests you are using the Windows PowerShell "curl" alias, which is an alias for the PowerShell Invoke-WebRequest cmdlet. That is quite different from the cURL tool: it serves a similar purpose (i.e. making HTTP requests), but takes a different set of parameters. If you want to use the PowerShell curl command (aka Invoke-WebRequest) instead of the cURL tool then you would need to work out a different set of parameters. ... View more

In relation to the subnet mapping for beacons: each beacon will only operate on IP addresses that are in a subnet that the beacon is explicitly configured to work with. For example, the Discovery & Inventory > Network > Subnets page shows information like the following: In this example: 172.26.81.173/32 is not mapped to any beacon, so all beacons will skip performing operations on devices in that subnet. 10.81.151.57/32 is mapped to the cheth_beacon. Any other beacon will skip performing operations on devices in that subnet. (NB. Normally subnets will be a larger range than the /32 ranges shown in this example. The /32 ranges here are a somewhat artificial sample.)   ... View more

A "device skipped" message sounds like you may be using a zero touch (remote execution) inventory gathering approach, rather than using installed agents - is that right? The most obvious reason I can thin of that a beacon may skip doing a zero touch inventory gathering operation on a device is because the device's IP address is not in a IP address range (subnet) that is mapped to the beacon for the beacon to connect with. ... View more

If you are using FlexNet Manager Suite On Premises and have skills to write SQL queries then you could consider querying the compliance database directly to identify this data. The history events that are logged when applications are recognized as installed on inventory devices appear as records in the dbo.ComplianceHistory view with a non-NULL SoftwareTitleID and ComplianceComputerID value. Look for such records, and write a query to aggregate and find the earliest record for each SoftwareTitleID. Be aware that a query like this may be very computationally expensive to run as the database schema isn't designed to support this type of analysis. I wouldn't be surprised to see it taking hours to summarize all the historical data across all applications, and other updates to the database may be blocked while the query runs. I can't think of any effective way to do a bulk analysis & extract of this data if you using FlexNet Manager Suite Cloud/Flexera One ITAM. ... View more

@jlvalen - you may be interested in the following post which discusses how the latest version of FlexNet Manager Suite uses the db2licm command during inventory gathering: Improved recognition of IBM DB2 databases and their add-ons with ARL update #2566. ... View more

I don't know of a direct comparison of the FlexNet inventory agent specifically to BMC Discovery, but the following post may help: The big choice for gathering inventory: the FlexNet inventory agent or tool "XYZ"?   ... View more

All the documentation for the BMC Atrium and Remedy integration can be found in the Inventory Adapters and Connectors Reference. Here's a link to this reference for the 2020 R2 release: https://docs.flexera.com/FlexNetManagerSuite2020R2/EN/InvAdapConn/index.html#adapters/Atrium/topics/BAR-Introduction.html   ... View more