33
There are differences in applying the .xml configuration format between versions 3.x and 2.x of ESET client solutions:
•
Version 3.x: Download the installation file (e.g., ess_nt32_enu.msi) from ESET’s web site. Insert the .xml
configuration file (cfg.xml) to the directory where the install file is located. If you run the installer, it 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’s web site. Extract the downloaded file
to a folder. The folder will contain installation files, including setup.exe. Copy the nod32.xml configuration file
into the folder. Run the setup.exe file and the configuration within nod32.xml
will be automatically applied. If the
.xml configuration file has a different name, or it 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).
NOTE:
Other parameters mentioned in the previous chapter can be used, too.
6.2.2
Remote installation in general
ESET Remote Administrator offers several methods of remote installation, listed directly below. The methods differ
with respect to how installation packages are delivered to target workstations.
•
Remote push installation
•
Logon script remote installation
•
Email remote installation
Remote installation does not necessarily have to be performed using the ERA tools – other methods are available
(central distribution of MSI, LANDesk, etc.). In the end, the most important aspect is to deliver the installation file
(or the agent) to clients and to ensure that it is launched under an Administrator account. For this purpose, the
direct installation described in the previous section can also be used.
Remote installation by means of ESET Remote Administrator consists of these steps:
•
Creation of installation packages
•
Distribution of packages to client workstations (push installation method, logon script, email, external solution)
The first step is initiated through the ERA Console, but the install package itself is located in the ERA Server, in the
following directory:
%ALLUSERSPROFILE%\Application Data\Eset\Eset Remote Administrator\Server\packages
To launch installation packages through the ERA Console, click the
Remote Install
tab and click the
Packages...
button.
Each installation package is defined by a
Name
(
See (1) in Figure 9 above). The other sections of the dialog window
are related to the content of the package, which is applied after it has been successfully delivered to a target
workstation. Each package contains:
•
Installation files (
2
) of ESET’s client solution
•
.xml configuration file (3)
•
Command line parameters(4)
The
Type
drop-down menu in section 1 extends the possibilities of ERA. In addition to remote installation, ESET
client solutions can be uninstalled remotely using the
Uninstall ESET Security Products and NOD32 version 2
option. Remote installation of an external application can also be performed, by selecting
Custom package
.
NOTE:
For technical reasons, the installation of older ESET solutions (version 2.x) is a separate function from the installation of
generation 3.x solutions. For the same reason packages are stored in two separate folders on ERAS.
NOTE:
The
Custom package
option offers a variety of methods, including the uninstallation of security solutions from other
vendors (if a suitable batch command is used).
