How can I perform a silent install that will push out the license key, so users do not have to enter it when Toad for Oracle is launched the first time?
The ability to push out a license key during a silent install is not something that is built directly into Toad. In order to do this you will need to create a script that runs right after the installation of Toad is done. What steps that script should take depends on the format of the license key you have. Starting in v10, the format of the Toad license key was changed from a 21-digit number to a longer alphanumeric string. Each of these key types are stored in a different area and take different steps to push them out silently. Below are the steps for each key type. If you currently have the older 21-digit number type and want to get it converted to the newer alphanumeric type, contact our licensing department at license@quest.com or fill out the form at https://support.quest.com/LicenseKey.aspx. Please supply your original key for confirmation.
Steps for older 21-digit number format...
For the 21-digit key format, the key is stored in the QSAuth11.key file. When Toad is launched, it looks to see if there is already QSAuth11.key existing. If one does, Toad will not prompt for a key and automatically carry over a copy of this to the new application data directory. If this file does not already exist, Toad will prompt the user on initial install for the license key, create the file, save the info and the user should not be prompted again.
The QSAuth11.key file can be manually created and planted so that a user is not prompted for a key on initial launch. Please try the following after Toad has been installed:
1. Manually create the QSAuth11.key file using notepad. The contents of the file should be two lines. The first line should be the license key and the second line should be the site message. It should look something like this...
1-12345-67890-12345-67890
SITE MESSAGE
Please keep in mind that this file is case and space sensitive, so do not add any extra character that you do not mean to have. A safer way of doing this, as an admin, install Toad, have it prompt you for the key and manually enter the key and site message in through the Toad gui. Once that's entered Toad will create the QSAuth11.key file for you.
The QSAuth11.key file created through the Toad gui will create and save into the file in the following directory:
C:\Documents and Settings\\Application Data\Quest Software\Toad for Oracle\
(or C:\Users\\AppData\Roaming\Quest Software\Toad for Oracle\in Windows 7)
2. Take the file and put that into the C:\Program Files\Quest Software\Toad for Oracle x.x\ClientFiles folder. When Toad is launched for the first time, the contents of the ClientFiles folder will be copied over from the Program Files directory, and create a general user files directory for each user where Toad settings will be stored from this point on.
This will include the planted copy of the .key and Toad will not prompt for the key since the file is already found.
Steps for newer alphanumeric format...
The key with the newer format stored the key in a different file. With the silent install instructions used in the newer versions of Toad a Quest.key or QuestKey.reg file is used to push out the license keys silently. Please refer to the Installation Guide of the specific version of Toad you are working with (i.e. Toad 9.7 and up). For version 12.11 the guide how to create QuestKey.reg can be found here.
If working with a Quest.key file, you may need to request this from support. You will also need the productlicense.key file. Try the follow after Toad has been installed:
1. When you extract the MSI files from the newer Toad installer, a template for the productlicense.key file will include with the other extracted files. You can manually create the productlicense.key file based off this sample and enter the key information where it shows you to.
2. Once you have this file, you will need to place the Quest.key file and a productlicense.key file on the machine Toad was installed on (any general location).
3. Execute the Quest.key file. The Quest.key and productlicense.key files must be placed in the same folder. The productlicense.key file is the file where the license key and site message is stored. When the Quest.key file is executed, it will take the productlicense.key file you paired it with, and will push the info out to the directory that Toad expect the license key. This will create and store the file and key where Toad can find it and and Toad will not prompt the user for the key since the file is already found.
Please note in Toad 11.0, a new way of pushing out the license key silently has been implemented. Please refer to the installation guide. in this case it uses the QuestKey.reg file.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center