Automated electronic software distribution (silent install) enables the installation of Presentation Client as a stand-alone application across a number of Windows operating system workstations, thus reducing administration time and ensuring consistent environments. Silent installation can be used in conjunction with System Management Services to automatically install Presentation Client from network servers on a large number of workstations.
Requirements
Before running the silent installation, ensure the JRE is installed on the target workstations, as it is not included with the silent installation. You can perform a silent installation of the Java Runtime Environment by performing the instructions in https://docs.oracle.com/javase/8/docs/technotes/guides/install/windows_installer_options.html.
Performing a Silent Installation
A response file is required in order to run a silent installation. The response file can either be created automatically or manually. The following procedure for performing a silent install includes the automatic creation of the response file.
Step 1: Automatically creating a response file
From the command prompt change the location to the directory containing the Setup.exe file.
Run the installation including the additional flags.
-a -r /f1<path><filename.iss>
where:
Flag | Description |
---|---|
-a | Signals that additional parameters are to be passed to the executable file. |
-r | Sets the installation in record mode. |
-f1 | Specifies the location and name of the response file to be created, where <path> is the location and <filename.iss> is the file name. If this switch is omitted, the default file setup.iss is created in the Windows directory. |
For example,
Setup.exe -a -r /f1C:\CEInstall\CEsetup.iss
Note: There is no space between /f1 and <path>.
Proceed through the installation process and select the options you want to use in the silent installation.
When the installation is complete the response file is created in the specified directory and contains information similar to the following example:
[InstallShield Silent] Version=v6.00.000 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-DlgOrder] Dlg0={2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdWelcome-0 Count=7 Dlg1={2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdLicense-0 Dlg2={2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-AskText-0 Dlg3={2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdAskDestPath-0 Dlg4={2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdSelectFolder-0 Dlg5={2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdStartCopy-0 Dlg6={2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdFinish-0 [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdWelcome-0] Result=1 [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdLicense-0] Result=1 [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-AskText-0] szText=11779900 Result=1 [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdAskDestPath-0] szDir=C:\Alinc Result=1 [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdSelectFolder-0] szFolder=Enterprise Application Component Enabler Result=1 [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdStartCopy-0] Result=1 [{2EFFFB81-3AAF-493B-B3A9-E52542AA555F}-SdFinish-0] Result=1 bOpt1=1 bOpt2=0
Step 2: Running the silent install
No messages are displayed when running a silent installation. You can create a log file in which all the installation information is recorded.
Uninstall any previously installed versions of Presentation Client.
To run the installation in silent mode you must first record your actions, and secondly you must run in the silent mode using the recorded script file.
To record:
-r /f1<path><filename.iss>
For example,
Setup.exe -r /f1"C:\setup.iss"
To run in silent mode:
Setup.exe -s /f1"C:\setup.iss"
Flag | Description |
---|---|
-s | Sets the installation into silent mode. |
f1 | Specifies the location and name of the response file, where <path> is the location and <filename.iss> is the file name. |
-r | To record the installation to the script file so the silent installation can use it. |
Step 3: Checking the log file for errors
To verify the success of the silent install, check the ResultCode value in the [ResponseResult] section of the log file. This value should be zero.
One of the following values is returned as the ReslultCode:
Value | Description |
---|---|
0 | Successful installation |
-1 | General error |
-2 | Invalid mode |
-3 | Required data not found |
-4 | Insufficient memory available |
-5 | File does not exist |
-6 | Cannot write to response file |
-7 | Cannot write to log file |
-8 | Invalid path to the InstallShield Silent response file |
-9 | Not a valid list type (string or number) |
-10 | Data type invalid |
-11 | Unknown error during setup |
-12 | Dialog boxes are out of order |
-51 | Cannot create the specified folder |
-52 | Cannot access the specified file or folder |
-53 | Invalid option selected |
Manually Creating a Response File
Rather than using the automatic process described in the preceding procedure, you can create a response file manually.
The response file has an .iss extension and is similar to an .ini file. The sections of an InstallShield response file must be in the following order:
Silent Header
All response files begin with a silent header. The silent header enables InstallShield to identify the file as a valid response file.
The silent header section must contain the following parameters and values:
[InstallShield Silent] Version=v6.00.000 File=Response File
Version indicates the version of InstallShield, it is not necessary to specify the specific release level. Use v6.00.000 in all response files. Future versions of Installshield is able to read this version of the response file.
Application Header
This is the second section in the response file. It allows developers of the installation setup to identify the setup for which the response file was created, as this is often difficult to determine by looking at the other response file data. It is not used by the setup script or the Setup.exe file.
The application header section contains the following parameters and values:
[Application} Name=<ProductKey from InstallationInfo> Version=<VersionKey from InstallationInfo> Company=<CompanyKey from InstallationInfo>
These values are derived from the values written to the registry in the call to the Installation Info function in your setup script.
Dialog Sequence
This is the third section in the response file. It lists all the dialog boxes needed during the installation, in the order in which they appear. This section is given the heading:
[<Product_GUID>-DlgOrder]
The dialog box parameters are formatted as follows:
Dlg<#>=<PRODUCT_GUID>=<DialogIdentifier>-Dlg-<#>
The dialog box numbering sequence begins at zero, meaning the first parameter entry is Dlg0. Each subsequent dialog box number increments by one.
The section is ended with the Count parameter, the value of which equals the number of dialog boxes listed. Because the dialog box sequence begins with zero, the Count value is always one greater than the highest dialog box number.
For example,
[{23EAFFCA-361D-11D3-8B0F-00105A9846E9}-DlgOrder] Dlg0={23EAFFCA-361D-11D3-8B0F-00105A9846E9}-Welcome-0 Dlg1={23EAFFCA-361D-11D3-8B0F-00105A9846E9}-AskOptions-1 Count=2
Dialog Box Data
The values entered in each dialog box are captured in the response file. Each dialog box listed in the dialog sequence section has its own section.
[<PRODUCT_GUID>-<DialogIdentifier>] Result=<value> Keyname1=<value> Keyname2=<value>
[<PRODUCT_GUID>-<DialogIdentifier>]
identifies the specific dialog box, where <DialogIdentifier> is the value entered for the dialog box in the dialog sequence section.
Data entered in a dialog box is recorded in the form Keyname=<value>. All dialog boxes return the keyname Result, which indicates the button pressed to exit the dialog box. The standard values for Result are 12 for the Back button, and 1 for Next or OK.
The keynames for the InstallShield dialog boxes are listed in the following table:
Dialog Box | Keynames | Description |
---|---|---|
SdWelcome-<#> | Result | 1 = Next |
SdLicense-<#> | Result | 1 = Yes is selected |
AskText-<#> | szText | The text from the edit field |
Result | 1 = Next | |
SdAskDestPath-<#> | szDir | The path specified in the edit field |
Result | 1 = Next | |
SdSelectFolder-<#> | szFolder | The folder specified in the edit field |
Result | 1 = Next | |
SdStartCopy-<#> | Result | 1 = Next |
SdFinish-<#> | bOpt | 1 = “Yes, I want to view the README file” is selected |
0 = “Yes, I want to view the README file” is not selected | ||
bOpt2 | bOpt2 is always 0 |