User manual MTD ZYJ192A

[. . . ] 39 INTRODUCTION The MTD Antivirus system offers a  wide range of tools, which make running and managing both smaller and larger company networks easier. Even the multi-license MTD for Windows offers the basic network services. Especially a feature called Mirror, which serves to decrease traffic across your Internet LAN connection. Client workstations, with MTD installed, will not download updates directly from the manufacturer (Eset company), but from a local update server, which is located in the same LAN. [. . . ] Clients Report, Alerts Report, Events Report, Scans Report, Tasks Report – typical reports that can be viewed in the Clients, Alert Log, Event Log, Scan Log or Tasks tab. Comprehensive Report – summary of these types: Combined Top Clients / Top Viruses Combined Top Viruses / Alerts Comparative Progress Specified Alerts Progress Remote Install This tab offers several variants of remote installation of the MTD Antivirus System on workstations and related features. More detailed information can be found below. Clients than is defined in the license key (purchased), only a limited number of clients, corresponding with the defined number, will be displayed. 11 license key can be changed remotely on RA server via RA console. it is possible in the menu Tools/ Server options – Renew License… button. Note: Should you have any problems with application of license keys, please look in the file C:\Program Files\ Eset\RA\Server\nod32ra. Log where you can find the exact reason for the failure. RA server configuration To configure RA server, connect RA console to it (for example in the menu File / Edit Connections…) and then select Tools/Server Options… General Tab Information on server part of RA Curent MTD ver. Attribute is taken from MTD for Windows that physically runs on the same machine as RA server. 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). 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. Thus the transmission band among RA servers can be partly saved. 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. Higher number of servers can be separated by commas. 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 MTD Control Center. [. . . ] Client Client RAC (Console) Client RAS 1 Client Client Client Client RAS 2 (Upper server RAS 1) Client Client Client Client Client RAS 5 (Upper server RAS 3) Client Client RAS 3 (Upper server RAS 1) Client RAS 4 (Upper server RAS 3) Client Client Client Client RAS 6 (Upper server RAS 5) Client Client replication way 36 Networks consisting of superior / inferior RAS servers allows the administrator to only control those client workstations that can be momentarily accessed by RAS (using RA console) and eventually can control clients connected to inferior RA server(s). So if the administrator connects using RA console for example to RAS3, he/she will be able to control client workstations connected to RAS3, RAS4, RAS5, and RAS6. If the administrator connects to RAS5, he/she will be able to control RAS5 and RAS6. and if he/she connects to RAS1 , he/she will be able to control all workstations of course. [. . . ]