ESET REMOTE ADMINISTRATOR V1 User manual

Administration Installation Guide
2
NOD32 Version 2.7 Includes Windows Vista and 64-bit protection
Remote Adminstrator 1.0.14
and LAN Update Server 2.7
Installation
Guide
Proactive protection
against Viruses, Spyware,
Worms, Trojans, Rootkits,
Adware and Phishing
Best Detection
Fastest Performance
Minimal Resource
Utilization

Administration Installation Guide
2
Copyright © 1997 – 2007 ESET LLC. All rights reserved.
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 LLC. 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.
Eset, NOD32 and AMON are trademarks of Eset.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
Eset, LLC
610 West Ash Street
Suite 1900
San Diego
California
92101
U.S.A.
http://www.eset.com
For Sales and Technical Support (US and Canada):
Tel: [phone]
Fax: [phone]
Online purchase: http://www.eset.com/purchase/index.php
Sales email:
[email protected]
Technical Support Worldwide:
http://www.eset.com/support
Then by clicking on your country’s name, you can locate the support details
closest to you.
This guide is frequently updated to reect changes in the product. The
latest version can always be found at
http://download1.eset.com/manuals/nod32raman.pdf
This guide was prepared for NOD32 Remote Administrator Server, Remote
Administrator Console version 1.0.14 and the NOD32 LAN Update Server
version for Windows, Version 2.7 (December 2006)

Administration Installation Guide
3
Contents
Introduction
Minimum System Requirements
Section 1: Overview
What you can do with Remote Administrator
Summary of features
Section 2: Installation for an office network
Installing RAS and RAC
Section 3: Running Remote Administrator Console
Connecting to server
Section 4: Configuration Editor
Overview
Section 5: Create a package
Installation package
Section 6: Remote Installation of NOD32
Points to watch out for
Push installation
Export to logon script
Export via email
Manual installation
Section 7: Use of Tasks
Creating tasks
On-Demand Scan Task
Update Now Task
Section 8: More Detailed Information
Remote Install in detail
The file nod32installer.exe
Clients window
Context menu options
Context menu examples
Alert log window
Event log window
Scan log window
Tasks window
Reports window
License key (nod32.lic)
RAC connection to RAS + settings
RAC server options setup
Use RAC more efficiently
Section 9: Possible Problems & Error Codes
Error messages
Section 10: Installation in a multi-site network
Installation instructions
Section 11: Installation in a small network
Installation instructionInstallation instructions
Creating a Mirror
Creating a customized installation
Section 12: Additional information
Command line parameters
Page
3
4
5
6
7
8
9
10
14
15
17
18
33
34
35
36
37
39
41
42
43
44
46
48
49
50
51
52
54
55
56
56
56
56
57
59
59
61
63
65
66
70
71
74
75
76
78
82
83

Administration Installation Guide
4
Introduction
Congratulations, you have just purchased NOD32 Enterprise Edition
incorporating Eset’s Remote Administrator Server & Console, which will
help you manage the most advanced antivirus solution available in a
network environment.
The following information will help you to get a better understanding of the
many features of NOD32 Remote Administrator, so that you get the best
protection and administration possible.
NOD32 is more than just a virus scanner – being able to scan for known
viruses is the bare minimum that should be expected from an anti-virus
product, so it should be reassuring to know that NOD32 not only does
this faster, and more reliably than other products, but that it also has an
excellent track record in discovering new threats. In addition, version 2.7
includes detection for adware, spyware and riskware aswell as rootkit
detection with its Anti-Stealth technology. With NOD32 you can be sure you
have the most advanced and comprehensive virus protection possible.

Administration Installation Guide
5
Minimum System Requirements
Please make sure that the computer on which you plan to install NOD32
meets the minimum system requirements for the program to run:
Disk Space: 30MB free disk space
Graphics: VGA video card. (SVGA 800x600 recommended)
You must only install ONE anti-virus On-Access
scanner at one time (a scanner that is always running
while your PC is switched on); otherwise you could
cause serious system instability.
If you are installing NOD32 with another anti-virus
program, please make sure you do not enable both
On-Access scanners at once.
If another anti-virus program has previously been installed on your
computer, its scanner may interfere with NOD32. Usually resident
scanners will display an icon in the system tray (the area of the taskbar
near the clock). We recommend removing any other antivirus software,
including older versions of NOD32, before installing NOD32 Version 2.7, to
avoid the possibility of serious problems
Version 2.7 may be installed over your existing NOD32 if it is version 2 or
higher, however, if any problems were encountered, a clean installation is
recommended.
Operating system CPU RAM
Windows 98/ME 133 MHz/150 MHz 32 MB
Windows NT4/2000 133 MHz 32 MB/64 MB
Windows XP/2003/XP 64 or 32-bit 300 MHz 128 MB
Windows Vista 800 MHz 512 MB

