User Guide

379
Package Validation
! Components shared with non-Windows installer applications
Checks that no components of the package are shared with other applications that
do not use Windows Installer.
! Files installed to Program Files by default
Checks that all application files are installed to a subdirectory of Program Files.
! Terminal Server Compatibility
(Enterprise edition only.) Checks for errors that might cause problems when the
package is installed in a Microsoft Terminal Services or Citrix environment. With
terminal service applications, installation resources must reside in per-machine
locations rather than per-user locations. Errors result from this test if the installation
is set to install per-user, if any keypaths reside in user-specific locations, or if
environment variables are present in the installation. If environment variables are
present, using the Correct button duplicates the variables, creating a per-user set
and a per-machine set, one of which is installed depending on the value of
ALLUSERS. Correcting some errors might cause keypaths to be empty, and might
cause a one-time repair. You can set a release to be compatible with Terminal
Services. See the description of the Release Type field in Creating a New Release
on page 180. Also see ALLUSERS Property in the Windows Installer SDK Help.
Also see:
Validating a Package
Customizing Validation Modules