Installation Guide

Using Automated Package Distribution Tools
June 2007 51
Using Automated Package Distribution Tools
QM’s MSI-based desktop application installations can be deployed (“pushed”) via
automated package distribution tools that make use of the Microsoft Windows
Installer service.
Requirements
QM support for automated package distribution depends on compliance with the
requirements listed below.
Execution
Installations must be executed on the target machine. Deployment methods that
capture a snapshot of an installation and redistribute that image are not supported.
Per-Machine vs. Per-User Installation
Installations must be deployed on a per-machine basis. Per-user installations are not
supported.
It might be necessary to ensure per-machine installation via command line.
Privileges
QM installations require either administrative or elevated privileges.
By default, Windows Installer installations run in the context of the logged-on user.
If the installation is run in the context of an administrative account, there is no need to
enable policies to grant elevated privileges.
If the installation is run in the context of an account with reduced privileges, then it
must be deployed with elevated privileges. The target machine must have the
Windows policy “Always Install with Elevated Privileges” enabled for both the User
Configuration and the Computer Configuration. When this policy is enabled, Windows
Installer installations will run in a context with elevated privileges, thus allowing the
installation to successfully complete complex tasks that require a privilege level
beyond that of the logged-on user.
Automated Package Installation vs. Manual Installation
Automated installations must use the same files and meet the same installation
criteria as manually-deployed installations.
QM MSI packages are located in the following location on a successfully-installed
production server and are intended for both manual and automated deployment.
<user-defined path>\QM\Tomcat\webapps\TUP\QM