You can deploy Reflection directly from the MSI command line. You can also deploy companion .msi files that you have created to contain your custom configuration files.
Use these procedures to install Reflection from a command line with MSI.
To customize your installation, specify Windows Installer properties on the command line or pass them in a transform file. For a list of public properties that are standard to the Microsoft Windows Installer, see the Modify Setup Properties pane in the Installation Customization Tool, or refer to the Microsoft Windows Installer Guide.
If you want to create a custom (non-default) user data location that will be used by all installed Reflection products, specify the product-specific property WRQ_USERDIR. This property affects only those applications whose default user data directory is [PersonalFolder]\Micro Focus\Reflection\. Reflection applications that use this default data location include: Reflection Workspace, Reflection FTP Client, Reflection Kerberos Manager, Reflection Key Agent, Reflection IBM Printer, and Reflection X (legacy). Reflection X Advantage does not use this user data location.
If you use setup.exe for your install, the setup program checks for any prerequisites required by the features you have selected and installs them automatically.
If you use msiexec.exe for your install, prerequisites are not installed automatically. You need to install them separately if they are not already on your users' workstations. You can find installers for the required prerequisites in the Prerequisites folder in the distribution media, or in your administrative installation. The prerequisites you need to install depend on which programs and features you are installing:
All Reflection Workspace features require Microsoft .NET Framework 4.7.1. If you attempt an install using msiexec.exe and this prerequisite is not found, a message displays and the installer stops. To install the .NET Framework, run the executable file in Prerequisites\DotNet471.
The Visual Basic for Applications feature requires Microsoft VBA 7.1. Use the core and language-specific *.msi packages in the Prerequisites\VB71 folder.
If you are upgrading a previous version of Reflection, the prior version must be uninstalled before you can install the current version.
If you use setup.exe for your install, the setup program checks for a previous versions of Reflection and uninstalls it automatically if one is found.
If you use msiexec.exe for your install, you must first manually uninstall any earlier versions. If you upgrade these products by deploying the .msi file directly and have not removed the earlier version, a message displays telling you to uninstall the older software first.
To deploy Reflection “out-of-the-box” directly with MSI
At a command prompt on a test workstation, change to the directory in which the . msi file resides and enter:
msiexec /i path_to_administrative_installation_point \ yourVersion .msi
where yourVersion .msi is the specific version of the reflection MSI that you downloaded (for example, ReflectionV17.0.msi).
To deploy Reflection and a transform directly with MSI
At a command prompt, enter:
msiexec /i path_to_administrative_installation_point \ yourVersion .msi TRANSFORMS= yourCustomInstall .mst
where yourVersion .msi is the specific version of the Reflection MSI that you downloaded (for example, ReflectionV17.0.msi).
You can deploy configuration files that are “packaged” in a companion installer package separately from Reflection. This allows you to deploy and maintain these files between Reflection software updates without removing Reflection.
If you use the Host Access Management and Security Server, you can upload MSI files to the Package Manager and silently deploy them to users' workstations. See Use Central Management to Deploy MSI Packages.
To deploy a companion installer package directly with MSI
At a command prompt, enter:
msiexec /i path_to_administrative_installation_point \ your_companion_file .msi
To remove a companion installer package directly with MSI
At a command prompt, change to the directory in which the companion installer package file resides and enter:
msiexec /x your_companion_file .msi