@Techbpn8771  I think I understand what you're trying to accomplish here, and I would also agree that it would be plausible to do something like this for testing purposes. However, I wouldn't consider an approach like this to be following "good practice" when it comes to production without properly documenting the reasons why a given user (or device installation) can be adjusted to not consume (1->0). Flexera's ITAM solution is designed to facilitate use cases like this but at the same time ensure proper documentation by allowing for allocations and exemptions, which in my opinion can (and should) be used to facilitate the use case(s) here, (as I understand it): I.e. as described earlier the permanent allocation can enforce consumption and exemptions can be used to document why consumptions shouldn't be counted in compliance calculations. I would welcome other views from other forum members on this topic as there may be other opinions/views and also better/other options to facilitate your use case(s). Thanks, ... View more

I tried that change, but to no avail... still getting the error in system tasks when I run the adapter.  I will likely open a support ticket and reference this post there... will update with results when it is fixed. ... View more

That is correct, only certain supported file types are imported to the compliance database and shown in the UI. The paths that are scanned are based on your file evidence settings: https://docs.flexera.com/flexera/EN/ITAssets/InvSet-FileInvSection.htm In regards to Linux there are further settings for network drives and file systems. https://docs.flexera.com/fnms/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/topics/PMD-IncludeNetworkDrives.html https://docs.flexera.com/fnms/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/topics/PMD-IncludeFileSystemType.html ... View more