This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
A new Flexera Community experience is coming on November 25th. Click here for more information.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Knowledge Base
- :
- Extra points for Application Usage Tracking (AUT) in FNMP
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Subscribe
- Article History
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Summary
In some circumstancse, the imported File Evidence for the usage tracking does not contain the installation match counts. It also does not necessary matched by an existing ARL rule which logically should be covered. Such File Evidence is still need link to the application manually for tracking the usage.Symptoms
/* For main workflow how to configure application usage tracking, please check KB: Q200826 */This article will describe something doesn't cover by above KB but is useful for configuration AUT. It applies from FNMP 9.2.3 to older version.
In some circumstancse, the imported File Evidence for the usage tracking does not contain the installation match counts. It also does not necessary matched by an existing ARL rule which logically should be covered. Such File Evidence is still need link to the application manually for tracking the usage.
From sql DB structure perspective, there are some file evidences entries after compliance importer is completed, Those FE exist in the ImportedInstalledFileEvidenceUsage, but not in the ImportedInstalledFileEvidence. Such File Evidence will be found FNMP UI with 0 match counts as Unassigned (unmatched). In ARL logic the matching on file evidence is by matching Primary Key (Name,Version,Company, Description & FileSize) , however such usage file evidence will not be run through ARL matching mechanism. In another word even we have a ARL rule can cover the raw entry, the current product will create a raw entry with 0 match counts into FNMP still.
The following sql query can be used to find such file evidence (only in ImportedInstalledFileEvidenceUsage not ImportedInstalledFileEvidence)
/* checking the format of File Evidence)
SELECT * FROM ImportedFileEvidence
WHERE ExternalFileID IN
(
SELECT ExternalFileID
FROM ImportedInstalledFileEvidenceUsage
WHERE ExternalFileID NOT IN
(
SELECT ExternalFileID FROM ImportedInstalledFileEvidence
)
)
SELECT *
FROM ImportedInstalledFileEvidenceUsage
WHERE ExternalFileID NOT IN
(
SELECT ExternalFileID FROM ImportedInstalledFileEvidence
)
Resolution
1. Pick the 'new' unassigned File Evidence2. Link to the corresponding SoftwareTitle
3. Make sure this SoftwareTitle Recognition is already happened via other ARL (through Installer Evidence, File Evidence, WMI, Suite etc)
4. Setting the Usage Period correctly
5. Create a license and link this application to the license
6. Another full Inventory Import (Not Reconcile only)
See attached file as a demonstration.
May 19, 2018 01:00 PM
100% helpful
(1/1)
Comments
- Mark as Read
- Mark as New
- Permalink
- Report Inappropriate Content
@Kevin_Hou wrote:
SummaryIn some circumstancse, the imported File Evidence for the usage tracking does not contain the installation match counts. It also does not necessary matched by an existing ARL rule which logically should be covered. Such File Evidence is still need link to the application manually for tracking the usage.
Symptoms/* For main workflow how to configure application usage tracking, please check KB: Q200826 */
This article will describe something doesn't cover by above KB but is useful for configuration AUT. It applies from FNMP 9.2.3 to older version.
In some circumstancse, the imported File Evidence for the usage tracking does not contain the installation match counts. It also does not necessary matched by an existing ARL rule which logically should be covered. Such File Evidence is still need link to the application manually for tracking the usage.
From sql DB structure perspective, there are some file evidences entries after compliance importer is completed, Those FE exist in the ImportedInstalledFileEvidenceUsage, but not in the ImportedInstalledFileEvidence. Such File Evidence will be found FNMP UI with 0 match counts as Unassigned (unmatched). In ARL logic the matching on file evidence is by matching Primary Key (Name,Version,Company, Description & FileSize) , however such usage file evidence will not be run through ARL matching mechanism. In another word even we have a ARL rule can cover the raw entry, the current product will create a raw entry with 0 match counts into FNMP still.
The following sql query can be used to find such file evidence (only in ImportedInstalledFileEvidenceUsage not ImportedInstalledFileEvidence)
/* checking the format of File Evidence)SELECT * FROM ImportedFileEvidenceWHERE ExternalFileID IN(SELECT ExternalFileID usps trackingFROM ImportedInstalledFileEvidenceUsageWHERE ExternalFileID NOT IN(SELECT ExternalFileID FROM ImportedInstalledFileEvidence))/* checking the usage information eg: LastUsedDate */SELECT *FROM ImportedInstalledFileEvidenceUsageWHERE ExternalFileID NOT IN(SELECT ExternalFileID FROM ImportedInstalledFileEvidence)
Resolution1. Pick the 'new' unassigned File Evidence
2. Link to the corresponding SoftwareTitle
3. Make sure this SoftwareTitle Recognition is already happened via other ARL (through Installer Evidence, File Evidence, WMI, Suite etc)
4. Setting the Usage Period correctly
5. Create a license and link this application to the license
6. Another full Inventory Import (Not Reconcile only)
See attached file as a demonstration.
@Kevin_Hou your steps help me in Tracking...
Apr 05, 2021
09:20 AM
