
4. Resolve Uninstall Dependencies: Based on what was found on the target and what is to be deployed,
reconciliation occurs. The result of this is a list of what product modules may need to be uninstalled
and a list of product modules to install. Any product modules that require deploying are recorded in
the state matrix. A failure here will cause installation to fail.
5. Uninstall Module: All product modules that need to be uninstalled are managed here. The following is
a brief description of this process.
a. A list of product modules is obtained from the database.
b. A connection is made to the module installer.
c. The runtime agent lock is updated.
d. Each module is uninstalled in turn by the module installer.
e. If an error occurs during this process, installation fails.
6. Uninstall Module Installer
a. This job is part of the complete removal of an agent. If you are uninstalling the agent, this job tries
every means possible to completely remove the agent.
n
Via asynchronous command using the Registration Service.
n
Via command to simple installer
n
Via remote share
b. If the current request is for any other kind of install action, this is a no-op.
7. Install Simple Installer
a. Install Simple Installer lays down the installation infrastructure. It uses a service to deploy the
installation infrastructure modules. Install infrastructure modules included at this time are
ECMCommon.exe, ECMSimpleInstaller.exe, and ECMComSocketListener.exe. The following
describes the actions that are preformed during this step.
b. An attempt is made to contact the Simple Installer on the target machine. If this action is successful
then this step is complete, else the following occurs:
c. Attempt to attach to the share on the target that was specified in the UI and using the specified
authority. If this fails, then the installation fails.
d. If the attach to share succeeded, the next step is to see if the Agent has a runtime lock. This lock (not
the same as the IsLocked registry entry), is used by the installation process to prevent two or more
Collectors from installing on the same target to the same location at the same time. The lock manifests
itself as a file on the target named (ECMMachineActionLock.dat ). This lock file is located in the root
directory of the install and contains the type of action being performed (installing, uninstalling,
collecting), a time stamp, and the request id of the action doing the work. If the lock file exists on the
target, contains a valid action with a request id, and contains a time stamp that has not expired, the
target is then considered locked and the install fails. In this case the lock is partially unlocked (the time
stamp is zeroed and the request id is purged). This allows a subsequent install to continue provided it
was not relocked by another Collector. In all other cases the lock file is zeroed and the install is
allowed to continue.
e. A pre-installation check is then preformed to ensure that the subsequent install will succeed. If various
components (ComSocketServiceListener, debug event dll, or the subsystem singleton dll) are located,
they are removed.
VCM Troubleshooting Guide
38 VMware, Inc.
Komentáře k této Příručce