09.12.2012 Views

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 17: Updating Applications<br />

Working with Upgrades and QuickPatch Projects<br />

Non-Administrator Patches<br />

Project: This information applies to QuickPatch projects.<br />

Windows Installer 3.0 and later enables you to create patches that can be installed by nonadministrators.<br />

Non-administrator patches can be used if all of the following criteria are met:<br />

• The target machine must be running Windows Installer 3.0 or later on the Microsoft Windows XP or<br />

later client platform. Server platforms are not supported.<br />

• The application was installed from a removable media such as a CD-ROM or DVD.<br />

• The application was installed in a per-machine context.<br />

Note: If the ALLUSERS property is overwritten at the command line, non-administrator patches will fail.<br />

• The base installation must include the certificate that will be used to sign all subsequent patches.<br />

• The base installation must include the MsiPatchCertificate table. This table provides the signer<br />

certificate that will be used to verify the digital signature of subsequent patches when they are<br />

applied by a non-administrator. If necessary, this table can contain multiple certificates, and<br />

subsequent patches would need to be able to verify at least one of the certificates. For more<br />

information, see Preparing Installations for Non-Administrator Patches.<br />

• The non-administrator patch must contain the MsiDigitalCertificate table. This table contains<br />

the signing certificates for the signed patches.<br />

If any of the above criteria are not met, end users cannot install the digitally signed patch in a lockeddown<br />

environment.<br />

A typical scenario in which non-administrator patches are used is the computer game industry. Some<br />

computer game users are children who might not have access to areas of the system other than folders in<br />

their own user profile and registry keys under HKEY_CURRENT_USER. Their parents would have<br />

administrative access to the machines so that they can control what is installed and what their children<br />

can access. Parents would install any and all applications. If patches are available for the installed<br />

software, children would be able to download and install non-administrator patches without help from<br />

their parents, as long as all of the above criteria have been met.<br />

Creating a QuickPatch Project and Applying QuickPatch<br />

Packages<br />

Project: This information applies to QuickPatch projects.<br />

A QuickPatch project is recommended for installation authors who want to ship small, single upgrades<br />

to their users. QuickPatch authoring provides a simple alternative to creating a patch in the Patch<br />

Design view, even though it provides less customization. Fundamentally, both patch creation methods<br />

produce the same deliverable types: .msp and .exe files.<br />

334 ISE-1800-UG01 <strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!