Direct installation

For a direct installation, the administrator must be present at the computer where the ESET security product will be installed. This method requires no further preparation and is suitable for small computer networks or in scenarios where ERA is not used.

You can use a predefined.xml configuration to make direct installation easier. 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 5.x, 4.x, 3.x and 2.x of ESET client solutions:

Version 5.x: Apply the same steps as for the Version 4.x.

NOTE: You can install ESET Security products for Linux and Mac using v.5 clients.

Version 4.x: Download the installation file (for example, 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, click Copy... next to the Package for Windows NT xx bit systems and save the package as an 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 (for example, 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).

NOTE: If you are installing ESET Smart Security (includes personal firewall) you must allow sharing and remote administration in these solutions. If you do not the network communication between such clients and the ERA Server would be blocked.