Installing UEC via the Command Line
Introduction
This page describes how to install Universal Enterprise Controller (UEC) using the Windows Installer command line interface.
A command line installation is useful in situations where:
- Several Universal Enterprise Controller installations must be deployed.
- It is not practical or convenient to perform the graphical interface installation.
- It is necessary to generate an installation log file.
Installing UEC
Step 1 | Download the Universal Enterprise Controller for Windows product distribution file, sb-UECtlr-6.3.0.<level>-windows-i386.exe, to your work station. |
---|---|
Step 2 | Execute the distribution file from the command line, and include all appropriate command line switches and parameters. |
Command Line Syntax
The following illustrates the command line syntax used to install UEC:
sb-UECtlr-6.3.0.<level>-windows-i386.exe [/v"command line parameters"] [/s] [/w] [/x]
In this syntax:
<level>
is the numeric package level.
The command line switches (/v, /s, /w, and /x) are processed directly by the distribution file to control behavior of the Windows Setup application.
The command line parameters are passed to the Windows Installer (msiexec) to control the extracted Windows installer package file (.msi) behavior during the install process.
Command Line Switches
The following table describes the command line switches available for a command line installation:
/v | Passes parameters to the Windows Installer (msiexec). |
---|---|
/s | Suppresses the initialization and extraction dialogs displayed before the product install Welcome dialog." |
/w | Instructs the Windows Setup application to wait until the installation completes. |
/x | Uninstalls UEC. |
Command Line Parameters
The following table describes the parameters that are available for a command line installation.
The parameters can be specified in any order, with the following exceptions:
- If the Repair (#/fom) or Remove (#/x) parameter is used, it must be specified before all other parameters.
- If the Silent install (#/q) and/or Log file (#/L) parameters are used, they can be specified in any order, but they must be specified after all other parameters.
These parameters are preceded by the #/v command line switch and must be enclosed in double (") quotation marks.
Parameter | Description | Default |
---|---|---|
/fom | Repairs a Universal Enterprise Controller installation. | n/a |
/x | Removes Universal Enterprise Controller. | n/a |
INSTALLDIR=installdir | Sets the root installation directory to < | (none) |
UECTLR={yes|no} | Specification for whether or not to install the UEC Service component during new installs, upgrades, or maintenance.
Since, by default, each component's install state is preserved during an upgrade or maintenance, UEC Service is not required unless you want to change the current install state. UEC Service is ignored during an uninstall. | yes |
/q | Suppresses the product installation dialogs. | n/a |
/L*v | Instructs the installation process to create an installation log file named < | n/a |
Command Line Installation Examples
The following examples illustrate different ways that UEC can be installed from the command line.
Graphical User Interface Install, All Components
To install all UEC components via the graphical user interface, issue the following command:
Graphical User Interface Install, All Components, with Log File
To install all UEC components using the Windows Installer graphical user interface and write a log file to C:\temp\install.log
during the installation, issue the following command:
Silent Install, Different Installation Directory
To install UEC under D:\Universal, which is a directory other than the one specified by the environment variable PROGRAMFILES, issue the following command:
Silent Install, All Components
To install all UEC components without using a graphical interface — that is, a silent install — issue the following command:
Detecting the Completion of Silent Installs
If the #/q switch is used to perform a silent install, no graphical interface or user interaction is required. One drawback to this is that no feedback is provided indicating when the Windows Installer process (install, uninstall, or repair) finishes.
One method that may be used to detect when the Windows Installer process ends is to execute it using the system's start command. Using available command line switches, the start command can be used to initiate the Windows Installer process and then wait for it to finish. When the start command returns control to its calling process (for example, the command prompt), the process will have ended.
For example, from the command prompt, issue the following command to start the Universal Enterprise Controller installation and wait for it to finish.
- The /b switch prevents the start command from opening a new window.
- The /wait parameter causes the start command to start the application, sb-UECtlr-6.3.0.0-windows-i386.exe, and then wait for it to finish.
The syntax above can also be used to execute the start command from within a script, such as a .bat file.
For more information on the start command, go to the Windows command prompt and enter: start /?.