36
/qb!
No user intervention is possible, but the installation process is indicated by a progress bar in %.
REBOOT =”ReallySuppress”
Suppresses restart after installation of the program.
REBOOT =”Force”
Automatically reboots after installation.
REBOOTPROMPT =””
After installation, a dialog window prompting the user to confirm rebooting is displayed (can’t be used along with
/qn
).
ADMINCFG =”path_to_xml_file”
During installation, parameters defined in the specified.xml files are applied to ESET security products. The parameter
is not required for remote installation. Installation packages contain their own
.xml
configuration, which is applied
automatically.
PASSWORD=”password”
You need to add this parameter when the ESS/EAV settings are password protected.
Parameters for ESET NOD32 Antivirus 2.x should be typed after the
setup.exe
filename, which can be extracted along
with other files from the installation package (e.g.,
setup.exe /silentmode
):
/SILENTMODE
Quiet installation mode – no dialog windows are displayed.
/FORCEOLD
Will install an older version over an installed newer version.
/CFG =”path_to_xml_file”
During installation, parameters defined in the specified
.xml
files are applied to ESET client solutions. The parameter is
not required for remote installation. Installation packages contain their own
.xml
configuration which is applied
automatically.
/REBOOT
Automatically reboots after installation.
/SHOWRESTART
After the installation, a dialog window prompting the user to confirm rebooting is displayed. This parameter can only
be used if combined with the
SILENTMODE
parameter.
/INSTMFC
Installs MFC libraries for the Microsoft Windows 9x operating system that are required for ERA to function correctly.
This parameter can always be used, even if the MFC libraries are available.
Under
Create/Select installation package contents
(2), the administrator can create a standalone install package
with a predefined configuration from an already existing and saved install package (the
Save As...
button). Such
installation packages can be run on the client workstation where the program is to be installed. The user only needs to
run the package and the product will install without connecting back to ERAS during the installation.
NOTE:
Adding a configuration to the
.msi
installation file means the digital signature of this file will no longer be valid.
Important:
On Microsoft Windows Vista and later we strongly recommend that you perform a silent remote installation
(the
/qn
,
/qb
parameter). Otherwise interaction with a user might cause the remote installation to fail due to timeout.
4.2.1 Requirements
The basic requirement for remote installation is a correctly configured TCP/IP network which provides reliable client
server communication. Installing a client solution using ERA imposes stricter conditions on the client workstation than
a direct installation. The following conditions should be met for remote installation:
Microsoft network client enabled
File and printer sharing service enabled
The file sharing ports (445, 135 – 139) are accessible
TCP/IP protocol
Administrative share ADMIN$ enabled
Client can respond to PING requests
Connectivity of ERAS and ERAC (ports 2221- 2224 are accessible)
Administrator username and password exists for client workstations (username cannot be left blank)
Simple file sharing disabled
Server service enabled
Remote Registry service enabled
