Introduction
For IT Visibility to import high fidelity OS information, it needs a specific set of properties that FNMS versions 2020 R2 and below do not provide. This page contains information on how to enable FNMS 2020 R2 and below to extract the specific properties from SCCM, ADDM and Flexera agent data that IT Visibility needs. From there, IT Visibility importer (available from Installers page under Discovery and Inventory) will extract it and send to IT Visibility for consumption.
Pre-requisites
FNMS 2019 R2 - FNMS 2020 R2
- FNMS 2021 R1 and later versions contain all these changes, do not take steps described in this article
- These steps are needed for export from FNMS
- Access to the FNMS Batch Server - these changes need to be done on the FNMS Batch Server
- Have knowledge on dealing with XML files
- Make a backup of all your Custom Readers and files affected
Enable OS Evidence extraction - Missing CustomInventory directory
Start here
- This set of steps is for users who do not have custom inventory readers (CustomInventory directory inside C:\ProgramData\Flexera Software\Compliance\ImportProcedures).
- Follow the steps below.
Files required
- SCCM
- Custom Inventory for SCCM.7z
- BMC Atrium Discovery and Dependency Mapping
- CustomInventory for BMC.7z
- ManageSoft
- CustomInventory for FNMP.7z
Instructions
- Download files attached to this article for the source you use
- Extract them somewhere
- After extracting and inside the extracted directory, there will be a CustomInventory folder with files inside.
- Copy them to this directory: C:\ProgramData\Flexera Software\Compliance\ImportProcedures
- WARNING:
- If this is the first CustomInventory directory, it is safe to overwrite the importer.xml file
- If there is an existing CustomInventory directory, it may not be safe to do so.
- As an alternative for the importer.xml file, you can add the xml element code block (the one inside the downloaded files) to the existing one.
- Done
- You can test them by running the compliance readers
- The directory structure inside the C:\ProgramData\Flexera Software\Compliance\ImportProcedures will loosely look like the one below
Enable OS Evidence extraction - Existing CustomInventory directory
Start here
- This set of steps is for users who do have custom inventory readers (CustomInventory directory inside C:\ProgramData\Flexera Software\Compliance\ImportProcedures).
- Users will need to manually modify and merge XML element code blocks. They will be outlined below.
- If they don't have it, they will have to follow the step above
- There are 3 compliance reader directories/sources to modify which in turn enable OS evidence extraction.
- The instructions below mainly focus on modifying XML elements
BMC Atrium Discovery and Dependency Mapping (ADDM)
Notes
- Follow these steps if you have an existing CustomInventory BMC Atrium Discovery and Dependency Mapping reader
- Modifications will need to be done in the following directories:
- C:\ProgramData\Flexera Software\Compliance\ImportProcedures\CustomInventory\Reader\BMC Atrium Discovery and Dependency Mapping
- Existing steps (element code blocks) will need to be modified and split. They need to be run on different versions of the database. The changes are outlined below:
Existing element code block modification
Order 620: Create ID fields for WMI evidence in the source database
- There is an existing step that looks like the code below:
<Reader xsi:type="ExecuteOnSource"
Name="Create ID fields for WMI evidence in the source database"
Order="620"
Retries="1">
<![CDATA[ ....
...
</Reader>
|
- Add a new attribute (VersionBefore="1.11") to the step above
- Once done, it should loosely look like the code block below
Order 640: Read WMI evidence on computers into FNMP
- There is an existing step that looks like the code below:
- Add a new attribute (VersionBefore="1.11") to the step above
- Once done, it should loosely look like the code block below
<Reader xsi:type="SourceToTarget"
Name="Read WMI evidence on computers into FNMP"
Order="640"
Retries="1"
Table="#InstalledWMIEvidence"
VersionBefore="1.11">
<![CDATA[ ...
...
</Reader>
|
New element code block introduction
Order 620: Create ID fields for WMI evidence in the source database
- Just after the element code block from the step: "Order 620: Create ID fields for WMI evidence in the source database", insert the new element code block (depicted below) after it.
Order 640: Read WMI evidence on computers into FNMP
- Just after the element code block from the step: "Order 640: Read WMI evidence on computers into FNMP", insert the new element code block (depicted below) after it.
How do I know it works?
- Run the Compliance Reader
-
Check the database and run the sql query below on the FNMP database against the compliance connection
- When installed right, it should populate values in that table with a ClassName of 'ADDM_OperatingSystem'
SMS (SCCM)
Notes
- Follow these steps if you have an existing CustomInventory SMS reader
- Modifications will need to be done in the following directories:
- Reader - C:\ProgramData\Flexera Software\Compliance\ImportProcedures\CustomInventory\Reader\SMS
- Writer - C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer
- As there are too many changes between 2019 R2 - 2020 for SMS WMIEvidence.xml, we will be replacing the entire reader file.
- We will also make minor changes to the Writer WMIEvidence.xml file
Reader - WMIEvidence.xml
- In the SMS Reader directory (C:\ProgramData\Flexera Software\Compliance\ImportProcedures\CustomInventory\Reader\SMS), you can replace the existing file with the one below. WARNING: If you have custom changes to the files, you will have to manually re-merge them after
- WMIEvidence.xml
Writer - WMIEvidence.xml
- We will be doing minor code changes to the Writer - WMIEvidence.xml file. You can find the file inside the C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer directory
- There is an existing element code block (Order 810: CalculateInstalledWMIEvidence). It will need to be replaced with the code block below.
How do I know it works?
- Run the Compliance Reader
-
Check the database and run the sql query below on the FNMP database against the compliance connection
- When installed right, it should populate values in that table with a ClassName of 'Win32_OperatingSystem'
ManageSoft
Notes
- Follow these steps if you have an existing CustomInventory ManageSoft reader
- Modifications will need to be done in the following directories:
- Reader - C:\ProgramData\Flexera Software\Compliance\ImportProcedures\CustomInventory\Reader\ManageSoft
- Only 1 Compliance Reader file needs to be changed. It is:
- ManageSoft WMIEvidence.xml
- Only 1 element code block needs to be replaced
- There is an existing element code block (Order 1120: Include additional WMI Evidence). It will need to be replaced with the code block below.
How do I know it works?
- Run the Compliance Reader
-
Check the database and run the sql query below on the FNMP database against the compliance connection
- When installed right, the above query will return data