InstallShield 2012 Spring Express Edition User Guide

Chapter 7: Specifying Installation Information
Configuring General Project Settings
Table 7-1: Comparison of Different Ways to Secure Objects (Files, Folders, and Registry Keys) in a Locked-Down
Environment (cont.)
Comparison Category Explanation of Available Support
Effect on permissions
that already exist
Ability to propagate
permissions to child
objects (subfolders,
files, and subkeys)
Ability to set
permissions for a new
user that is being
created during the
installation
• Traditional Windows Installer handling—Existing permissions may be deleted. For
example, if permissions are already set for a folder on the target system for the
Everyone user, and your installation needs to set permissions for the Administrators
user, this option would allow you to set permissions for the Administrators user.
However, the existing permissions for Everyone would be deleted.
• Custom InstallShield handling—This option lets you add permissions to a file,
folder, or registry key that already exists on the target system, without deleting any
existing permissions for that object. For example, if permissions are already set for a
folder on the target system for the Everyone user, and your installation needs to set
permissions for the Administrators user, these options would allow you to set
permissions for the Administrators user without deleting the existing permissions for
the Everyone user.
• Traditional Windows Installer handling—Not supported. If you want to configure
permissions for a subfolder or a file in a folder (or a subkey under a registry key), the
parent that is created on the target system automatically inherits the permissions of its
child.
• Custom InstallShield handling—Supported. This option lets you configure
permissions for a folder (or a registry key), and indicate whether you want the
permissions to be applied to all of the folder’s subfolders and files (or the registry key’s
subkeys).
• Traditional Windows Installer handling—Not supported.
• Custom InstallShield handling—Supported. If a new user is created during the
installation, you can configure permissions for that user.
Neither option lets you set permissions for objects that are not being installed as part of your
installation.
Learning More about the Custom InstallShield Handling Option or the Traditional
Windows Installer Handling Option
In Express projects, you need to specify whether you want to use the custom InstallShield handling or
the Windows Installer handling. To learn how, see Selecting the Locked-Down Permissions Type for a
Project.
To learn how to set permissions for a file or folder using either of these options, see Configuring
Permissions for Files and Folders. For information on setting permissions for a registry key using either
of these options, see Configuring Permissions for Registry Keys.
Selecting the Locked-Down Permissions Type for a Project
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.
142 ISE-1900-UG00 InstallShield 2012 Spring Express Edition User Guide