Windows Installer Editor Reference
180
Your Installation on the Destination Computer
See also:
Setting Version-Specific Windows Installer Options
on page 176
Guidelines for Custom Action Location
on page 454
About UAC Elevation of an Entire Installation
¾
Windows Installer 4.0 or later only.
To avoid elevation-related failures, you can elevate an entire installation. At run time, a
UAC prompt appears only when the installation first begins. The remainder of the
installation runs in an elevated mode.
Use this method of elevation when an installation’s User Interface sequence contains the
following types of custom actions:
z
Actions that access a restricted area to check launch conditions or obtain data to
populate installation dialog boxes.
z
Actions that perform an IIS check. These actions usually appear in a Web or server
installation.
z
Actions that access user information or other restricted information. These actions
usually appear in a server installation.
The option to elevate the entire MSI is on the Windows Installer Options page, under the
UAC Compatibility Settings section.
See
Setting Version-Specific Windows Installer Options
on page 176.
When you elevate an entire MSI, the custom action WiseElevateCheck is added to the
User Interface sequence. Do not remove this custom action from the installation.
Note
When you create a Web installation or a server installation, Wise IIS-related custom
actions are added to the Execute Immediate sequence. These actions are coded to run
in an elevated mode. Any other custom actions in the Execute Immediate sequence that
access restricted areas are not elevated. Move them to the Execute Deferred sequence.
The elevated MSI runs as follows:
z
A single UAC prompt appears when the MSI begins. No other prompts appear.
z
During the User Interface sequence, the WiseElevateCheck action determines
whether the installation is running with elevated privileges and elevates it if
necessary.
z
If the installation is set to create an installation log, two logs might be created. One
log contains little information. The other log appears to contain entries for two
Create a standard user
installation with no elevation
If an application is written to be installed and run by standard users without
elevation, you can bypass UAC elevation issues. The installation cannot contain
actions that access a protected area on the destination computer. If the
installation tries to access a protected area, it fails.
See
Creating an Installation for Standard Users
on page 71.
Option
Description