43
The username and password of the account under which the installation of the package is to be performed must be an
account with administrator rights or, preferably, a domain administrator account.
During the remote installation process, backward connection to ERAS takes place and the agent (
einstaller.exe
) adopts
settings from the
Set Default Logon for E-mail and Logon Script Installations
option.
If the
einstaller.exe
agent is started manually on a target workstation, the remote installation is handled in the following
way:
The
einstaller.exe
agent sends a request to ERAS (TCP port 2224)
ERAS starts a new push installation (with a new agent) of the corresponding package (sent via the share
admin$
). The
agent waits for an answer from ERAS (sending the package via the share
admin$
). In the event that no answer
arrives, the agent will attempt to download the install package (via the TCP/IP port 2224). In this case, the
administrator username and password specifed in
Remote Install > Logon ...
on the ERAS is not transferred and the
agent attempts to install the package under the current user. On the operating systems Microsoft Windows 9x/Me,
the administrative share cannot be used, therefore the agent automatically establishes a direct TCP/IP connection to
the server. The new agent then starts downloading the package from ERAS via TCP/IP protocol.
The installation of the package is launched, applying the associated .xml parameters under the account defined in ERAS
(the
Set Default Logon for E-mail and Logon Script Installations
option).
4.2.6 Upgrade
This type of installation is designated for clients with ESS/EAV version 4.2 and later. Beginning with version 4.2, a new
upgrade mechanism was implemented that allows ERA to initiate the upgrade process on the client side without the
need of the
einstaller.exe
agent. This mechanism works in a manner similar to the program component update, - or
PCU, which upgrades clients to a newer version of the program. For version 4.2 and later ESS/EAV clients, we strongly
recommend this type of upgrade.
NOTE:
If a custom configuration file has been defined for the installation package it will be ignored during the upgrade.
