Installation Guide

Quality Management Installation Guide
52 June 2007
Alteration of these files or the use of other MSI files included with the product at other
locations is not supported.
Installation criteria such as supported operating systems, product deployment
configurations, installation order, and server/client version synchronization must be
met. Altering the supplied MSI packages to circumvent the installation criteria is not
supported.
Multiple Software Releases
Multiple software releases must not be combined into a single deployment package.
Each QM software release is intended for distribution in its entirety as a distinct
deployment. Combining multiple releases (for example, a software package's base
release and a subsequent service release) into a single deployment package is not
supported.
Reboots
Any reboots associated with QM installations are required. If the installation’s default
reboot behavior is suppressed, the target machine must be rebooted before running
the installed applications to ensure expected functionality.
Delaying a reboot is not known to be an issue at this time, as long as a reboot occurs
before launching the installed applications. If it is determined in the future that
delaying a reboot via command line suppression affects expected behavior, then that
delayed reboot will not be supported.
Best Practices
Best practices recommendations are listed below.
Windows Installer Logging
Window Installer logging should be enabled. The installations should be run with the
following command line argument:
/l*v <logfile path and name>
NOTE: The logfile path and name must be a location to which the
installation’s user context has permission to write.
This ensures that any loggable issues are captured efficiently.
Deployment
Each installation package should be deployed using its own deployment package.
Using separate packages offers faster isolation of potential issues than does a
composite deployment package.