User`s guide

28
which a line providing installation (or uninstallation)
of NOD32 on remote workstations will be inserted. Click
on the EDIT button to edit the le in the user-friendly
internal editor. Click on the SAVE button to conrm the
changes made.
HINT: Alternatively, you can choose your own way,
outside the console. Copy the le nod32installer.exe from
the RA server from corresponding package and install it
in your own way. It is located in the directory: C:\Program
Files\Eset\RA\Server\packages\{package_name}.
Variant “Send via E-mail” naturally sends the le
nod32installer.exe via e-mail. After running the email
attachment, either remote installation or remote uninstall
of NOD32 for Windows will start.
During the installation, again choose the
required Package and select addresses, where the le
nod32installer.exe shall be sent. It is also advised to dene
Subject (of e-mail) and Body (of e-mail).
For the RA server to work properly, it is required to
set the SMTP server address and sender e-mail address.
In case this information is not available, the e-mail can
be sent using the Microsoft Outlook application (Outlook
Express is not supported).
HINT: Alternatively, you can choose your own way,
outside the console. Copy the le nod32installer.exe from
the RA server from corresponding package and install it
in your own way. It is located in the directory: C:\Program
Files\Eset\RA\Server\packages\{package_name}.
Other information
Remote install in detail
In this chapter you can nd more detailed information
about the remote install process. In the case of a Push
installation, the following operations take place:
1) RA server contacts a remote workstation and attempts
to authorize by username and password, entered by
the administrator from the RA console.
2) If successful, the RA server connects to
the workstation using share ADMIN$ and
starts copying the le nod32installer.
exe belonging to the installation package.
3) The le nod32installer.exe is started as a service and
executed.
4) After that nod32installer.exe contacts the RA server
on port 2224 (TPC). For RA server this is a signal for
corresponding installation package again via share
ADMIN$
5) When the download nishes successfully, the
installation of the package starts, together with
predened attributes. Installation package is on
the machine unpacked and started using SETUP.EXE
together with attributes dened in given package.
Thanks to NOD32.XML the setting dened by
conguration editor NOD32 (more in chapter 2) will
be applied.
In the case of the variant “Export to logon script“, or “Send
via E-mail“, the process starts with the running of
the le nod32installer.exe (either manual – by user,
or automatic, e.g.: from logon script). Then these
operations take place:
1) The le nod32installer.exe is started as a service and
executed.
2) After that nod32installer.exe contacts the RA server
on port 2224 (TPC). For RA server this is a signal for
corresponding installation package again via share
ADMIN$ .
3) Access via share ADMIN$ and to remote installation
uses information dened in RA console by the
administrator in Remote Install folder, with the Log
on… button (Set Default Logon for E-mail and Logon
Script).
4) When the download nishes successfully, the
installation of the package starts, together with
predened attributes. Installation package is on
the machine unpacked and started using SETUP.EXE
together with attributes dened in given package.
Thanks to NOD32.XML the setting dened by
conguration editor NOD32 (more in chapter 2) will
be applied.
The le nod32installer.exe
The le nod32installer.exe is an installer that
will prepare NOD32 for Windows for remote install.
After executing, it is installed as a service. It can
perform the following tasks as well:
• Check, whether there is NOD32 for Windows already