Install Windows App activity

The Install Windows App activity installs an application from an MSI package on a Windows target machine.

Note: This activity replaces a Powershell activity by the same name available in releases prior to Geneva. If you have a workflow created in a previous version that uses the deprecated activity, your workflow will continue to work normally after upgrading to Geneva. However, all new workflows must use the custom version of this activity. This activity was built with the Powershell activity designer, which gives workflow administrators the ability to store input and output variables in the databus.

Input variables

Table 1. Install Windows App input variables
Variable Description
hostname Hostname or IP address of the target Windows machine on which the service is installed. Use the Resolve DNS MID Server capability to resolve hostnames into IP addresses.
installerpath Path to the installer. The installer can be on any machine that is visible to both the MID Server and the target machine (local drive, UNC path, mapped drive, etc.).
installer Name of the installer file, such as winzip150.msi. The installer must be an MSI package.
arguments The parameter that contains the command line arguments to the MSI package. These are name=value pairs, separated by a space. For example, the argument might appear as: INSTALLDIR=c:\myinstallfolder ADDDESKTOPICON=0. These arguments are dependent on the what the actual MSI being installed defines. If there are no arguments, leave the field empty.

Output variables

Table 2. Install Windows App output variables
Variable Description
result Either success or failure.
errorMessage The executionResult.errorMessages from the Activity designer parsing sources.


The activity state tells the workflow engine what to do with the activity.
Table 3. Install Windows App conditions
Name Description
Success The Windows application was successfully installed on the target machine.
Failure The Windows application failed to install on the target machine