xml license files against Toad.exe files with version 10 or higher.

Match QSAuth11.key license files against Toad.exe files with version at least 6 but less than 10.The following logic was used in fabricating installer evidence: 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.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. Ask Quest (the vendor) to provide a mapping showing which Toad edition each discovered license key value corresponds to.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.I have worked with one organization who has sought to automate this with the following dance moves: 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. Can you improve the deployment process to either change the installer details or include a 'helper file' to asist in the recognition process?ĭepending on your findings, you could then look into a technical solution.Does the existence of a file indicate a specific edition, e.g.If you cannot make out editions from the data, you have a data quality issue and will need to look into alternatives. If you can make out editions in the evidence, there could just be a recognition issue and some changed/addition patterns maybe fix it. WHERE iie.DisplayName LIKE '%toad for oracle%' ON iiie.ExternalInstallerEvidenceID = iie.ExternalInstallerIDĪND iiie.ComplianceConnectionID = iie.ComplianceConnectionID ON ic.ExternalID = iiie.ExternalComputerIDĪND ic.ComplianceConnectionID = iiie.ComplianceConnectionID JOIN ImportedInstalledInstallerEvidence iiie To see the original evidence, you either need a FNMS Reporting enhancement or look into the database or NDI file. For such applications additional data needs to be collected. I would like to clarify, if the original evidence would allow for edition recognition or not.įamous example would be MS SQL Server, where the installer alone would include version details, but not editions.

Toad download free version