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. [. . . ] This version is considered to be up-to-date and determines the currentness of the stations (meaning that the older versions differ from these ones in colors). With Change password button it is possible to change or set the password for RA server. It gives the option to change license key on RA server. Database Maintenance Tab Here you can set RA server behavior in connection with database maintenance. Following options will influence how many (X) events for each station should be saved in event log and scan log tabs. Only keep the latest X events for each client Only keep the latest X scan logs for each client Delete clients not connected for the last X months – the workstations that has not been connected to RA server for more than X months will be deleted from clients tab (usually the ones that do not exist in LAN) Following choices will influence how the old events should be deleted from the alert log, event log and scan RA Configuration License keys (. LIC files) NOD32 Remote Administration (or NOD32 Enterprise Edition package) is delivered with a license key – a file with . 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. Later manipulation of the license key has to be done manually. 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. exe service , and then every 60 minutes. 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. Events older that X months will be deleted. 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). [. . . ] 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. [. . . ]