User manual NOD32 ESET REMOTE ADMINISTRATOR SERVER 2

[. . . ] We protect digital worlds NOD32 for Windows Administrator NOD32 Remote Administrator User’s guide content chapter 1. No part of this document may be reproduced or transmitted in any form or by any means electronic or mechanical, for any purpose without the express written permission of Eset,  spol. Information in this document is subject to change without prior notice. Certain names of program products and company names used in this document might be registered trademarks or trademarks owned by other entities. [. . . ] In this case the key must be copied into the folder C:\Program Files\Eset\RA\Server, which is done automatically during installation of the server part. The license file contains information about expiry date and extension of the NOD32 Remote Administrator product license. The license file in fact determines functioning of NOD32 Remote Administrator as a product. If there are more license keys in the folder C:\Program Files\Eset\RA\Server, then RAS will choose the most appropriate (more detailed information can be found in the file nod32ra. If the license key has expired, NOD32 Remote Administrator will run in demo mode, i. Delete alert logs older than X months Delete event logs older than X months Delete scan logs older than X months Clean up every X minutes – settings above will be applied every X minutes. When deleting events (by administrator or functions described above) no physical cleaning directly from the database file is done. To clean the events directly from the database (this will compact the size of database file), it is necessary to set the following option: Compact every X (days, weeks, months) During this activity the service of RA server is temporarily stopped (for maximum few minutes) till the database is “cleaned”. In this time the RA server will not be able to accept console requests and workstation information. Therefore it is no recommended to do this activity too often and during the heavy traffic. Loggig Log Enable logging – enables logging of RA server events NOD32 RA server is able to log to the file (Log filename), whereas the size of this file can be restricted (Rotate when greater than). At the same time it is possible to enable log to OS application log (Log to OS application log) or enable log over database (not recommended). replication Log Replication „to“ settings Enable „to“ replication – enables replication – described in “Large Hierarchical Networks” chapter. Upper server – the address (IP or according to DNS) of superior RA server to which the data replication from just configured RA server will be applied. From the picture in “Large Hierarchical Networks” chapter it is obvious what should be written in this column, see upper server attribute. Replicate every XX minutes – replication frequency (every XX minutes) Replicate Up Now – instant application to chosen upper server Checkboxes on the left part enable to define log types (alert, event, scan), which can be replicated (transferred) to superior RA server on administrator’s request. Checkbox in the right part enables defining if this should be done automatically (Automatically replicate . Administrator can request them individually from inferior server any time. Replication „from“ settings Enable „from“ replication – ticking this option in Allow servers column allows to define RA servers (their name), from which the RA server will accept replication requests. Standard replication runs on TCP 2846 port, thus it can be changed (on inferior server directly in this tab, on superior – upper server in Other Settings tab). Other settings Tab: SMTP settings Server - SMTP Server address, through which the reports will be sent, or requests for remote installation via email Sender address - e-mail address which will be set as the „sender“ in outgoing e-mails. Allow new clients – Clients are, by default, added to the list (the Clients tab in console) automatically at the moment when RAS registers the first attempt to establish connection from a new, so far unregistered client module of NOD32 Control Center. [. . . ] It leads to another idea – you can use more administrators to control only partial groups of client workstations (and which are connected to a certain RAS and to RA servers inferior to it). What information will be retrieved from the client workstations connected to inferior RA servers is configured in the replication setup. Replication is nothing else but a  communication of RAS with superior RA servers. Its specific features are described in the chapter about the RA server setup. [. . . ]