Custom remote install

It is not a requirement to use ERA tools to remotely install ESET client solutions. In the end, the most important aspect is to deliver and execute the einstaller.exe file on client workstations.


For einstaller.exe to launch, the user currently logged in does not necessarily have to be an administrator. The agent adopts the required administrator username/password/domain from ERAS. For more information, see the end of this chapter.


The einstaller.exe file can be obtained as follows:

· From the Computers tab (in the Remote Install tab), right-click anywhere in the tab, choose Export to Folder or Logon Script from the context menu and select the Type and name of the Package to be installed.
· Click the … button next to Folder and select the directory where einstaller.exe will be exported.
· Click the Export to Folder button.
· Use the extracted einstaller.exe file.


NOTE: The ”Direct installation with predefined XML configuration” method can be used in situations where it is possible to provide administrator rights for the installation. The .msi package is launched using the /qn parameter (version s 4.x, 3.x) or the /silentmode parameter (version 2.x). These parameters will run the installation without displaying a user interface.




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).