Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


gbmolina

nod32 v3.0.621 silent install problems

24 posts in this topic

hi there, I´ve been trying to get the nod32 v3.0.621 silent install with WPI running but with no success, here is the code I use:

msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qb /cfg=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml

if anyone can tell what am I doing wrong would vey much appreciate it. thanks.

PS first I get the windows installer window which shows me the aveilable commands (I tried most of them, nothing happens), then WPI just quits giving an error report about the install process :wacko:

I also tried the /silen /passive switches with no success...

0

Share this post


Link to post
Share on other sites
You should use /qn instead /qb. :rolleyes:

thanks, but it did not help, same error and no installation at all.

0

Share this post


Link to post
Share on other sites

I don't know what happening when you run your command. Do you get any error message?

To find out which step(s) in installation process fail I would try to run this MSI in 3 steps:

1. msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" (without any switches) if it works, go to step 2.

2. msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qn. if it works too, go to step 3.

3. msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qn /cfg=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml

If it still doesn't work, put </l* c:\eavbe.log> in the end of your command to find out what's happening when Msiexec.exe trying to install that MSI-file.

0

Share this post


Link to post
Share on other sites

I've exactly the same problem.

It looks like the installer doesn't like the \cfg command...

0

Share this post


Link to post
Share on other sites
I've exactly the same problem.

It looks like the installer doesn't like the \cfg command...

you mean to tell me that if i remove the /cfg everyhting will be ok? have you tested that?

0

Share this post


Link to post
Share on other sites

I have I install my Nod32 with just the /qn switch

Edited by Kelsenellenelvian
0

Share this post


Link to post
Share on other sites
I have I install my Nod32 with just the /qn switch

are you sure? are you talking about nod32 v3.0.621? you mean a totaly silent install with NO reboot at the end?

0

Share this post


Link to post
Share on other sites

I am using the same your NOD32 version, if you're already extracted EXE to MSI, using nod32.msi /qn switch is correct. It will not REBOOT

0

Share this post


Link to post
Share on other sites

cmd1[pn]=['"%wpipath%\\Install\\Nod32av.msi" /qn'];

Is my WPI command.

0

Share this post


Link to post
Share on other sites
cmd1[pn]=['"%wpipath%\\Install\\Nod32av.msi" /qn'];

Is my WPI command.

i am not using wpi install i am using only runoncex.cmd can any one tell me what is the parameter of that

0

Share this post


Link to post
Share on other sites

The switches for NOD32 changed from version 2 to version 3.

I asume that this should work:

msiexec.exe /i "%WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi" /qb! ADMINCFG=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml

Here is the RunOnceEX commands I use.

REG ADD %KEY%\100 /VE /D "ESET NOD32 Smart Security 3.0.621" /f

REG ADD %KEY%\100 /V 2 /D "%systemdrive%\install\ESET\ess_nt32_enu.msi /qb! REBOOT=ReallySuppress ADMINCFG=%systemdrive%\Install\ESET\gbmNOD32v3settings.xml" /f

Parameters for ESET Smart Security and ESET NOD32 Antivirus should be typed after the name of the MSI

installation package (e.g. ea_nt64_ENU.msi /qn):

• /qn

Quiet installation mode – no dialog windows are displayed.

• /qb!

No user intervention is possible, but the process of installation is indicated by a progress bar.

• REBOOT="ReallySuppress"

Suppresses restart after the installation of the program.

• REBOOT="Force"

Automatically reboots after the installation.

• REBOOTPROMPT =""

After the 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 the installation, parameters defined in the specified XML files are applied for the client solutions ESET. The parameter is not required for remote installation. Installation packages contain their own XML conigurations, which are applied automatically.

Insert the desired XML configuration created in the ESET Configuration Editor and named cfg.xml to the directory where the downloaded installer is located. If you run the installer, it will automatically adopt configuration from cfg.xml. In case the XML configuration file has a different name, or it is located somewhere else, the parameter ADMINCFG=”path_to_xml_file”can be used. (for example ess_nt32_enu.msi ADMINCFG=”\\server\xml\settings.xml” to apply configuration stored on a network drive).
0

