Thanks.  I found another thread on this topic which appeared to indicate that with cloud it was not possible as t he Inventory Adapter code is updated from the "master" prior to any imports and your updates will be removed.   Additionally, if you "disconnect" the beacon in order to run the inventory, there is an additional hash check to ensure that no code in the Inventory Adapter was changed and the inventory will be discarded and not loaded. Not sure if this is still the case (am thinking yes) or as you suggested if protecting  the adapter files on the file system level would address.  Will try and test out.  I have found a few limitations with cloud versus on-prem that I am trying to figure out if I can still do another way.  Another example is inventory replication from prod to dev (ndi files) with web.config but that does not appear to be possible in cloud from what I can see. https://community.flexera.com/t5/FlexNet-Manager-Forum/Update-SCCM-readers-to-just-import-servers/td-p/96316 ... View more

The webinar mentions future enhancements to agent to detect edition and also for FNMS to handle bundles.   Is that yet in place?   Thanks Craig ... View more

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 Provided customer workaround Logged as bug and enhancement Please refer to, Bug: IOJ-2119536 Enhancement: IOJ-2119539   Workaround: Only for on-prem:   Run query, against FNMSCompliance db: SELECT [BeaconTargetPropertyID] ,[BeaconTargetID] ,[KeyName] ,[Value] ,[TenantID] FROM [FNMP].[dbo].[BeaconTargetPropertyValue_MT] ORDER BY [FNMP].[dbo].[BeaconTargetPropertyValue_MT].BeaconTargetID   Delete any records where KeyName is CTrackerExcludeDirectory (and the BeaconTargetID links to 'target__unix' in the BeaconTarget_MT table)   'UPDATE BeaconPolicy SET RevisionNumber = RevisionNumber + 1' - This will remove the exclude directory from the beacon policy, and then agent policy (for Unix devices).   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.   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. ... View more

Did you try installing agent on your  Photon Linux based VCSA 6.5/6.7 vCenters appliance to obtain an inventory for this device? We have a similar issue where the Vcenter job creates an NDI and shell record for the VCSA  appliance but is missing critical information such as serial number.  Am thinking we need to install the agent (assuming works) on this device to fill out the shell record.   Something doesn't seen quite right with the process though. Craig ... View more

@ChrisG    I see creating a bearer token is required for cloud which can be obtained by going to Accounts > All Accounts > Create an account > Service account in the web UI. Adda new account, and the token will be displayed once when the account is created.   I don't a reference to service account in the web UI, am I missing something?   Thanks Craig     ... View more