VMware PACKAGE MANAGER 1.1 User manual

vCenter Configuration Manager
Software Provisioning Components
Installation and User's Guide
Package Studio 1.1
Software Repository for Windows 1.1
Package Manager 1.1
This document supports the version of each product listed and supports all
subsequent versions until the document is replaced by a new edition. To
check for more recent editions of this document, see
http://www.vmware.com/support/pubs.
EN-000455-00

Copyright You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
[e-mail]
© 2006-2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and
intellectual property laws. VMware products are covered by one or more patents listed at
http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All
other marks and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
vCenter Configuration Manager Software Provisioning Components Installation and User's Guide
2 VMware, Inc.

Contents
About This Book 5
Introduction to VCM Software Provisioning 7
VMware vCenter Configuration Manager Package Studio 7
Software Repository for Windows 7
Package Manager for Windows 7
Overview of Component Relationships 8
Installing the Software Provisioning Components 9
Software Provisioning Requirements 9
Software Provisioning Component Software Requirements 9
Software Provisioning on Guests 10
Install Software Repository for Windows 10
Software Repository Structure 11
Manually Uninstall the Repository 11
Manually Configure Repositories 11
Configure Mirrored Repositories 14
Install Package Studio 17
Manually Uninstall Package Studio 19
Installing Package Manager for Windows 19
Manually Uninstall the Package Manager for Windows 20
Using Package Studio to Create Software Packages and Publish to Repositories 21
About Package Naming and Versioning 21
Correct Naming Practices 21
Correct Versioning Practices 22
How Package Names and Versions Are Processed by Package Manager 23
Creating Packages 23
Create Packages with Dependencies 25
Create Packages as Dependency Containers 26
Specify Package Conflicts 27
Specify Provides for Packages 29
Add Commands, Arguments, and Scripts to Packages 30
Using Signing Certificates with Software Packages 32
About Signing Certificates and Installing Software Packages 32
Sign Packages with Certificates 32
Editing Packages 34
Edit Published Packages 34
Create New Package from Existing Projects or Packages 36
Using Software Repository for Windows 39
About Repository Platforms and Sections 39
Platforms 39
Sections 40
Sample Platforms and Sections 40
Add Platforms and Sections to Repositories 40
Publish Packages to Repositories 41
Using External Software 43
VMware, Inc. 3

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide
About External Software 43
Best Practices 43
Adding Applications to an External Software List 44
Managing External Software Lists 44
Naming External Software Packages 44
Defining Attributes 44
How Package Manager Processes External Software during Installation 44
Define External Software Attributes 46
Using Package Manager for Windows 49
Processing Dependencies 49
Security 49
Add Repository Sources 49
Remove Repository Sources 50
Install Packages 50
Remove Packages 51
Package Manager for WindowsCommand Line Options 51
Requirements and Considerations 52
Wasp Command Line Options 52
Maintain Package Manager for Windows Data 62
Package Manager Maintenance 62
Repository Source Maintenance 62
4 VMware, Inc.

About This Book
About This Book This manual, vCenter Configuration Manager Software Provisioning Components Installation and User's Guide,
describes how to install the components, use the components to create software packages, publish
packages to repositories, and install software on target machines.
Intended Audience
To use the information in this guide effectively, you must have a basic understanding of how to configure
network resources, install software, and administer operating systems. You also need to fully understand
your network’s topology and resource naming conventions.
Document Feedback
VMware welcomes your suggestions for improving our documentation. If you have comments, send
your feedback to [e-mail].
Technical Support and Education Resources
The following technical support resources are available to you. To access the current version of this book
and other books, go to http://www.vmware.com/support/pubs.
Online and Telephone
Support
To use online support to submit technical support requests, view your product
and contract information, and register your products, go to
http://www.vmware.com/support.
Customers with appropriate support contracts should use telephone support for
priority 1 issues. Go to http://www.vmware.com/support/phone_support.html.
Support Offerings To find out how VMware support offerings can help meet your business needs,
go to http://www.vmware.com/support/services.
VMware Professional
Services
VMware Education Services courses offer extensive hands-on labs, case study
examples, and course materials designed to be used as on-the-job reference tools.
Courses are available onsite, in the classroom, and live online. For onsite pilot
programs and implementation best practices, VMware Consulting Services
provides offerings to help you assess, plan, build, and manage your virtual
environment. To access information about education classes, certification
programs, and consulting services, go to http://www.vmware.com/services.
VMware, Inc. 5

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide
6 VMware, Inc.