Share this post


Link to post
Share on other sites

msiexec.exe /i %AppsRoot%\Install\WPI\install\NOD32\nod32.3.0.msi /qn

taskkill /IM egui.exe /F

Works fine

0

Share this post


Link to post
Share on other sites

thanks everyone, I finally got it working, the tested syntax is this:

msiexec.exe /i %WPIPATH%\Install\NOD32_3.0.621\eavbe_nt32_enu_30621.msi /qb! REBOOT="ReallySuppress" ADMINCFG=%WPIPATH%\Install\NOD32_3.0.621\gbmNOD32v3settings.xml

thanks again

0

Share this post


Link to post
Share on other sites

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

THAAAAANNNNNKKKKKKKKK YOOOOOOOOOOOOUUUUUUUUUUUUUUUUUU HELO!

0

Share this post


Link to post
Share on other sites

you dont need admincfg=<path to xml> if your xml is called cfg.xml and resides in the same dir as the installer.

0

Share this post


Link to post
Share on other sites

Um, and what would be the layout of such an XML file? Can't seem to find it anywhere :s

0

Share this post


Link to post
Share on other sites
Um, and what would be the layout of such an XML file? Can't seem to find it anywhere :s
With NOD32 installed and everything in place just go to setup and export settings in cfg.xml.
0

Share this post


Link to post
Share on other sites

Regarding custom silent installation of Nod32, is it possible to install it silently with all the up to date virus definition files? I tried this some time ago, by extracting the msi and copying the updated *.nup files to APPDATADIR\Updfiles, but it failed to install the signature database.

0

Share this post


Link to post
Share on other sites

how do you guys create your .xml? i've tried using /admincfg="%somepath%"

the settings dont seem to be read

0

Share this post


Link to post
Share on other sites

how do you guys create your .xml? i've tried using /admincfg="%somepath%"

the settings dont seem to be read

I know that post has been written a while ago but I think it could be useful to give some more information on that.

When you installed a NOD32 with all the setup you need, you can go into it's console and extract the configs into a file (XML file).

We use that to deploy NOD32 on all our customers PCs. So we are packaging the MSI file with the XML file into a Wise Installation package and we deploy at large with all the same setups.

So the string to use to call the installation silent is nod32.msi /qn REBOOT="ReallySuppress" ADMINCFG="%xmlfile.xml%"

(you replace %xmlfile.xml% with the complete path of the XML file or simply the file name if it's in the same folder as the MSI file).

That's it!

0

Share this post


Link to post
Share on other sites

haiiiiiiiiiiiiiiiiiiiiiiiii

about nod32 v4 silant instal with config.xml

What code I used from this:

RunProgram="setup.msi /qn /norestart /cfg=\"%%T\\config.xml"

RunProgram="setup.msi /qn /cfg=config.xml"

RunProgram="setup.msi /qn /REBOOT="ReallySuppress" ADMINCFG="%xmlfile.xml%"

RunProgram="setup.msi /qn /config .\STANDARDR.WW\config.xml"

0

Share this post


Link to post
Share on other sites

hello i have a silent installer of nod32 and i want also to put the xml settings file how can i do it?

Edited by dimitris77
0

Share this post


Link to post
Share on other sites

ECHO OFF
cls
ECHO instalacja NOD32
ECHO.
:CheckOS
IF EXIST "%PROGRAMFILES(X86)%" (GOTO 64BIT) ELSE (GOTO 32BIT)
:64BIT
echo 64-bit...
"\\install$\nod32\klient\eea_nt64_plk.msi" /passive REBOOT="ReallySuppress" ADMINCFG="\\install$\nod32\licencja\2014_by_KC.xml"
GOTO END
:32BIT
echo 32-bit...
"\\install$\nod32\klient\eea_nt32_plk.msi" /passive REBOOT="ReallySuppress" ADMINCFG="\\install$\nod32\licencja\2014_by_KC.xml"
GOTO END
:END

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.