Novell ADMINSTUDIO 9.5 User Manual page 61

Two new Windows Installer properties are available when you add an MSI DLL custom action to your project to
detect virtual machines: IS_VM_DETECTED and IS_VM_TYPE. The custom action should be configured to call
the ISDetectVM function in the
In addition, the InstallScript language has been expanded to support the detection. The structure
a new
bIsVirtualMachine
InstallScript function GetSystemInfo.
New Support for Setting Permissions for Files, Folders, and Registry Keys
InstallShield offers two new ways to secure files, folders, and registry keys for end users who run your product in a
locked-down environment:
• Custom InstallShield
support for setting permissions at run time. With this option, InstallShield stores permission information for
your product in the custom ISLockPermissions table of the .msi database. InstallShield also adds custom
actions to your project to set the permissions.
•
SetObjectPermissions, an InstallScript
function in InstallScript events and InstallScript custom actions to set permissions at run time.
With the custom InstallShield handling option, the file, folder, or registry key for which you are setting permissions
must be installed as part of your installation. With the SetObjectPermissions function, the file, folder, or registry
key can be installed as part of your installation, or it can be already present on the target system.
Previously, the only option that InstallShield offered for setting permissions was to use the traditional Windows
Installer handling. With this option, the permission information is stored in the LockPermissions table of the .msi
database. The new custom InstallShield handling option and the SetObjectPermissions function offer several
advantages over the traditional Windows Installer handling:
•
The custom option and the SetObjectPermissions function include support for many well-known security
identifiers (SIDs) that are not supported by the traditional Windows Installer handling option.
•
The custom option and the SetObjectPermissions function support the use of localized user names for the
supported SIDs, unlike the traditional option. With the traditional option, if you try to use a localized name to
set permissions on a non-English system, the installation may fail.
•
The custom option and the SetObjectPermissions function let you specify that you want to deny a user or
group from having the permissions that you are specifying. The traditional handling does not allow you to do
this.
•
The custom option and the SetObjectPermissions function let 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.
With the traditional handling, the existing permissions are deleted.
•
The custom option and the SetObjectPermissions function let 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). With the traditional handling, 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.
AdminStudio 9.5 User Guide
SetAllUsers.dll
member, and a new
handling—In Windows Installer-based projects, you can choose to use custom
ADS-0950-UG00
file, which is installed with InstallShield.
constant is available for use with the
VIRTUAL_MACHINE_TYPE
Function—You can use the new SetObjectPermissions
Chapter 1: AdminStudio 9.5 Help Library
What's New in AdminStudio 9.5
SYSINFO
contains
61