Introduction to VCM Software Provisioning 1
Introduction to VCM Software Provisioning The VCM Software Provisioning components consist of VMware vCenter Configuration Manager
Package Studio, software package repositories, and Package Manager.
VMware vCenter Configuration Manager Package Studio
Package Studio is the application used to build software packages for installation on target Windows
servers and workstations.
A software package provides the files and metadata necessary to install and remove programs. One of the
most useful features of a package is the metadata regarding dependencies, conflicts, and other
relationships that are not represented by software installation files. This metadata is used to determine if
the necessary dependencies are in place so that an installation is successful, and if not, what is necessary to
make the installation successful. This use of metadata is similar to rpm on Linux.
Packages support commercial and custom software that may be installed using any installation
technology, including .msi, .exe, or scripts (Python, VBScript, PowerShell, and others).
Once a package is created and ready for distribution, it is published to a software repository. You use
Package Manager to download the package from the repository to the local machine and install it on your
Windows systems.
Software Repository for Windows
Software Repository for Windows is the shared location to which packages are published by Package
Studio and the location from which Package Manager downloads packages for installation.
Package Manager for Windows
Package Manager is the application installed on each machine to manage the installation and removal of
the software contained in packages. Package Manager is configured to use one or more repositories as
sources for packages.
If you are using the software provisioning components in conjunction with VMware vCenter
Configuration Manager (VCM), you can use VCM to add and remove sources, and to install and remove
packages.
VMware, Inc. 7

Overview of Component Relationships
The following diagram displays the general relationship between Package Studio, repositories, and
Package Manager in a working environment.
vCenter Configuration Manager Software Provisioning Components Installation and User's Guide
8 VMware, Inc.

Installing the Software Provisioning Com-
ponents 2
Installing the Software Provisioning
Components
The software provisioning components should be installed on machines with the following relationships:
nSoftware Repository for Windows: Installed on at least one Windows machine in your environment,
and installed on the same machine with Package Studio. Install the repository before installing Package
Studio.
nVMware vCenter Configuration Manager Package Studio: Installed on the same machine as your
software repository.
nPackage Manager: Installed on all Windows machines on which you are managing software
provisioning.
To uninstall the above applications using a script at a later date, you should save a copy of each of the .msi
files in an archive location. To uninstall using the .msi, you must have the same version used to install the
application.
Software Provisioning Requirements
VCM Software Provisioning provides the components to create software provisioning packages, publish
the packages to repositories, and then install and remove software packages on target machines.
The following operating systems are supported platforms:
Supported Operating System Supported Hardware Platform
Microsoft Windows 7 x86, x64
Microsoft Windows Server 2008 R2 x64
Microsoft Windows Server 2008 SP2 x86, x64
Windows Vista SP2 x86, x64
Microsoft Windows XP SP3 x86
Microsoft Windows XP SP2 x64
Microsoft Windows Server 2003 R2 SP2 x86, x64
Microsoft Windows Server 2003 SP2 x86, x64
Table 2-1 Software Provisioning Operating System and Hardware Requirements
Software Provisioning Component Software Requirements
The following are the VCM Software Provisioning components and their software requirements:
VMware, Inc. 9

nVMware vCenter Configuration Manager Package Studio: The application used to the create the
software packages. Requires .NET 3.5.1.
nSoftware Repositories: The file system used to store the shared software packages. Requires .NET 3.5.1
and IIS 6, 7, or 7.5.
nPackage Manager: The application on each managed machine that downloads packages from
repositories, and then installs and removes the software contained in the packages. Requires .NET 3.5.1.
Software Provisioning on Guests
Any virtual machine guest on VMware ESX 3.5 and vSphere 4 (both i and non-i versions) meeting the
above requirements can be used for any of the VCM Software Provisioning components.
Install Software Repository for Windows
The Software Repository for Windows and the VMware vCenter Configuration Manager Package Studio
should be installed on the same machine. The process installs the Repository folders and subfolders, and
configures the virtual directory. The virtual directory is used by Package Manager to access the repository.
Prerequisites
Target machine meets the supported hardware requirements, operating system, and software
requirements. See "Software Provisioning Requirements" on page 9 for currently supported platforms and
requirements.
Access to the Repository.msi, which is available on the VMware website or in the vCenter Configuration
Manager application files.The default location in the VCMapplication files is C:\Program
Files\VMware\VCM\AgentFiles\Products.
Procedure
1. Double-click Repository.msi.
The Welcome page appears.
2. Click Next.
The License Agreement page appears.
3. Review the agreement, and then select I accept the terms of the License Agreement to continue. The
other options become available.
4. Select I am an authorized agent and/or representative of the customer/end-user and I have read the
terms and conditions stated above.
5. Click Next.
The Installation Folder page appears.
6. Use the default path or click Change to modify the path. When the path is correct, click Next.
The Virtual Directory page appears.
7. Use the default name or type a new name in the text box.
8. Click Next.
vCenter Configuration Manager Software Provisioning Components Installation and User's Guide
10 VMware, Inc.