You are currently reviewing an older revision of this page.
Document Type: TechNote Product(s): AutoPIPE, AutoPIPE Nozzle, PULS, PlantFLOW Version(s): V8i Original Author: Jeremy Hoesly, Bentley Technical Support Group
Document Type: TechNote
Product(s): AutoPIPE, AutoPIPE Nozzle, PULS, PlantFLOW
Version(s): V8i
Original Author: Jeremy Hoesly, Bentley Technical Support Group
Some users want to automate the program installation so that it can be performed from the command line instead of via the graphical installer. This is especially useful to system administrators when installing a program on multiple computers. Historically, the products have used InstallShield installers which can be automated using a response file. However, the products are moving to WiX installers which are easier to automate. Instructions for both installer types are provided below.
AutoPIPE 9.5 and later uses a WiX installer. To perform a silent installation, extract the contents of the package to the BentleyDownloads folder. Then run Setup.exe with a /qnui switch from a script or the Command Prompt like so:
Setup.exe /qnui
Please note that the AutoPIPE Preview Handler component still displays a graphical installer even when executing the Setup program silently. To prevent this from occurring, edit the Setup.xml file. Add a /qn switch to line 67 or 68 so that it appears like the following:
<ExecutionCommand Value="msiexec.exe /qn /norestart /i "[CurrentFolder]\System\AutoPIPE Preview Handler Setup.msi""></ExecutionCommand>
The AutoPIPE Nozzle component included with AutoPIPE 9.5.1.x also displays a graphical installer even when executing the Setup program silently. To prevent this from occurring, edit the Setup.xml file. Add a /v/quiet switch to line 82 so that it appears like the following:
<ExecutionCommand Value=""[CurrentFolder]\APNozzle\Install\Setup.exe" /v/quiet"></ExecutionCommand>
AutoPIPE (9.4 and earlier), PCF translators, STRAIT translator, ADL Pipe translator, AutoPIPE Nozzle, PULS, and PlantFLOW use InstallShield installers. These installations can be automated using a response file.
A response file contains answers to the installation dialogs presented during a graphical installation. To create a response file, first extract the installation files for the program, and quite the graphical installer. Then open an administrator command prompt, navigate to the install directory in the extracted location, and run setup.exe like so:
setup.exe /r /f1%userprofile%\Desktop\setup.iss
The graphical installer will appear. The /r switch will record the responses given during this installation. By default, the response file, setup.iss, will be saved in the Windows directory. The /f1 switch given above will save the response file on the desktop instead.
Once complete, move the setup.iss file to the install directory. To silently install the program, open an administrator command prompt, navigate to the install directory, and run setup.exe like so:
setup.exe /s
The /s switch will use the setup.iss response file when performing the installation. Please note that some installation windows may still appear momentarily, but no interaction from the user should be required.
Important: If running the silent installation command from a script, also add the /sms switch to the command above. This will pause execution of the script until the installation is finished.
1) Copy AutoPIPE installer to a local drive. Say c:\APInstaller\
2) Go to command line
3) Go to AutoPIPE Installer folder - say cd c:\APInstaller
4) Run AutoPIPE installer in recording mode, do specify a path for the answer file.
setup.exe -r -f1 "c:\APInstaller\setup.iss"
Refer to developer notes for more information on available switches!
5) Now once the installation has completed, you will have an answers file generated on the specified path
"setup.iss"
6) You can use this answer file to supply as an argument running the installer again on any other machines in silent mode.
setup.exe -s -f1 "c:\APInstaller\setup.iss"
(provided as reference for any one to duplicate/verify this problem)
Those setup.exe files generated with InstallShield inherently support the creation and use of answer files that may be used to silent install applications. Although it has no logic to handle anything not expected by the answerfile (more or less dialogs, more or less options in a dialog) it can be a helpful means of installation for some applications. The supported switches are as follows:
-d
Runs setup in debug mode. The -d switch also includes a [pathonly] option for specifying the path of the Setup.rul file. For more information, refer to the Visual Debugger help file.
-f[path\CompiledScript]
Specifies an alternate compiled script. Unless the compiled script (.ins file) also resides in the same directory as that of Setup.exe, the full path to the compiled script must be specified. _setup.dll must also reside in the same directory as your .ins file. For example, setup -ftest.ins will launch setup using Test.ins instead of Setup.ins.
-f1[path\ResponseFile]
Specifies an alternate location and name of the response file (.iss file). If this option is used when running InstallShield Silent, the response file is read from the folder/file specified by[path\ResponseFile]. If this option is used along with the -r option, the response file is written to the folder/file specified by[path\ResponseFile]. If an alternate compiled script is specified using the -f switch, the -f1 switch entry must follow the -f switch entry.
-f2[path\LogFile]
Specifies an alternate location and name of the log file created by InstallShield Silent. By default, Setup.log log file is created and stored in the same directory as that of Setup.ins. If an alternate compiled script is specified using the -f switch, the -f2 switch entry must follow the -f switch entry.
-m[filename]
Causes Setup.exe to generate a Management Information Format (.mif) file automatically at the end of the setup. Do not include a path - the .mif file is always placed in the Windows folder. [filename] is optional. If you do not specify a filename, the resulting file will be called Status.mif.
-m1[serial number]
Tells setup to place the indicated serial number in the created .mif file.
-m2[locale string]
Tells setup to place the indicated locale in the .mif file. English (ENU) is the default; refer to Microsoft documentation for a complete listing of locale strings.
-r
Causes Setup.exe automatically to generate a silent setup file (.iss file), which is a record of the setup input, in the Windows folder.
-s
Runs InstallShield Silent to execute a silent setup.
-SMS
Prevents a network connection and Setup.exe from closing before the setup is complete. This switch works with setups originating from a Windows NT server over a network. Please note that SMS must be uppercase; this is a case-sensitive switch.
-z
Prevents Setup.exe from checking the available memory during initialization. This switch is necessary when running a setup on a machine with more than 256 MB of memory; if it is not used, Setup.exe reports insufficient memory and exits.
-uninst
Runs the setup as an uninstallation without reading the script.
-verbose
Provides more detailed information when a Setup.exe error occurs.
1. Setup.exe command line parameters are not case sensitive; upper case or lower case letters can be used. 2. Separate multiple command line switches with a space, but do not put a space inside a command line switch (for example, /r /fInstall.ins is valid, but not /r/f Install.ins).
3. AutoPIPE Nozzle uses an installshield based installer. It can support silent install but for AP Nozzle you will have to record an answer file and then supply this file during instllation.
Bentley AutoPIPE
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please submit any comments you have on this Wiki article to the "Comments" area below. THANK YOU!