Administration Installation Guide
6
Overview

Administration Installation Guide
7
Overview of what you can do with the
Enterprise Edition of Remote Administrator
This is the complete package for any medium to large sized business.
It comprises of the standard NOD32 antivirus for workstations, the LAN
Update Server (Mirror) version which will receive all updates & upgrades
from Eset, the Remote Administrator Server which will run on the
company’s server and the Remote Administrator Console where you can
administrate the whole setup.
This will mean that you only have to download updates to your server, thus
reducing internet trafc. Naturally, your server should be in operation during
the entire working day and should have an NT-based operating system
(NT4/2000/XP/2003) but doesn’t have to be a ‘server’ operating system.
The updates will be stored there and then picked up by the workstations in
your network. So the server acts as a ‘mirror’ to your clients and is referred
to as such in the setup.
Using NOD32 Remote Administrator Console (RAC), the administrator
can get a global overview of the NOD32 antivirus system activity on
network workstations, and can receive information about threats, or other
problems, via email or Windows Messenger. The information retrieved
from the workstations is stored centrally on the server (NOD32 Remote
Administrator – RAS) which the administrator can access via RAC from his/
her own workstation or laptop. The communication takes place both ways
and thus the administrator can immediately react to fresh situations, and
assign tasks to the relevant NOD32 on client workstations.

Administration Installation Guide
8
Important features of NOD32 Remote
Administrator:
NOD32 Remote Administrator is a powerful tool that enables an
administrator to manage large installations of the NOD32 antivirus
system in large corporate networks. It consists of two modules -
NOD32 RA Server (RAS) and NOD32 RA Console (RAC).
FEATURES
Quick overview of your network security situation
Comprehensive statistics in an intuitive graphical form
Enables virus scan on remote disks
Remote NOD32 client conguration le editing on chosen
workstations
Remote installation/uninstall of NOD32 antivirus system
Localization of unprotected computers in network
►
►
►
►
►
►

Administration Installation Guide
9
Installation
for an office network

Administration Installation Guide
10
Installation instructions for a typical ofce
network setup.
When you received your Enterprise Edition license email, you will have
seen the Username and Password required to access the Eset servers for
updates and there will have been a .lic key also attached (nod32.lic). This
key is specic for your RAS and determines how many clients you can
connect to your server and the expiry date of the license.
Save the nod32.lic key you received as an attachment with the email
from Eset to the desktop for the time being. (Note: do NOT use a web
based email program to download this attachment. eg: Outlook Web
Access, because this will corrupt the key).
AFTER installation is complete, you should move the nod32.lic key to
C:\Program Files\ESET\RA\Server directory and re-start the RAS
service.
Here are the basic, recommended steps to take when setting up Enterprise
Edition for NOD32:
Install Remote Administrator Server (RAS)
Using your Username and Password, download and install NOD32
Remote Administrator Server (RAS) onto your server (http://www.
eset.com/download/balance.php?dir=/download/ra/rasrvnten.exe).
The product must be installed on an MS Windows NT based operating
system (NT4, 2000, XP, 2003). RAS is installed by running the le
rasrvnten.exe.
During installation, the program will ask for the location of the license
key, ie: the le called nod32.lic, which contains information about its
owner, its expiry date as well as about the number of users, for which
the RAS was purchased. Alternatively, you can copy the key later into
the directory C:\Program Files\Eset\RA\Server (it is activated after
restarting the NOD32 Remote Administration Server service). Later
on, after connecting to the server from the console (RAC), Information
included in the key can be seen in Help > About NOD32 Remote
Administrator Console.
During the ‘Expert’ installation, the name of the server, under which
workstations in the network recognize it, is required. If not stated
otherwise, the server is represented using the name of the machine/
server where RAS is being installed.
Please be careful when entering the name of the server. This name
is used by nod32installer, providing remote installation of NOD32
on workstations. If RAS was not visible under this name, the remote
installation could fail.
We recommend entering the DNS name of the server.
►
►
►
►
►

