Apr 26, 2017 - 12:42 AM
The bundles are defined at https://support.quest.com/kb/15106 and https://www.quest.com/documents/toad-..., but the license requirement is determined by the combination of deployment and license key deployed. E.g. If only base ctomponents are deployed, but using an Xpert license key then an Xpert license is required. If you want to know more reach out through LinkedIn.
May 09, 2017 - 08:11 AM
Many thanks Niall for your help.
Just going back to an earlier point on this topic, you mentioned that the auditor would be looking for need details of the installation and license keys used for each machine. I am assuming these licenses keys are stored within the registry. By any chance, would you have any information on what location in the Registry, i could find these keys? I'm hoping that i can retrieve this key data from machines using a custom script or SCCM.
Feel free to email me back at firstname.lastname@example.org
Jul 10, 2017 - 03:08 AM
Jul 24, 2017 - 02:31 AM
Would you have any general info license rules regarding license keys? (e.g. do new releases require new keys, what if user still has old key installed, etc.)
Aug 09, 2017 - 07:22 AM
yes, new releases require new keys; they are delivered by email with version and edition listed. The details held within the license keys themselves can be inaccurate, a large number just show "Toad for Oracle", but do not correctly show edition/ add-ons etc.
The recent alpa-numeric keys contain a link back to your license numbers listed on renewals; think it's the first 3 or the last 4 sections between the "-" eg if the key ends ABCD-123-456-789-23, the "123-456-789" should link back to a license purchase/ maintenance renewal.
Old keys are fine as long as the version and edition are lower that the current version, although this may require pointing out to the auditors!
Beware trial keys, many turn out to be pirate, and you are only allowed have one deployment of each product as a trial across the entire licensed org. There is also a maximum of 5 free editions. Also beware any key that does not have your company name in the "sitemessage" part of the License file. Understandably Quest are pretty agressive regarding pirate keys.