Preinstallation instructions for Citrix or Remote Desktop Services
All Toad user files are stored in a user_name directory. When a user opens Toad for the first time, Toad copies the contents of this folder to the user’s associated Application Data folder in the Toad installation folder.
Note: Write access is required to the Oracle directory if any of the users want to edit the tnsnames.ora file by using the TNSNames Editor within Toad.
To install Toad on a Citrix/Remote Desktop Services system
- Connect to the system as an administrator.
- Copy the Toad installer to the Citrix/Remote Desktop Services server, if required.
- Install Toad according to the instructions provided in this guide.
- Right-click the Toad.exe file in the root installation folder, and then select Properties. Make sure the Allow non-administrators to run this program option is selected under Compatibility | User Account Privileges.
-
Repeat these steps for each server in the Citrix/Remote Desktop Services farm.
Note: Although you must install Toad on every server in the farm, you only need to publish Toad once.
Install Toad silently from the command line
A silent installation enables you to install Toad and other Edition products without user interaction, making it ideal for automated deployments across your organization. You can specify command-line parameters to configure the installation, such as choosing a custom installation directory.
Note: Legacy offline licenses, such as those that use a license key and site message, can also be applied silently. See Install licenses.
Note: Toad is installed per machine and will be available to all users on that machine.
Toad for Oracle Edition Installer
Installation supports silent mode by using the /install and /qn command-line parameters. See Toad for Oracle Edition Installer options for the complete command-line reference.
See Obtaining the installer for instructions on acquiring the Toad for Oracle Edition Installer.
Toad for Oracle Product Installer
Installation supports silent mode by using the /i and /qn msiexec command-line parameters when launching the Toad product installer. See Toad for Oracle Product Installer options for the complete command-line reference.
See Install licenses for instructions to silently deploy legacy offline licenses.
See Obtaining the installer for instructions on acquiring the product installer.
Install licenses
This topic applies to Toad for Oracle with legacy offline license keys. Toad for Oracle Subscription licenses are retrieved automatically by Toad when you sign in within Toad.
To install legacy offline licenses on the target computers
- Create a Questkey.reg text file to specify each license key.
- Send the file to the target PC and import it to the Registry there.
To create the Questkey.reg file
Create the Questkey.reg file in a text editor. The following is a template:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\{08439167-4CA5-48E9-A810-A3A7C0B80B06}]
[HKEY_CURRENT_USER\Software\{08439167-4CA5-48E9-A810-A3A7C0B80B06}\Local]
[HKEY_CURRENT_USER\Software\{08439167-4CA5-48E9-A810-A3A7C0B80B06}\Local\REPLACE_WITH_KEY]
"SiteMessage"="REPLACE_WITH_SITEMESSAGE"
"ProductName"="REPLACE_WITH_PRODUCTNAME"
"ProductVersion"="REPLACE_WITH_PRODUCTVERSION"
Follow these steps to configure the file:
- Do not change the first two HKEY_CURRENT_USER lines. They are the key entries.
-
Replace the "REPLACE_WITH_(KEY | SITEMESSAGE | PRODUCTNAME | PRODUCTVERSION)" text with the relevant information supplied with your license.
-
Add any additional licenses as required in the same file by replicating the last four lines and then applying the correct information.
- Save the file.
To apply the file on the target computer
- Transfer the Questkey.reg file to the target PC.
-
Import the file to the Registry on the target PC with the following command in the Windows command prompt:
C:\> reg import Questkey.reg
When Toad or any other Edition product is launched, the software validates the license and removes the corresponding entries from the Windows Registry.
Install Toad as Read-only
A read-only installation of Toad prevents users from making any changes to the database, regardless of their Oracle privileges. A read-only installation applies to all users on that machine for this version of Toad.
See Obtaining the installer for instructions on acquiring the product installer.
Note: Toad is installed per machine and will be available to all users on that machine.
Configuring Toad for Oracle as read-only
Choose one of the following methods:
-
Supplying the READONLY=1 command-line parameter during installation, for example: msiexec.exe /i "ToadforOracle_2025R3_x64_En.msi" READONLY=1
See Toad for Oracle Product Installer options for the complete command-line reference.
-
Install Toad as usual and add a "Read-Only" DWORD entry with a value of 1 to the following Registry location: HKEY_LOCAL_MACHINE\Software\Quest Software\Toad for Oracle\2025 R3.
Note: This can be added either before or after installation.
Command-line options
Command-line options can be supplied to customize the installation, for example choosing a custom installation directory, restricting the users ability to save database passwords, or disabling Toad's check for updates feature.
You can install the software using either the Toad for Oracle Edition Installer or the Toad for Oracle product installer. Refer to the following tables for the command-line options available for each installer.
Toad for Oracle Edition Installer options
You can use the following command-line parameters during installation:
|
/? |
|
Displays the command-line reference including detailed examples. |
|
/qn |
|
Quiet mode, no user interface. |
|
/L |
Logfile |
Writes logging information into a logfile at the specified path.
Example: /L "C:\path_to_log_file" |
|
/install |
|
Installs one or more products. |
|
/extract |
|
Extracts one or more product installers (.msi files). |
|
/uninstall |
|
Uninstalls one or more products. |
|
/p |
Products |
Specifies a comma-separated list of product codes to which the action should be applied.
Optionally used with the /install, /extract, and /uninstall options.
- 101 - Toad for Oracle
- 520 - SQL Optimizer for Oracle
- 525 - Benchmark Factory
- 530 - Code Tester for Oracle
- 535 - Spotlight on Oracle
- 540 - Toad Data Modeler
Example: /p:101,520 |
|
/installdir |
Directory |
Specifies the installation directory.
Example: /installdir:"C:\target_directory" |
|
/autoupdatedisabled |
|
Installs Quest Auto Update as disabled. |
Examples:
-
Display command-line reference:
ToadforOracle_2025R3_x64_En.exe /?
-
Install Toad silently to the default directory:
ToadforOracle_2025R3_x64_En.exe /install /p:101 /qn
-
Install Toad and SQL Optimizer silently to a custom directory:
ToadforOracle_2025R3_x64_En.exe /install /p:101,520 /installdir:"C:\target_directory" /qn
-
Install Toad silently to the default directory with Quest Auto Update disabled:
ToadforOracle_2025R3_x64_En.exe /install /p:101 /autoupdatedisabled /qn
Toad for Oracle Product Installer options
The Toad installer is executed using msiexec, for example: msiexec.exe /i "ToadforOracle_2025R3_x64_En.msi".
All standard msiexec command-line parameters are supported when installing Toad. Additional Toad-specific options can be provided as PROPERTY=value pairs where the property name is in upper case.
For a comprehensive list of Windows Installer command-line options, including parameters not covered in this document, see the official Windows documentation: https://learn.microsoft.com/en-us/windows/win32/msi/command-line-options.
You can use the following command-line properties during installation:
|
TARGETDIR |
Installation directory |
Installs Toad to a custom installation directory.
Example: TARGETDIR="C:\target_directory" |
|
READONLY |
1 |
Installs Toad as read-only, preventing users from making any changes to the database, regardless of their Oracle privileges.
Example: READONLY=1 |
|
RESTRICTIONS |
p|i|ai |
Installs Toad with restrictions. Multiple restrictions can be supplied as a comma-separated list.
Example: RESTRICTIONS=ai
Example: RESTRICTIONS=p,i
-
p - Restricts saving of database passwords
-
i - Restricts internet access
Note: This restriction does not prevent requests that are essential for core functionality or those initiated by the user, such as FTP connections.
- ai - Restricts access to artificial intelligence features
|
|
AUTOUPDATE_DISABLED |
1 |
Quest Auto Update is installed in a disabled state, so product updates will not be downloaded or communicated to the user.
Example: AUTOUPDATE_DISABLED=1
To enable Quest Auto Update:
- Configure the Quest Update Service Windows Service so that its startup type is set to Automatic (Delayed Start)
- Start the Quest Update Service Windows Service.
- Add the C:\Program Files\Quest Software\DBT\Autoupdate\QuestUpdate.NotificationUI.exe executable to the list of Windows Startup Apps.
- Run QuestUpdate.NotificationUI.exe. It runs as a background process.
|
Examples:
-
Install Toad silently to the default directory:
msiexec.exe /i "ToadforOracle_2025R3_x64_En.msi" /qn
-
Install Toad silently to a custom directory:
msiexec.exe /i "ToadforOracle_2025R3_x64_En.msi" TARGETDIR="C:\target_directory" /qn
-
Install Toad silently to the default directory with logging:
msiexec.exe /i "ToadforOracle_2025R3_x64_En.msi" /qn /l*v "C:\path_to_log_file"
-
Install Toad silently to the default directory with Quest Auto Update disabled:
msiexec.exe /i "ToadforOracle_2025R3_x64_En.msi" /qn AUTOUPDATE_DISABLED=1
Note: To perform a silent installation of other products that are provided with your Edition, see the installation guide for that product at https://support.quest.com/technical-documentation.
