Hi Would like to understand the kind of issues we may come across because of this ... View more

The above stat talks about the % of evidences we have in the library BUT when it comes to coverage of Non-windows applications we do support most of the non-windows applications based on the standard installer technology and Advanced installer technologies Advanced (IA, IS/ISMP, IIM, Install stream, OUI and BEA) Standard (RPM, SDUX, SUNPKG and LPP, ASPA)  We had good coverage of non-windows applications for IBM (Most of the IBM applications we have support on non-windows platform) Oracle Adobe (We do support MAC apart form Windows, Linux, AIX, HPUX and Solaris) SAP Microsoft Veritas VMWare Cisco and other publishers I will get the stats based on the number of applications. ... View more

Hi, I'm so sorry, I though that file was part of the inventory agent archive. Thank you so much for your help. ... View more

Thanks! ... View more

Hi, I am wondering if the solution works on 7.19? Regards Ronald ... View more

Thanks Jensen! ... 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

Hi Chris, Thanks for your help!   Regards   Ronald ... View more

Thanks, this is exactly what I am talking about 🙂 I understand that sometimes an new agent is created for a specific customer issue.  That doesn't mean that other customers are not affected. In the current situation you have to wait 6 months until it is included in the original on prem release.  If it turns out you need another fix because the fix was incomplete it takes you another 6 months. By publishing all agents (including beta for customer issues) : -->Customers have earlier access to fixes for issues -->Flexera has an wider test spectrum  --> Possible issues are earlier detected -->All parties benefit from this.   Regards   Ronald  ... View more

Hi Stefan, Thanks for your response. This is also my approach, but this is not perfect. Also Flexera stated that there are no other customers know to be effected. That is why I raised this post. Can you share your Flexera case nrs by email with me? Regards Ronald ... View more

Hello Aamer, Thanks for your clarification on this topic. At this moment I am facing issues with an customer that has some Oracle False Positives.  They see installations with evidence of folders that doesn't exist and they have 2019R2 agent. My suspicion is now that there are some left over on the system with  inventory.xml and comps.xml causing these issues. My customer is going to check this. The big question I have is why does Flexera still use the inventory.xml and comps.xml files for scanning as it looks like this keeps creating false possitives?   Regards Ronald ... View more

In theory - we now support RDS. This issue may be around authentication as we typically utilize Windows\AD Authentication. I'm not sure we've done a full QA with Azure AWS. There's a bit more in this thread from Feb. https://community.flexera.com/t5/FlexNet-Manager-Forum/FNMS-installed-on-Amazon-RDS-MS-SQL-engine/m-p/132596 ... View more

Thanks Aamer!   Cheers   Ronald ... View more