User`s guide
11
Protection Modules > AMON > Setup > Security tab
> Enable automatic startup of AMON.
• AMON / Settings / Enabled
AMON – the resident shield will watch over the ma-
nipulation of les (YES), or will be running only in the
background and will not watch over the manipulation
(NO).
• IMON / Settings / Register IMON to the system
We recommend setting this option to YES, if it is
a workstation, and to NO, if NOD32 for Windows will
be installed on a server, or a PC, where some other
services are running.
These settings can be changed also in the menu
NOD32 Control Center > Threat Protection Modules >
IMON > Quit.
• IMON / Settings / Enabled
IMON – the Internet monitor – will control commu-
nication (YES), or will be running only in the backg-
round and will not watch over the communication
(NO).
• Update / Prole / Settings / Update server
This option sets a path to the server, which will be ser-
ving as an update server. By default it is set to AUTO-
SELECT - NOD32 automatically chooses one of the Eset
company update servers.
• Update / Prole / Settings / Username and Password
Username and password are authorization data to the
above mentioned server. In case NOD32 is updated di-
rectly from an Internet update server of the Eset Com-
pany, then enter the username and password you re-
ceived when you purchased the NOD32 license. If you
use your own update server (see chapter about “Mir-
ror”), enter the username and password for this upda-
te server (also described in a separate chapter).
• General /Settings / ThreatSense.Net
This system allows sending of suspicious les (that
were identied by heuristic analysis as probably be-
ing infected by an unknown virus) from client to our
virus lab. We recommend considering this feature,
especially the option that decides whether the suspi-
cious les will be sent automatically, after user’s con-
sent or not at all..
Proles – Scheduler/Planner
NOD32 for Windows allows dening “groups” of set-
tings – proles – in certain parts of the program, espe-
cially in update proles and scanning proles. You may,
for example, want to have one prole p roviding updates
from a local server and another one, providing updates di-
rectly from the Internet. The same applies to the scanning
proles – one prole would test local disks without scan-
ning of archives, and another would scan network drives
including archives.
The proles are interconnected with scheduled tasks
(NOD32 Control Center / NOD32 System Tools / Schedu-
ler/Planner). For example, after standard installation of
NOD32 for Windows, a prole is created called My Pro-
le, which as one of its tasks sets automatic update for
every hour.
Please pay attention when setting compatibility of
the proles and the scheduled tasks, and please also be
careful when dening your own proles – check whether
the proles are really launched automatically.
If there’s no automatic update scheduled, it is shown
in the Setup of Automatic Update tab, as can be seen in
the screenshot.
chapter 1 / Basic network features of NOD32 for Windows










