User`s guide

27
chapter 3 / Remote installation
Remote Installation Process
How to create and congure
installation packages
First of all, create installation packages – les with
*.nip extension, or installers for specic workstations
(according to their operating system) with a preset
conguration.
To do it, click on the Packages (the Manage Packages
section) button in the Remote Install tab.
In the Create/Select NOD32 installation package
contents section, create (clicking on the Create button),
or choose already existing (the Select button) “content”
of package. If you run the program for the rst time,
choose Create. In the Source section, browse for NOD32
installer (in a form that can be also downloaded from
the Internet – to navigate to the Eset website, click on
the Download button), or for the le update.ver from the
update copy (mirror).
In the Package section, dene where the content
will be saved. By default it is set to Server, or the PC
where the RAS service is running. Or, alternatively, export
the package to an EXE le. Click on the Create button to
create. The console will automatically detect, for which
version is which installation dedicated, and will distribute
it accordingly.
It is recommended to associate a new package
to a conguration that will be applied on remote
workstations. To do it, navigate to the Edit/Select
conguration associated with this package section. Click
the Select button to choose an already existing XML
conguration le, or create a new one with the Edit
button. If you chose both Windows NT and Windows
9x workstations in the previous paragraph, then after
clicking on the Edit button you have to decide which
version of operating system it will be used (by default
for the both). In the section Edit/Clear command line
associated with this package you can dene command
line parameters, which will be used with the package.
A summary of the parameters can be found below in the
corresponding chapter.
Export to remote workstations
PUSH install method
It is a method where the installation is “pushed”
to remote workstations directly on administrator’s
command. This is possible only assuming that there
is a Windows NT based operating system installed on
workstations (NT4, 2000, XP…).
Choose the workstations in the Push Installation
dialog window (click on the Install…button in the
Remote Install tab) where NOD32 for Windows will be
installed. To select a workstation, click the right mouse
button and select Copy to Remote List, or use the drag &
drop method in the left section (Network places). To get
current information from a workstation, click the right
mouse button on it and select Get Info (in the Remote
installation section). Similarly, you can start remote
installation itself (the Install option), or uninstall (the
Uninstall option). To apply the installation, select
a “package” in the pull down menu, and select
workstations (press CTRL or SHIFT and click the left
mouse button to select more workstations).
The console may ask for administrator’s username
and password for this situation. Please specify whether
the workstation is located in a domain or in a workgroup.
“Export to logon script” and “Send via
E-mail”
These two methods are almost similar. They dier
only in the
way the le nod32installer.exe is sent to target
workstations.
In case of the version “Export to logon script”, select
Package in the section Installation location, dene the
directory where the le nod32installer.exe will be located,
or edit the path to the parent directory “from the point
of view” of remote workstations (the item Share). It is
required to enable access to the directory for the remote
workstations.
In the section Script location, select a directory where
the logon script to be edited is located.
All corresponding les in the directory will be
displayed according to the mask in the File(s) section
(including logon scripts). Now also select les into