VMware PACKAGE MANAGER 1.1, Инструкция по установке и эксплуатации

Страница: 44 / 66

n
Depends: Package Manager will install a second copy of an application when it is specified as a
dependency.
n
Conflicts: Package Manager will install a package even though an externally installed application exists
on the machine that is specified as conflicting with the package being installed.
To avoid these undesirable results, you should add all externally managed software to the External
Software list, paying particular attention to packages specified as depends or conflicts in your packages,
and continue to publish updated versions to the repository to ensure Package Manager has the most
current list to reference when processing dependencies and conflicts during installation.
Adding Applications to an External Software List
Consider adding existing applications to your External Software list under the following circumstances:
n
You begin using software provisioning to install packages on machines already in use. Adding
previously installed applications to the External Software list and then publishing it to the repository
provides the mechanism by which Package Manager can verify the existence of the application on the
target machine. It makes applications not installed as packages visible to Package Manager, reducing
the need to re-install applications installed outside Package Manager.
n
You add dependencies to applications installed outside Package Manager. Even on a machine on which
only the basic operating system is installed, you will have certain applications that are already installed,
for example, Internet Explorer. Identify the applications, add them to the External Software list, and
publish the list to the repository used by the machines.
Managing External Software Lists
You can publish only one version of the list to a repository. After creating an initial list, add to the existing
list rather than publishing a new list. If you publish a new list to a repository, it overwrites the existing list.
Naming External Software Packages
When creating the name for the external software package (<New External Package>), apply the same
naming considerations you used when naming packages. By using the same naming conventions, you
ensure that Package Manager can process the defined external software "packages" as if they were actual
packages, even though they contain only attributes to check rather than installation files.
See "About Package Naming and Versioning" on page 21 for more information.
Defining Attributes
The list of attributes displayed in the Attribute Name drop-down list is based on values in the uninstall
registry keys, located in HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall (on 32-bit machines) or HKEY_
LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall (on
64-bit) and on properties defined in Windows Management Instrumentation (WMI) for installed software.
When creating attributes, make certain that the value entered in the Value text box correctly matches the
expected value for the application on the target machines.
How Package Manager Processes External Software during Installation
When instructed to install a package, Package Manager processes the request in the order described
below.
vCenter Configuration Manager Software Provisioning Components Installation and User's Guide
44 VMware, Inc.