Showing results for 
Show  only  | Search instead for 
Did you mean: 

Exclusions removed on agent after upgrade

we just completed upgrade from 2018 r1 to 2019 r2 and noticed that the files exclusions we had configured in the config.ini on several Unix servers appear to have been removed.  Note that the agents have not been upgraded yet.


An example of the config.ini entry is below and am wondering if the new feature where you can configure exclusions from UI pushed down via policy which is now removing the existing exclusions in the config.ini file on the yet to be upgraded agents.


Now that we have upgraded the application server is it now that manual updates of config.ini on specific servers is not supported and all exclusions must be configured on UI and applied globally?







(3) Replies
By Level 17 Champion
Level 17 Champion

Hi Craig,

Agreed, I can only guess that your agent folder exclusions got updated from the database (as mentioned by you). Can you check the WebUI ("Inventory & Discovery" > "Settings")? And maybe check the database tables:

  • BeaconTargetPropertyValue_MT
  • BeaconTarget_MT

Keys "CTrackerExcludeDirectory" and "CTrackerIncludeDirectory" is what you should be looking for.

Best regards,


Just had call with Flexera on this is apparently a bug.

Details below...until fix we need to adjust our steps when upgrading other customers where file exclusions are configured.


  1. Provided customer workaround
  2. Logged as bug and enhancement

Please refer to,

Bug: IOJ-2119536

Enhancement: IOJ-2119539



Only for on-prem:


  1. Run query, against FNMSCompliance db:

SELECT [BeaconTargetPropertyID]





FROM [FNMP].[dbo].[BeaconTargetPropertyValue_MT]

ORDER BY [FNMP].[dbo].[BeaconTargetPropertyValue_MT].BeaconTargetID


  1. Delete any records where KeyName is CTrackerExcludeDirectory (and the BeaconTargetID links to 'target__unix' in the BeaconTarget_MT table)


  1. 'UPDATE BeaconPolicy SET RevisionNumber = RevisionNumber + 1' - This will remove the exclude directory from the beacon policy, and then agent policy (for Unix devices).


  1. Note that the cached device configuration contents.ndc on an agent device will cause the 'original' value to be restored to config.ini on the next policy run after exclude directory is removed from the FNMS db policy properties. If this is not desired, the 'cache' and 'pkgcache' directories on the agent machine in /var/opt/managesoft/launcher should be deleted and then policy reapplied.


  1. However, please note that if the Inventory Settings page in the FNMS UI is saved again, the exclude directory property will be added to BeaconTargetPropertyValue_MT again, requiring the above workaround (1 - 4) to be applied to remove it.

Thanks for sharing your findings.