42
7. Deployment scenarios for ESET Remote Administrator,
Mirror server and ESET client solutions
7.1 Small network – 1x ERAS, 1x Mirror server
Suppose all clients are Microsoft Windows 2000/XP workstations and notebooks, networked within a domain.
The server named GHOST is online 24/7 and can be a Windows workstation, Professional, or Server edition (it does
not have to be an Active Directory Server). In addition, suppose that notebooks are not present in the company’s
network during the installation of ESET client solutions. The network structure may resemble the one displayed
below:
Figure 13
Network structure in a small company
7.1.1
Installation of ERA Server
Install ERA Server on the server named GHOST. During the installation, the license key file (nod32.lic) must be
supplied in order to provide operation of ERAS for a defined period. After installation, the ERAS service is launched
automatically. The activity of the ERAS service is recorded in the following file:
%ALLUSERSPROFILE%\Application Data\Eset\Eset Remote Administrator\Server\logs\era.log
7.1.2
Installation of ERA Console
Install the ESET Remote Administrator Console to the administrator’s PC/notebook (as shown in the lower part
of the picture). If the Console is installed on the same computer as ERAS, the ERAS server name (GHOST, in our
example) should be automatically inserted into the Console settings. If the Console and ERAS are installed on
different computers, click
File > Edit Connections...
and click the
Connection
tab. Click the
Add/Remove...
button
to add the ERA Server name.
For more information see section 4.1, “Connecting to ERAS.”
