PreviousNext
Help Library

Specifying the Required Execution Level for your Setup Launcher on Windows Vista Platforms

InstallShield 12

Project-Specific

PROJECT

This information applies to the following project types:

InstallShield lets you specify the minimum execution level required by your installation's Setup.exe file for running the installation (the setup launcher, any setup prerequisites, and the .msi file) on Windows Vista platforms. You can configure this for each individual release in your project.

Task

TASK

To specify the required execution level for a release:

  1. In the View List under Media, click Releases.
  2. In the Releases explorer, click the release that you would like to configure.
  3. Set the Required Execution Level to the appropriate setting.

The available options are:

If the Setup Launcher setting is set to Yes, InstallShield embeds a Windows Vista application manifest in the Setup.exe launcher. This manifest specifies the selected execution level. Operating systems earlier than Windows Vista ignore the required execution level.

If the Setup Launcher setting is set to No, InstallShield does not embed the Windows Vista application manifest in the Setup.exe launcher.

The benefit of elevating the required execution level is that privileges can be elevated only once if necessary to run Setup.exe, and that these privileges can be carried over to all of the installation's prerequisites and the .msi file without requiring multiple prompts for approval. Thus, if two of your prerequisites require administrative privileges, for example, you can change this setting to Administrator, and then end users are prompted only once during the installation, before Windows Installer runs the Setup.exe file. Note, however, that if you elevate the privileges and also launch the application at the end of the installation, the elevated privileges are carried over to the application. In most cases, running an application with elevated privileges on Windows Vista platforms is discouraged.

Note that an end user's installation experience is more secure when installations are run with only the permissions that they need. Unless an application is designed to be run only by system administrators, it should be run with the least privilege.

See Also




Macrovision Corporation
copyright
contact