
11. (Optional) Select Force Reboot after command if the package requires a reboot after installation.
IMPORTANT If you select this option, the target machines will reboot after installation of the current
package without regard to time of day, state of the machine, or other factors.
12. To configure the associated removal command, repeat the above process after selecting Removal in
the drop-down list. The files, commands, arguments, and pre- and post-command options may all be
different for each of the actions.
Using Signing Certificates with Software Packages
When creating packages, you have the option to sign the package with a software signing certificate.
Signing a package ensures that package is from an authorized source and has not been altered since it was
published before it are installed on your machines.
About Signing Certificates and Installing Software Packages
Signing packages is an optional function; however, signing software packages is commonly part of the
best practice for proper network security. If you are unfamiliar with certificates, you should have a
network administrator who is familiar with certificate management assign you one with a private key.
You can publish unsigned packages to repositories, but this is not recommended.
If you are familiar with certificates, and decide to sign packages, you must be able to meet the following
prerequisites in order to sign and install packages:
n
The signing certificate must be a trusted certificate.
n
The signing certificate has a private key.
n
The user signing the packages has access to the signing certificate's private key when signing a package.
Access can be to the Certificate Store containing the certificate, an exported .pfx file of the certificate, or
an exported .pvk file of the certificate.
n
The public key of the signing certificate you used to sign a package is available on all the machines on
which you are installing packages.
Using a certificate with an expiration time will require you to generate and publish revised packages after
the certificate expires. If the certificate passes the expiration time, the packages must be individually edited
to point to a different and valid certificate, or new packages must be created.
Sign Packages with Certificates
You have the option to use a certificate to sign the packages you create. For more information about
certificates, see "About Signing Certificates and Installing Software Packages" on page 33.
Signing packages is an optional function; however, signing software packages is commonly part of the
best practice for proper network security. If you are unfamiliar with certificates, you should have a
network administrator who is familiar with certificate management assign you one with a private key.
You can publish unsigned packages to repositories, but this is not recommended.
Using Package Studio to Create Software Packages and Publish to Repositories
VMware, Inc. 33
Kommentare zu diesen Handbüchern