Windows Installer Editor Reference
241
Advanced Installations
To add a digital signature
Select Installation Expert > Digital Signature page, mark Add a digital signature, and
complete the page:
z
Web URL
Enter your organization’s Web site address.
z
Descriptive Name
Enter the name of your application. This name is embedded in your Authenticode
certificate to let end users verify the name of the application they are installing.
z
TimeStamp URL
Specify the URL you use for your timestamping service. Timestamping lets end
users distinguish between a certificate that has expired but was valid when it was
used to sign the installation, and a certificate that was used to sign an installation
while it was expired. The timestamping service must be available on your computer
to build the installation but does not need to be available to the end user running
the installation.
z
Certificate options
Signtool.exe with Personal Information Exchange file
Mark this to use signtool.exe and then specify the Personal Information
Exchange file (.PFX) to use. This option requires a password.
You will be prompted for the password during compile.
Signcode.exe with public/private key pair files
Mark this to use signcode.exe and then specify the credentials file (.SPC or
.CER) that contains your Digital ID, and your private key file (.PVK).
z
Digital Signature for
Specify which output files should be digitally signed. If you select a type of output
file that is not selected on the Build Options page, this drop-down list is ignored.
Example: If you specify Do not create an .EXE file in .EXE Options on the Build
Options page, and in this drop-down list you select Installation .EXE only, no
digitally signed installation is created, because the installation doesn’t create an
.EXE file.
Note
The ability to add a digital signature to .MSI and external .CAB files is supported by
Windows Installer 2.0 or later only.
See also:
Setting Digital Signature Options
on page 38
Creating an Installation for Microsoft SMS
If an installation will be run in a Microsoft Systems Management Server (SMS)
environment, you can have the installation create a status .MIF file in the Windows
directory to describe the application. In order to use an installation in an SMS
environment, you must also create a package definition file (.PDF or .SMS), which
contains information about the installation. You can create the package definition file