When you create a preconfigured package using the ESET Remote Administrator (ERA) Installation Packages Manager, a NOD32 Installation Package is created using the extension *.nip. If you would like to install this package locally to a client workstation, rather than through a push install, you can select one of two methods below. In the first method, you can convert the .nip file to an executable file (.exe) and, in the second method, you can save the configuration as an .xml file.
Locate the specific *.nip file that you would like to use. It should be located in the directory where your ESET RAS packages are stored. For example:
C:\Documents and Settings\All Users\Application Data\ESET\ESET Remote Administrator\Server\packages\install_v3\NOD32 v. 3.0.684.0\package_nt32.nip
Make a copy of the *.nip file and change the .exe extension to it. For example, package_nt32.nip would become package_nt32.exe. Copy the .exe file to the computer on which you would like to install it.
To install the package, execute the file. You must perform a silent install with a suppressed restart and execute the file with the appropriate switches. For example (including quotation marks):
"C:\Documents and Settings\eset\Desktop\package_nt32.nip.exe" /qn REBOOT="ReallySuppress"
The .xml configuration and the .msi package will be extracted and the installation will start automatically.
Name your ESET client configuration file cfg.xml. Place this file in the same folder or directory in which you saved the ESET .msi file.
Utilize the switches to install silently and supress restart with this method (including quotation marks):
"C:\Documents and Settings\eset\Desktop\eavbe_nt32.msi" /cfg=CFG.XML /qn REBOOT="ReallySuppress"
The ESET .msi install package will automatically detect cfg.xml, and then import the settings during installation.