7
2.1.3
Installation
The installation process is initiated by running the installation package. During this process, you will be prompted
to upload a license key, which is a file with the
.lic
extension. If the Expert installation mode is selected, several
other parameters can be defined. They can be modified later in ERAC, but in most cases there is no need to do
so. The only exception is the server name. The server name should be the same as in the DNS, or the
Computer
name
value of your operating system (
My Computer > Properties > Computer name
tab). The IP address of the
computer can also be used. This is the most essential piece of information for performing remote installation. If the
name is not specified during installation, the installer will automatically supply the value of the system variable
%COMPUTERNAME%, which is sufficient in most cases.
By default, the ERAS program components are installed to the following folder:
%ProgramFiles%\Eset\Eset Remote Administrator\Server
and other data components such as logs, install packages, configuration, etc. are stored in:
%ALLUSERSPROFILE%\Application Data\Eset\Eset Remote Administrator\Server
NOTE:
On servers with ERAS, the ERA client should also be installed. ERAS uses the current virus signature database version
number as a reference number for clients. Installation of a solution with the LAN Update Server (Mirror) is recommended.
2.1.4
Logs
ERAS does not generate any output for a log file. This file is located in the folder:
%ALLUSERSPROFILE%\Application Data\Eset\Eset Remote Administrator\Server\logs
The log file titled “era.log” stores all events that take place during operation of ERAS, including error messages
related to starting the ERAS service, such as a corrupt database error or license key error. The log file allows you to
quickly determine the exact cause of ERAS failing to launch correctly.
NOTE:
In the ERAS setup (accessible through ERAC) you can define several levels of logging including log rotation, to
significantly reduce log file size and growth rate. Logging to the operating system application log can also be configured.
2.1.5
Configuration
To a certain extent, ERAS can be configured during installation (particularly in Advanced mode) or later using the
ERA Console connected to the ERA Server. If need be, the .xml configuration files on the server can be modified.
These files are located in the following directory:
%ALLUSERSPROFILE%\Application Data\Eset\Eset Remote Administrator\Server\configuration
NOTE:
For security reasons, password setup is separated (into individual .xml files) from other setup options. Potential lost
passwords (e.g. to access an ERA Server) can be resolved by deleting the era_private.xml file located in the Configuration folder
2.1.6
License keys
The license key is a file with the .lic extension, similar in structure to the .xml format, but protected by an electronic
signature. This file is required to successfully configure ERAS. The file contains the following information:
• License owner
• Number of client machines (number of licenses)
• License expiry date
Here are four common problem scenarios related to license key files:
• .lic file is not present
ERAS will run in a trial mode – it will be possible to administer only two clients (workstations) for an unlimited time
period.
• .lic file is corrupt
The ERA Server service will not launch at all. The event will be logged to the era.log file.
• .lic file has expired
If the expiry date defined in a .lic file is older than a current date, it is not possible to establish connection between
ERAC and ERAS. ERAS will continue to accept information from clients, but will not be able to administer them.
