How to configure SCCM to collect IBM tag file evidence and import them into FNMP

[#1]

Summary

This article describes how to configure SCCM to collect sys, sys2, swtag, cmptag, lax, swidtag, sig and import into FNMP/FNMS to accurately recognize several Applications

Synopsis

This article describes how to configure SCCM to collect file evidence to help accurately recognize several Applications and Components

Discussion

To collect file evidence tags (sys, sys2, swtag, cmptag, lax, swidtag, sig) using SCCM software inventory, the following configuration is required in SCCM:

1. Open the System Center Configuration Manager.
2. Click on Administration ? Client Settings.
3. In the right pane, Right click on the "Default Client Settings" ? Properties ? "Software Inventory"
4. Configure the "Inventory these file types" and collect files by adding extensions e.g *.swtag and paths e.g (C:\Program Files).
5. Click OK. This will save the configuration, and SCCM client will download these configurations for the next scheduled software inventory file scan.

Note: The above steps applies to all versions, but the below only applies to versions of FNMP/FNMS prior to FlexNet Manager Suite 2015 R2 SP3.
The default SCCM Readers file "FileEvidence.XML" on the FNMP Application Server may need modification to ensure that these file extensions get imported.
Open the following (default location) C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\SMS\FileEvidence.xml

Find either of these lines:
IN ('.exe', '.sys', 'sys2') OR IN ('.exe', '.sys', 'sys2', 'wtag', 'ptag')
and replace them with:
IN ('.exe', '.sys', 'sys2', 'wtag', 'ptag', '.sig', '2tag', '.lax', 'dtag')

Additional Information

These extensions and more are now in the out of the box Readers for SCCM on FlexNet Manager Suite 2015 R2 SP3 and above, so the modification to FileEvidence.xml is no longer required (provided that SCCM collects inventory for these extensions as well).

It should be noted that this file evidence will provide more accurate recognition of the edition for IBM applications but SCCM does not provide the information required for accurate compliance calculations on IBM PVU licenses.

To comply with IBM sub-capacity license require, it is required to either use ILMT or the FNMS Agent with IBM PVU scanning enabled.