Silent installation provides a convenient method for deploying Toad to multiple machines. With some customization, you can also deploy the license key and settings at the same time.
Note: To perform a silent install, you can use either stand-alone installer or extract the .msi from the Quest Software Installer, provided with Toad Suite.
Before performing a silent installation, review the following to determine which installer to use:
Before you can perform a silent installation, the following software must be installed on every computer where you are installing Toad:
Use the executable file to perform a silent install to the default directory (or to a different directory) and to specify options such as logging installation messages.
To perform a silent install using the executable file
For a standard installation with all features enabled, enter the following command:
“ToadInstaller.exe” /S
You can customize MSIEXEC command-line options and overrides for your installation similar to the following command:
“ToadInstaller.exe” /S /Lx “C:\temp\installLog.txt” INSTALLDIR=”Drive:\your_install_path” USERNAME=”some_user” COMPANYNAME=”your_company” ALLUSERS=1
Use the following descriptions to customize the command-line options and overrides for your installation.
Command-Line Options
The following MSIEXEC command-line options are used in this example:
Option |
Description |
---|---|
/L “C:\temp\ |
(Optional) Write installation messages to the specified log. You can append other options, such as x for debug (used in the previous example) or v for a verbose log. See the log section at http://msdn2.microsoft.com/en-us/library/aa367988.aspx for more information about additional logging options. Also, substitute “C:\temp\installLog.txt” in the example with the fully qualified name of the log file. Enclose this value in double quotations. The installation process creates this file if it does not exist. Otherwise, the existing file is overwritten. |
Toad Default Installation Option Overrides
You can specify the following values to override Toad’s default installation options. Enclose each value in double quotations.
Option |
Description |
---|---|
INSTALLDIR |
(Optional) Specify the absolute path for the directory in which you want to install Toad. If you do not include this path, the installation program defaults to: |
ALLUSERS |
(Optional) Specify one of the following:
Note: If you do not specify this property, the installation program defaults to a per-user installation. |
USERNAME |
(Optional) Specify the user that intends to use Toad on the target computer. Notes:
|
COMPANYNAME |
(Optional) Specify the name of the company that owns this installation. |
Notes:
|
The Quest Software Installer can be launched in "extraction mode," which allows you to extract the Toad for SAP Solutions MSI installer.
To launch the Quest Software Installer in extract mode
Run Toad from the command prompt and include the command-line switch "/extract".
"ToadInstaller.exe" /extract
In the Product Selection page, select the products that you want to extract.
Click Extract to extract the files.
The Finish page has a link to the directory into which the files were extracted and a link to the log file for the extraction process (Readme.txt). The extraction log contains verification of the files that have been extracted along with the command-line switches required for performing the default installation. You must run the installers in the order specified.
To perform a silent install using msi
For a standard installation with all features enabled, enter the following command:
You can customize command-line options and overrides for your installation similar to the following:
Command-Line Options
The following MSIEXEC command-line options are used in this example:
Option | Description |
---|---|
/i | Run the installation. |
/q |
Specify the user interface (UI) that displays during installation. You can append other options, such as n to hide the UI or b to hide the Cancel button during the installation. |
Note: All command-line options are case-insensitive. See http://msdn2.microsoft.com/en-us/library/aa367988.aspx for a complete list of command-line options. |
Toad Default Installation Option Overrides
You can specify the following values to override Toad’s default installation options. Enclose each value in double quotations.
Option |
Description |
---|---|
INSTALLDIR |
(Optional) Specify the absolute path for the directory in which you want to install Toad. If you do not include this path, the installation program defaults to: |
ALLUSERS |
(Optional) Specify one of the following:
Note: If you do not specify this property, the installation program defaults to a per-user installation. |
USERNAME |
(Optional) Specify the user that intends to use Toad on the target computer. Notes:
|
COMPANYNAME |
(Optional) Specify the name of the company that owns this installation. |
Notes:
|
You can create a Microsoft transform (.mst) file that deploys the license key, custom settings, and connections for users when performing a silent install using the .msi file. You can also use the .msi file to perform a basic silent install using the default directory (or install to a different directory) and to specify command-line options and default installation overrides. See Perform Silent Installation Using MSI for more information if you are not creating a transform file.
Note: (MSI installs on Windows Vista and 7) If you are using MSI to install Toad on Windows Vista or 7 with UAC enabled, you can install a file that adds a "Run as administrator" option when right-clicking the MSI file: http://www.symantec.com/connect/downloads/msi-run-administrator-context-menu-vista.
The following procedure uses the Wise Installer to create the transform file.
To create a transform file that includes custom Toad settings
Select Tools | Configuration Wizard from the Toad menu and complete the Configuration wizard. This wizard creates an initial settings file (Settings.xml).
Select each page in the window and set any options you want to deploy. These options create a module settings folder and files.
Exit Toad. Upon exiting, a Connections file is created.
File to Add |
Windows Vista, Windows Server 2008, Windows 7, Windows 8 |
---|---|
Settings.xml |
C:\Users\ username\AppData\Roaming\ Quest Software\Toad for SAP Solutions 3.2. |
ModuleSettings folder and files |
C:\Users\username\AppData\Roaming\ Quest Software\Toad for SAP Solutions 3.2\ModuleSettings. |
Connections.xml |
C:\Users\username\AppData\Roaming\ Quest Software\Toad for SAP Solutions 3.2. |
Toad must be installed on the Citrix server by the Citrix administrator. Users then connect to this instance through their Citrix login.
Note: Limited testing has been performed for Citrix XenApp™ 5.0 support on Windows Server® 2003 and for Citrix XenApp 6.5 on Windows Server 2008 R2.
To install Toad on a Citrix system
Connect to the Citrix Environment as an administrator.
Copy Toad to the Citrix server, if needed.
Start the Toad installation process.
Repeat steps 2 through 4 for each server in the Citrix farm.
Note: Although you must install Toad on every server in the Citrix farm, you only need to publish Toad once.
Review the following considerations regarding licensing:
To upgrade Toad
If you are upgrading from a previous version of Toad, you are prompted to migrate your settings the first time you start Toad. The settings files include database connections, layout customizations, shortcut keys, and options customized in the Options pages.
To migrate the settings again, remove or rename the current version's Application Data folder and migrate the files from the previous version's Application Data folder.
If you upgrade to a newer version of Toad, Automation scripts created in a previous version must be upgraded before you can open them in the newer version. Toad prompts you to automatically upgrade a script when you attempt to open it in a newer version.
In addition, scheduled scripts are scheduled to run using the version of Toad in which they were created. After upgrading Toad, those previously-created, scheduled scripts will not execute in the newer version until you migrate each script's scheduling task. Toad prompts you to migrate scheduling tasks when you initially launch the application after installation.
An automation script is compatible with the version of Toad in which the script was created. If you want to open and/or modify a script using a newer version of Toad, you must upgrade the script. Toad automatically prompts you to upgrade the script the first time you open it in the newer version.
To upgrade an Automation script
Open the script in Toad. Toad prompts you to upgrade the script.
To upgrade the script, select Yes.
If you selected Yes, Toad upgrades your script and saves a backup copy of the original script in the following location:
<application data directory>\Automation\bak\
Each scheduled Automation script uses a Windows scheduling task. The scheduling task specifies which version of Toad to use by specifying the version's application path. Toad provides you with two easy ways to migrate your scheduled scripts' scheduling tasks when you upgrade Toad. First, Toad prompts you to migrate scheduling tasks upon initial launch of the application after installation. Next, you can migrate scheduling tasks at any time using the Job Manager.
Notes:
To migrate scheduling tasks upon initial launch
To migrate scheduling tasks using the Job Manager
Select the scheduled tasks to migrate and click OK.
Note: Only currently-scheduled tasks (enabled or disabled) are listed in the Migrate Scheduled Tasks dialog.
On occasion you may need to modify the application path in a Windows scheduling task. You can do this by manually editing the scheduling task using the following procedure.
To manually edit a scheduling task
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy