You will also lose fidelity going from DP to FNMS because DP normalizes away some products that are relevant to licensing but for no other purpose, by design, in order to present streamlined ITSM data. The best way to preserve fidelity in reporting across your environment is FNMS -> DP regardless of whether you are using the FlexNet Inventory Agent.  ... View more

Upgrade rights don't apply to local applications if they're missing End of Life date (can't remember now but I think only this one is required). Your solutions is to: set upgrade rights without until date (leave it blank) OR set any dates in the locally created applications ... View more

This is a very nice description. Maybe an idea if the discovery still fails. Try ping, nslookup and/or telnet  to reach some sample machines in the  targeted range. There might still be a  routing issue or firewall blocking your access. ... View more

  Hi @JensWalton , I was able to make a report that shows what I think you want:  * Contracts * Licenses * Purchases * Contracts  The way FNMS does the join, the first "Contracts" will be all contracts, but the second one will be an inner join with its predecessor item, Purchases. While it's not possible to further filter this report in the FNMS UI to the exception items where the license contract doesn't match the purchase contract, the report has the data you need and could be further refined in Excel or, if you are on prem, via a SQL report.    ... View more

Thanks a lot Natalie 🙂 ... View more

Kathy: Though there are exceptions - in general, a "Trial" version of software has the exact same installation footprint as the fully licensed version - the difference being controlled by a License Key. This makes identification difficult because: 1) You need to know where the license key is located (local file/windows registry/etc) 2) The license key may be encrypted 3) Know the translation rules to interpret the license key to know if this is a trial install or not At a higher level, a concept to keep in mind is that if you look at the actual EULA for most trial software, it will state that only 1 or 2 copies of trial software can be installed across the organization. You can understand why a publisher would not want you to install 25 instances of trial software. Therefore, even if you could determine that there are 25 installs of trial software for a product, it is likely that you would be legally obligated to license most of them anyway. Trial software should be installed in a controlled sandbox/lab environment so the installs can be known and then within the license in FlexNet Manager they can be exempted from consumption. ... View more

Thanks for your help. We are actually going to go to the company that manages our PeopleSoft implementation to get some assistance. ... View more

Quest Toad is one of those applications which require additional application-specific data to be gathered and interpreted in order to identify what edition is installed. I have worked with one organization who has sought to automate this with the following dance moves: Configure SCCM to gather Toad license key details from QSAuth11.key and ProductLicenses.xml files that different versions of Toad use, along with details of the path and version from the WinPE EXE header in corresponding Toad.exe files. Ask Quest (the vendor) to provide a mapping showing which Toad edition each discovered license key value corresponds to. This was required because Quest advised there was no other way (and the organization themselves could find no other way) to determine which edition each license key corresponded to. Configure a bespoke import process in FlexNet to combine the information from steps 1 and 2 to fabricate installer evidence details which contain edition information and can be used to recognize application installations. The following logic was used in fabricating installer evidence: Match QSAuth11.key license files against Toad.exe files with version at least 6 but less than 10. Match ProductLicenses.xml license files against Toad.exe files with version 10 or higher. Set the fabricated installer evidence DisplayName to Toad for Oracle - <Edition>, where <Edition> is: Freeware - If the Toad.exe file's full path contains the word “freeware” or “read-only” Trial - If the Toad.exe file's full path contains the word “trial” or the license file identifies the license as a trial license. Pirated copy - If the license key->edition mapping identifies the key as a pirated key. The edition from the license key->edition mapping if specified. Otherwise Unknown Set the fabricated installer evidence Version to the <Major>.<Minor> version from the Toad.exe file WinPE header information. Of course, sending a list of license keys found to be used across the organization to the vendor can raise some questions, especially as it is common for Toad software to be used with pirated license keys. See the following posting for some thoughts on engaging with vendors: Oracle LMS Services. Note that this solution was put in place some years ago (~2011), so there is every possibility that it may not be relevant for newer Toad releases. I hope this helps, but please do your own research and post here if you discover more current information. ... View more

Hi, I had a similar issue - had to make excemption on Oracle publisher within the ILMT Reader. Unfortunately I do not have another solution. Analysing several issues with ILMT connector I think the connector imports outdated data. ILMT running on SQL or DB2, which version and which product (ILMT, BigFix Inventory)? Best regards Vladi   ... View more

Hi @shelby_day ! I marked the solution because: 1) It related directly to your question by referring to the location for the material you were seeking, and 2) It called out that the related required changes to the Practice Guide aren't done yet but are in progress - so of course it won't be possible for you to review them yet. 🙂  If things prove to be completely off base, it's definitely feasible to un-mark this solution.   Best, Natalie   ... View more