You can add the following arguments if you want to specify locations other than the default
directories:
REPOSITORY_ROOT=C:\Program Files\VMware\VCM\Tools\Repository\ (Defaults to this or uses
the Repository’s value if it is already installed)
PACKAGESTUDIO_DIR="C:\Program Files\VMware\VCM\Tools\Package Studio\" (defaults to this
path)
Manually Uninstall Package Studio
Use the following script to run an unattended uninstall the Package Manager. To uninstall the application,
you must use the version of the PackageStudio.msi that was used to install the application.
Procedure
1. Copy the PackageStudio.msi to the machine on which you are uninstalling the application. You can
also run it from a shared location.
2. Run the .msi file using the following command line syntax:
msiexec /x [path]\PackageStudio.msi /l*v %temp%\PackageStudio.log
Install Package Manager on Managed Machines
The Package Manager is automatically installed on target machines when the 5.3 VCM Agent is installed.
On the target machine, the Package Manager does not contain the software packages, only pointers to the
packages in the repository sources of which it is aware. When directed to install, the package is copied
from the repository to the cratecache folder on the target machines. It is from this location that Package
Manager upzips the files to the %TMP% directory and runs the configured installation.
When a Remove Package action is sent to Package Manager, it checks first for the package in the
cratecache. If it is not found, it then checks the repository sources for the package, and again copies it to
the target machine's cratecache folder. It is from this location that it unzips the files. The configured
uninstall files may be run form the zip directory.
Installing the VCM Agent
If you are preparing to use software provisioning on machines not previously managed in VCM, you
must first install the VCM Agent. See
"Installing the VCM Windows Agent on your Windows Machines"
on page 61
for complete instructions. By default, the VCM Agent installation installs the agent extensions
for provisioning and the Package Manager for Windows. This default action is based on the settings in
Administration | Settings | General Settings | Installer
.
Prerequisite
Target machine meets the supported hardware requirements, operating system, and software
requirements. See
VCM Hardware and Software Requirements Guide
for currently supported platforms and
requirements.
Verifying the Installation of the Agent Extensions for Provisioning
If you do not know if the machines are ready to use provisioning or not, you can verify the version of the
Agent Extensions for Provisioning. The Agent Extensions for Provisioning include the Package Manager.
vCenter Configuration Manager Installation and Getting Started Guide
184
VMware, Inc.
Summary of Contents for VCENTER CONFIGURATION MANAGER 5.3
Page 8: ...vCenter Configuration Manager Installation and Getting Started Guide 8 VMware Inc...
Page 46: ...vCenter Configuration Manager Installation and Getting Started Guide 46 VMware Inc...
Page 158: ...vCenter Configuration Manager Installation and Getting Started Guide 158 VMware Inc...
Page 178: ...vCenter Configuration Manager Installation and Getting Started Guide 178 VMware Inc...
Page 194: ...vCenter Configuration Manager Installation and Getting Started Guide 194 VMware Inc...
Page 204: ...vCenter Configuration Manager Installation and Getting Started Guide 204 VMware Inc...
Page 208: ...vCenter Configuration Manager Installation and Getting Started Guide 208 VMware Inc...
Page 234: ...vCenter Configuration Manager Installation and Getting Started Guide 234 VMware Inc...
Page 264: ...vCenter Configuration Manager Installation and Getting Started Guide 264 VMware Inc...
Page 274: ...274 VMware Inc vCenter Configuration Manager Installation and Getting Started Guide...