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?
Thanks
Craig
IncludeDirectory=/ ExcludeDirectory=/ENTERPRISE-LDAP/*,/UNIX-LDAP/*,/var/crash,/cores ExcludeEmbedFileContentDirectory=/ENTERPRISE-LDAP/*,/UNIX-LDAP/*,/var/crash,/cores InventorySettingsPath=/var/opt/managesoft/tracker/inventorysettings/
May 27, 2020 08:16 AM
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:
Keys "CTrackerExcludeDirectory" and "CTrackerIncludeDirectory" is what you should be looking for.
Best regards,
Markward
Jun 03, 2020 06:07 AM
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.
#CustCall
Please refer to,
Bug: IOJ-2119536
Enhancement: IOJ-2119539
Workaround:
Only for on-prem:
SELECT [BeaconTargetPropertyID]
,[BeaconTargetID]
,[KeyName]
,[Value]
,[TenantID]
FROM [FNMP].[dbo].[BeaconTargetPropertyValue_MT]
ORDER BY [FNMP].[dbo].[BeaconTargetPropertyValue_MT].BeaconTargetID
Jun 03, 2020 01:23 PM
Thanks for sharing your findings.
Jun 04, 2020 02:23 AM