Dear All,
I have a query. We have CMDB deployed in our organization, but we would prefer to use Flexnet Agents to collect the data. However, we would also like to integrate with CMDB to ensure that if any agent doesn't respond, CMDB data is used. Thus, we would want Flexera to use data from its own agents preferably during installation. However I was not able to confirm that this is how the tool behaves. Can someone confirm that this is the behaviour of tool. Is there a way to force this via the interface.
Thanks!
Mar 11, 2020 06:42 AM
Hi @flexeranoob
by default inventory data collected by the FNMS Agent (via FNMSInventory) is set as primary connection. Other inventory sources e.g. SCCM, CMDB, ... are secondary sources and add additional information to existing inventories from the primary connection or create new inventories if it doesn't exists.
Flexera Help:
Primary Connection
The primary connection has priority for the import of hardware inventory. Any non-null value from the primary connection cannot be over-written by conflicting data from any secondary source, even if the secondary source was imported more recently. For values that are null (not reported) in the primary connection, secondary connections can provide data, with the most recent secondary import taking priority for this. (The primary connection setting has no effect on the import of software inventory.)
Overlapping Inventory
The current rule used for handling overlaps (records about the same endpoint device from multiple inventory tools) between this inventory connection and any other connection, based on whether or not data from this connection should be considered "stale" in comparison to others. This control is intended to help migrate target inventory devices from one inventory source to another (such as from an old to a newer version of your chosen tool, or to move a target device from one location to another that uses a different inventory connection). Values may be:
Back to your question, if there is no FlexNet agent data for an inventory, this information is taken from the CMDB
Best,
Dennis
Mar 11, 2020 03:58 PM
Hi @flexeranoob
by default inventory data collected by the FNMS Agent (via FNMSInventory) is set as primary connection. Other inventory sources e.g. SCCM, CMDB, ... are secondary sources and add additional information to existing inventories from the primary connection or create new inventories if it doesn't exists.
Flexera Help:
Primary Connection
The primary connection has priority for the import of hardware inventory. Any non-null value from the primary connection cannot be over-written by conflicting data from any secondary source, even if the secondary source was imported more recently. For values that are null (not reported) in the primary connection, secondary connections can provide data, with the most recent secondary import taking priority for this. (The primary connection setting has no effect on the import of software inventory.)
Overlapping Inventory
The current rule used for handling overlaps (records about the same endpoint device from multiple inventory tools) between this inventory connection and any other connection, based on whether or not data from this connection should be considered "stale" in comparison to others. This control is intended to help migrate target inventory devices from one inventory source to another (such as from an old to a newer version of your chosen tool, or to move a target device from one location to another that uses a different inventory connection). Values may be:
Back to your question, if there is no FlexNet agent data for an inventory, this information is taken from the CMDB
Best,
Dennis
Mar 11, 2020 03:58 PM
Thanks! This helps. Just a quick follow up question. Does this mean that if we obtain inventory via CMDB, and later the Flexera agent reports for the same machine, it will (by default) take priority.
This is helpful.
Mar 11, 2020 04:08 PM
Yes, you'r right.
Merging duplicate inventory from this feed — overlapping inventory from this connection is never considered stale, and for overlapping device records, participates in data merges according to the following priorities:
Mar 11, 2020 04:27 PM