Hi,   it make sense to "Allow" the following in "Licenses" List software licenses Read software license information Modify an existing software license hope this will help you. Best regards, cAPS ... View more

Here is a short summary about AgentID. The AgentID is formed from the following information: physical machines: SHA256 (HostName + BIOS_Serial_Number + History_Iteration) virtual machines: SHA256 (VMID + GenerationID + History_Iteration) (where generation ID is available only for certain hypervisors running certain versions of Windows guests) As far as we know, an insufficiently mature process in the creation of VMs (e.g. simple copying) can lead to agents on different devices generating the same AgentID. The reason for this is that the same VMIDs (UUID) and MAC addresses exist on the open devices. The consequence is that the import into the FNMS inventory table is only done from one of the devices, because the UniqueAgentIdentifier is supposed to prevent the import of multiple objects with the same value. According to the statements of the Flexera support staff, the following measures can be taken to prevent the creation of AgentID duplicates. 1./ Changing the VMID (UUID) using script or manual correction on the machine itself       (was successfully tested at my customer's site) 2./ Change of one or more MAC addresses on the machine.        This should also result in a change of the History Itheration, because here changes of the AgentID are included, which are based on changes of the MAC address. Statement of the Flexera Support: "The History_Iteration section is part of the AgentIDHistory section to keep track of AgentID changes. This is calculated with MAC address changes." I could not confirm this yet, but I will add an update here as soon as I have tested it. I had our customer make changes to the UUIDs. Now we can also see VMs in the interface that were previously not loaded into the database by the AgentID duplicates. Regards, Cap ... View more

Oh, my gosh... I think I need to go to the optician. Thanks a lot for your support Joseph. Stay healthy and have a good Day. Kind regards, Cap ... View more

Hi Josh, i have a few additional questions about the generated Agent IDs. As already described by you, the AgentIDs for VMs are composed of VMID, GenerationID and History_Itheration. The VMID is the UUID of the VM which can also be found in the NDI, right? I found the GenerationID in the vCenter and can be read out in the *.vmx file there. But I could not find the GenerationID in the *.ndi file. Now to my questions: 1./ How to get the GenerationID to create the AgentID if it is not available in *.ndi. Is it read from the registry / a WMI? 2./ What is the "History_Itheration" and where does your algorithm get this information from? Is this the information from  REG:[...]ManageSoft\AgentUniqueID\History? 3./ Is there a more detailed documentation for generating the AgentID? - which data (partly known) - are from which sources (not known) I'm asking because we have an enormous amount of duplicate AgentIDs in one environment, which means we are missing a lot of VMs in the interface. I want to show the customer exactly where the problem lies in their infrastructure. Thanks for your feedback.   ... View more