1 - This depends on the source of inventory for the VM. If the source is through an inventory connection, then you need to delete the VM out of that inventory source, and the during the next import it will be deleted from FNMS. Optionally, you can change the status of the Inventory Device from "Active" to "Ignored" (manually or with a Business Adapter). When an inventory device is ignored, then any software on the device is not considered during License Reconciliation.
If the source of inventory is the Flexera Agent, then you must also change the status of the Inventory Device. There is a new feature in FNMS-OP 2022 R1 where based on a date threshold, and inventory device where the source is the Flexera Agent is past that date threshold, that device is automatically deleted during the nightly compliance/reconciliation process.
2) I am not sure I understand your question. The Flexera Agent uploads to a Beacon Server.
I am looking at the uploader log under /var/opt/managesoft/log. There i can see that the the location where it is trying to connect and upload the log is incorrect. How can I correct the location without uninstalling and reinstalling the agent. I am sure there is a configuration file which i can edit and put the correct path. I need the file both for linux and windows Agent systems.
Once I have corrected the path how to manually restart the upload process. I am sure there is a command to manually initiate the process.
Manually running mgspolicy using command line options like the following will typically reset the agent according to policy settings that will be downloaded from the specified beacon. These settings include details of beacon that will be subsequently used for downloading and uploading data.
All the above operations should be run using root rights (on Unix-like operating systems), or local administrator rights (on Windows operating systems).
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
By default, an Agent will choose the highest priority Beacon of:
A Matching AD sitename
The fastest ping response
A random number - for load balancing between similar Beacons from the previous two algorithms
This may be modified in the Agent policy, there's some other alternatives outlined in the earlier linked document.
If you would prefer particular Agents communicate with particular Beacons, this is also possible through the Inventory Group Settings. In the Web UI, you can specify a target set of Agents, as with configuring a Discovery & Inventory Rule, and force those Agents to only communicate with a subset of your environment's Beacons. This is outlined in our documentation, here: https://docs.flexera.com/FlexNetManagerSuite2022R1/EN/WebHelp/index.html#tasks/InvSet-InventoryGroupSettings.html
