ESET REMOTE ADMINISTRATOR 4 Manual de instalación descargar pdf (Pagina 33)

4. Installation of ESET client solutions

This chapter is dedicated to the installation of ESET client solutions for Microsoft Windows operating systems. Installations

can be performed directly on workstations, or remotely from ERAS. This chapter also outlines alternative methods of

remote installation.

NOTE: Although it is technically feasible, we do not recommend that the remote installation feature be used to install

ESET products to servers (workstations only).

4.1 Direct installation

With a direct installation, the administrator is present at the computer where the ESET security product is to be installed.

This method requires no further preparation and is suitable for small computer networks or in scenarios where ERA is not

used.

This task can be greatly simplified with the help of a predefined.xml configuration. No further modification, such as

defining an update server (username and password, path to a Mirror server, etc.), silent mode, scheduled scan, etc., is

required during or after installation.

There are differences in applying the .xml configuration format between versions 4.x, 3.x and 2.x of ESET client solutions:

Version 4.x: Download the installation file (e.g., ess_nt32_enu.msi) from eset.com and create your own installation

package in the Installation Packages Editor. Edit/Select the configuration that you want to associate with this

package, press the Copy... button next to the Package for Windows NT xx bit systems field and save the package as

ESET Install Msi File With Configuration (*.msi).

NOTE: Adding a configuration to the .msi installation file means the digital signature of this file will no longer be valid.

In addition, the steps from version 3.x apply to version 4.x as well.

Version 3.x: Download the installation file (e.g., ess_nt32_enu.msi) from eset.com. Copy the configuration file (cfg.xml) to

the directory where the install file is located. Upon execution, the installer will automatically adopt the configuration

from the .xml configuration file. If the .xml configuration file has a different name or is located somewhere else, the

parameter ADMINCFG =”path_to_xml_file” can be used (e.g., ess_nt32_enu.msi ADMINCFG =”\\server\xml\settings.xml” to

apply the configuration stored on a network drive).

Version 2.x: Download the installation file (e.g., ndntenst.exe) from eset.com. Extract the downloaded file to a folder

using a file extraction program such as WinRAR. The folder will contain installation files, including setup.exe. Copy the

nod32.xml configuration file to the folder. Run the setup.exe file – the configuration within nod32.xml will be automatically

applied. If the .xml configuration file has a different name, or is located somewhere else, the parameter /

cfg =”path_to_xml_file” can be used. (e.g. setup.exe /cfg =”\\server\xml\settings.xml” to apply the configuration stored on

a network drive).

4.2 Remote installation

ERA offers several methods of remote installation. Distribution of installation packages to target workstations can be

performed using the following methods:

Remote push installation

Logon script remote installation

Email remote installation

Upgrade

Remote installation by means of ERA consists of these steps:

Creation of installation packages

Distribution of packages to client workstations (push installation method, logon script, email, upgrade, external

solution)

The first step is initiated through ERAC, but the install package itself is located in ERAS, in the following directory:

%ALLUSERSPROFILE%\Application Data\Eset\Eset Remote Administrator\Server\packages

To launch installation packages through ERAC, click the Remote Install tab, select the Computers tab and right-click

1 2 ... 28 29 30 31 32 33 34 35 36 37 38 ... 91 92

Comentarios a estos manuales

Sin comentarios

ESET REMOTE ADMINISTRATOR 4 Manual de instalación Pagina 33

Comentarios a estos manuales

Relacionado con productos y manuales para Software ESET REMOTE ADMINISTRATOR 4