Selecting the Locked-Down Permissions Type for a Project

InstallShield 2019

Project • This information applies to the following project types:

Basic MSI
DIM
InstallScript MSI
Merge Module
MSI Database
MSM Database
Transform

InstallShield includes a project-wide setting that lets you specify how your installation should configure permissions for files, folders, and registry keys for end users in a locked-down environment.

Selecting the locked-down permission type for a project:

1. In the View List under Installation Information, click General Information.
2. In the Locked-Down Permissions setting, select the appropriate option:
Custom InstallShield handlingInstallShield adds a custom table and custom actions to your project to set permissions on the target system. This is the default value.
Traditional Windows Installer handlingInstallShield uses the LockPermissions table in the .msi database to store permissions information for your product.

For a detailed comparison of these two options, see Securing Files, Folders, Registry Keys, and Windows Services in a Locked-Down Environment.

The next time that you configure permissions for a file, folder, or registry key in your project, InstallShield uses the locked-down permission type that you selected:

If you selected the traditional Windows Installer handling option, InstallShield uses the LockPermissions table in your project.
If you selected the custom InstallShield handling option, InstallShield uses the ISLockPermissions table in your project; InstallShield also adds the ISLockPermissionsCost and ISLockPermissionsInstall custom actions to your project.

If you change the value of the Locked-Down Permissions setting but your project already contains permission settings for files, folders, or registry keys, InstallShield displays a message box that lets you specify whether you want to migrate the permission data to the appropriate table. If you choose to migrate the data, InstallShield moves the data to the table that corresponds with the option that you selected; if you are switching from the custom InstallShield handling option to the traditional Windows Installer handling option, InstallShield also deletes the ISLockPermissionsCost and ISLockPermissionsInstall custom actions from your project.

See Also