Installation guide

a. Click Properties and type a Name, Version, Description, and select the Architecture. These fields
are required. You have the option to update the other fields, depending on you requirements.
Configuring the package with Depends, Conflicts, Provides, and adding and configuring the
installation and removal files.
b. Click Files and import the installation files, add pre-command files, configure the commands and
arguments, and add post-command files.
c. Click Save to save the setting and files as a Project (*.prj).
d. Click Generate to save the project as a package (*.crate).
3. Click Package Signing and sign the package with a signing certificate.
a. Click Open to select a package (*.crate file).
b. Click Sign and select a certificate from the certificate store or from a file.
4. Click Manage Repositories and select the platforms and sections to which you are publishing the
package.
a. Click Add Platforms to add a platform.
b. Select a platform, and then click Add Sections.
c. Select a section, and then click Publish Package.
d. Select the package (.crate) and click Open.
e. (Optional) Select additional platforms and sections to which to publish the package.
f. Click Publish. The package is published to the software repository.
5. Click External Software and add externally managed software, especially any packages specified as
depends or conflicts in any of your packages.
a. Click New External Package and replace the text with the name you will use as an external
software package name.
b. Type a version number in the Version text box.
c. Select the Architecture in the drop-down menu.
d. Click Select Attribute Name and select a registry property or WMI attribute in the drop-down
menu.
e. Add attributes.
f. To save a copy locally, click Save .
g. Click Publish External SW to publish to the repository.
Run Package Studio as Administrator
The enhanced security on Windows 2008 Server requires you to run Package Studio as an administrator. If
you do not, you will not be able to publish packages to the repository.
NOTE You do not need to run Package Studio as administrator if your repositories were configured on
non-UAC protected paths or when you are running Package Studio and the repositories on machines
other than a Windows 2008 Server.
vCenter Configuration Manager Administration Guide
182
VMware, Inc.