Administration Installation Guide
11
RAS is installed as a service. Note: The service is installed, but not
started, during RAS installation. You can control the service manually
using these commands:
“c:\program les\eset\ra\server\nod32ra.exe” /installservice
“c:\program les\eset\ra\server\nod32ra.exe” /removeservice
You can stop and start the service by going to Start > Control Panel >
Administrative Tools > Services > NOD32 Remote Administrator Server
> ‘Start the service’,
Install Remote Administrator Console (RAC)
Using your Username and Password, download and install NOD32
Remote Administrator Console (RAC) onto your server plus any
machine that you want to administrate your clients from. ie: your
workstation or laptop as well as the server if you wish. (http://www.
eset.com/download/balance.php?dir=/download/ra/raconsnten.
exe)
Install NOD32 LAN Update Server
Using your Username and Password, download and install NOD32 LAN
Update Server (Mirror) version onto your server (http://www.eset.com/
download/balance.php?dir=/download/win/v2ad/ndntenad.exe). Its
virus signature database will form the basis of a so called Mirror for the
client workstations.
For detailed instructions on downloading and installing NOD32 LAN
Update Server (Mirror) version (which is the same as installing the
Standard, single-user version) please click here: http://download1.
eset.com/manuals/StandardInstallGuide.pdf. The IMON module
should not be running on the server. In fact, the only module that is
required on a server is AMON.
If you wish, you may defer the restart until all other installations are
completed. Once installed and you have rebooted your server, NOD32
will automatically update. You should then create a Mirror on the server.
Click this icon once in the system tray, which will open the Control
Center.
►
♦
♦
►
►
►
►
►

Administration Installation Guide
12
Creating a Mirror
Click ‘Mirror’
Click ‘Setup’
Check ‘Create update mirror’
Check the ‘Available versions’ you require for your network. ie: WinNT
machines and/or Win9x machines. All versions that will be running on
the workstations should be checked.
Setup a path to the Mirror on your server. You can choose to create
this folder anywhere you wish, but it’s recommended to keep the path
reasonably short (ie: C:\Mirror or C:\NOD32\Mirror or C:\Program Files\
Eset\Mirror)
Check ‘Require permission to perform program component upgrade’.
Besides the virus signatures database update, a license also includes
program updates – program component upgrades, which require a
restart of the operating system and bring a lot of new features and
improvements to NOD32 (it is an upgrade to a completely new version,
eg: from 2.5 to 2.7). Choose this to ensure that the program component
upgrade will not be applied to a local update server immediately
it is available on the servers of the Eset company. NOD32 on the
workstations will remain in the current version, and the workstations will
only accept virus signatures updates from the mirror. It is up to the user
to consider this option, especially since before updating all workstations
in the network, the new version may be tested in a detached network
dedicated to testing.
Check ‘Enable access to les via the HTTP protocol’
Click ‘OK’
Click the ‘Update’ button to update your
newly created Mirror, since there may
be more components mirrored than are
used by the local system.
1.
2.
3.
4.
5.
6.
7.
8.
9.

Administration Installation Guide
13
If you would prefer a Shared Folder Mirror path, when entering it,
please use the UNC path. Let’s assume that the shared folder is named
NOD32NET and is located on the MAIN server. Then enter the path in
this form: \\MAIN\NOD32NET
In this case, a Logon name and Password should be entered that the
clients will use to access the Mirror on the server.
(Optional) Download NOD32 for Windows,
standard, single-user version(s)
RAS has both of the installers (Windows NT/2000/2003/XP/Vista and
Windows 95/98/ME) embedded into the program but because the
contents of RAS is not updated as frequently on the Eset website as the
standard version of NOD32, you may wish to download the very latest
versions to be installed on your client machines as described above,
which will save pushing a possible Program Component Upgrade at
some point after the initial installation on the client workstations.
Using your Username and Password, download only NOD32 for
Windows NT/2000/2003/XP/Vista 32-bit/64-bit onto your server (http://
www.eset.com/download/balance.php?dir=/download/win/v2st/
ndntenst.exe) assuming you have machines running these operating
systems in your network.
Using your Username and Password, download only NOD32 for
Windows 95/98/ME onto your server (http://www.eset.com/download/
balance.php?dir=/download/win/v2st/nd98enst.exe) assuming you
also have machines running these operating systems in your network. If
not, there’s no need to download this version.
SAVE these 2 installers into a new folder and call it NOD32 Installers,
for example, and place the folder in C:\Program Files\Eset\RA\Server,
or wherever you choose on the server. It is not necessary to install the
standard, single-user version of NOD32 at this point.
The initial downloading and installing of components is now complete.
►
►
►
►
►
►
►

