VMware VCM 5.3 Instrukcja Naprawy Pobierz pdf (Strona 37)

1. Detect Previous Install (Detects previous Agents and Agent components): Detect previous install

determines if a previous Agent version is installed on the target machine. When installing 4.11.x or

later, if a previous Agent version is detected, it must be removed. The Detect Previous Install process

determines if a previous Agent is present by attempting to connect to the agent installation DCOM

components (Basic and Agent Installers). If a connection is made to either of these components, Detect

Previous Install sets a state member that the following three steps use to determine if they should

execute. This step and the three that follow it remove the previous Agents and are included in all types

of install and uninstall requests.

2. Validate Installation Environment

a. The validate installation environment job is the first real job that gets executed. This job ensures

that the target is available for installation. If the validate job is able to contact the Module Installer,

it calls methods on that component to get all the install manifests on the target. It also checks the

registry for various conditions that should prevent the install. This job fails if the following

conditions are satisfied:

The agent is locked: The following shows the registry entry that is evaluated by this job to

determine if the agent is locked. HKEY_LOCAL_

MACHINE\SOFTWARE\Configuresoft\ECM\4.0\Agent\IsLocked. If this key exists and has a

value other than 0 then the agent is locked.

NOTE The install infrastructure cannot remove or modify this value.

The Agent is a Collector: The following shows the registry entry that is evaluated by this job

to determine if the agent is on a collector box HKEY_LOCAL_

MACHINE\SOFTWARE\Configuresoft\ECM\4.0\Installer\CDInstall. If this key exists and

has a value of 2 then this identifies the box as a collector box. NOTE: The install infrastructure

cannot remove or modify this value.

b. If the validate job is not able to communicate with the install infrastructure, it flags the install as

valid and the request continues.

c. If an error, an error would be any result other than Install required or Success, is generated by an

attempt to communicate with the install infrastructure, validate fails, as does the install, usually

with an error that mandates that an uninstall must occur prior to installing.

d. If the validate job is able to communicate with the Module installer, it gathers all the module

information available from the various install manifests it gathered, and stores this information as

a state variable so that other install jobs can use the information to see what was installed. It does

this in the method RecordModuleInstallerVersion, and stores the module names and versions in

the state parameter “install_module”. The module installer job uses this parameter to determine

what parts of the install infrastructure need to be installed.

3. Interrogate Target Environment: After the installation infrastructure has been deployed, the various

product modules need to be deployed. In order to find out what product modules need to be pushed

out, the following process occurs.

a. A connection is made to the module installer.

b. The runtime agent lock is updated.

c. The module installer returns all modules currently installed.

d. The product modules are then recorded in the database.

e. A failure here will cause install to fail.

Windows Agent Installation

VMware, Inc. 37

1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 67 68

Komentarze do niniejszej Instrukcji

Brak uwag

VMware VCM 5.3 Instrukcja Naprawy Strona 37

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Nie VMware VCM 5.3