Administration Installation Guide
14
Running RAC

Administration Installation Guide
15
Setting up RAC connection to the server.
Run RAC by double-clicking on this icon on the desktop of
your workstation or laptop.
Note: No clients will appear yet, unless you have already manually
installed NOD32 onto some workstations and congured them for
Remote Administration via their Control Center(s).
Go to Tools ---> Console options ---> Connection ---> Add/Remove, and
enter the DNS name of your server (You can use the IP address instead
but if that ever changed in the future, it might cause a problem) ---> click
OK.
From the ‘Select Connection’ box, choose the server name you’ve just
added.
Press ‘Connect’.
In the ‘Current state of connection’ window, you should see the name
of the server. If true, press OK. Note: The server will not show up in the
upper section of the RAC until it has at least one client connected.
►
►
►
►
►

Administration Installation Guide
16
The attribute Primary Server denotes the name of the server with RAS
installed, to which the remote client is connected via NOD32 Control
Center. If there is another server showing other than the one which the
administrator is currently connected to, then it is a result of replication.
You may add a connection via SMTP server also if you have a mail
server address and you wish to be contacted via email from your clients
about alerts, etc. or you wish to install on some clients via email: Tools
---> Server Options ---> Other Settings tab.
►
►

Administration Installation Guide
17
Configuration
Editor

Administration Installation Guide
18
Overview of the Conguration Editor
If you’re already familiar with the standard version of NOD32 for Windows,
you’ll know that the program has a vast array of options when it comes to
scanning, updating, scheduling and reporting inltrations.
The Conguration Editor does exactly the same job but is designed for you,
the administrator of your network, to create a universal set, or various sets,
of parameters associated with the installation package(s) you will soon
create.
The Conguration will be saved as an .xml le. You can set this up before
or during the creation of your installation package. Here are 3 ways to do
this:
Start ---> Program Files ---> Eset ---> Conguration Editor. Now make
the necessary changes to your conguration as described on the next
page and save, with a title and directory of your choice, on the server.
RAC ---> Tools ---> Conguration Editor. Now make the necessary
changes to your conguration as described on the next page and save,
with a title and directory of your choice, on the server.
During the setup of an installation package. Details on page 33.
1.
2.
3.

Administration Installation Guide
19
The Conguration Editor setup
The conguration le (.xml) may be created on the server
or, you can also install NOD32 LAN Update Server version
on your workststion and create the conguration there and
then copy it to the server (C:\Program Files\Eset\RA\Server\
MyConguration.xml).
Start
Program Files
Eset
Conguration Editor.
You will now see a window like this:
Rather than look at every single option in the editor, we’ll take a look at the
crucial areas that should be considered when setting up a conguration, but
obviously, you can change as many options as you wish. Further in-depth
information can be found on page 49.
When an item is changed, the radio button beside it turns blue. This helps
you to identify quickly the areas of alteration that you’ve made. Also, in
future conguration amendments, the client workstations will only look for
any new items that have been modied.
►
►
►
►
►

Administration Installation Guide
20
The rst section is General and we’ll look at the Settings area. Here it is
advisable to ‘lock’ the settings in NOD32 and Password Protect them with a
password of your choosing, so that only you can alter the conguration on
any workstation, and not your clients.
The next section is Notications. If you choose to have messages
sent to you about alerts/inltrations on your client machines, you will need
to enter the SMTP server address (or IP address) that you use plus the
sender address should be entered exactly as
[e-mail]
which will enable you to identify the relevant machine in your network. Pay
close attention to the way %ComputerName% is entered as this is case-
sensitive.
Also, enter the email address
you’d like the warnings sent to.
Also you can choose to have
Windows Messenger messages
sent via your LAN instead of, or
in addition to, the email method.
Here, you will just need to
enter the name(s) of the PC(s)
you’d like the messages sent
to, delimited by a semicolon or
comma.