coch

V11 .msi silent install fails

Recommended Posts

Any input from admins or others?

Unfortunately trying to replicate Proactive Services method did not produce same results here. @Proactive ServicesAre your install consistently successful?

There should not be any issues between 1034 and 1033 language settings

The exe method would be much easier to keep OEM installs current

If we can get a working command going then just drop in latest exe edition and unattended installs would be golden 

I will keep trying the exe steps to see if I can stumble on the issue but in the meantime the old MSI method combined with a prepopulated registry setting is working well

Any input, suggestions or speculations are very welcomed - We don't learn unless we struggle!

Share this post


Link to post
Share on other sites

Try running the bootstrapped installer with the following syntax:
EIS:
--silent --accepteula --language 1033 --msi-property-ehs PRODUCTTYPE=eis

EAV:
--silent --accepteula --language 1033 --msi-property-ehs PRODUCTTYPE=eav

Optional parameter:
--msi-property  ADMINCFG="%path_to_the_cfg_xml%"

Edited by Marcos
typo fixed

Share this post


Link to post
Share on other sites

Thanks Marcos, I confirm it works now, with a slight modification to your above instructions:

-silent should be --silent

(you had double dashes everywhere except for the first argument silent and I found it didn't work with a single dash, you really need two dashes everywhere)

I also found that the % are not required in the path_to_the_cfg_xml

 

Here's the command that I used, with correction made, and it was successful in a complete silent install of NOD32 using the .exe:

eav_nt64.exe --silent --accepteula --language 1033 --msi-property-ehs PRODUCTTYPE=eav --msi-property ADMINCFG="D:\Reformat\Programs\NOD32-v11-Config.xml"

Replace whatever's between the quotes after ADMINCFG= with the actual path to your own config file.

Edited by coch

Share this post


Link to post
Share on other sites

Sorry, it is not 100% working unfortunately, despite my post just above.

The settings from the cfg.xml file are not applied. Quotes or no quotes. Percent sign or no percent sign. ESET installs with the default settings regardless of having specified --msi-property ADMINCFG=

 

 

Share this post


Link to post
Share on other sites

Just prior to the new information from @Marcos I was fooling around with the EXE silent steps and had the explorer open, seen the ESET folders created and started drilling down into the folder structure will it was installing. While doing this, the folders and files disappeared and was left with the eula bits.

suspicious of this behavior I preloaded the registry keys needed as I did for the MSI install and the silent exe method completed correctly, this indicated the need for the productacode , producttype and other registry strings needed.

When @Marcos submitted the new information with the new PRODUCTTYPE=eav added it looked hopeful the issue was getting narrowed down.

Putting the latest information into play this indeed is a working EXE silent install method

On ‎1‎/‎25‎/‎2018 at 5:18 AM, Marcos said:

EAV:
--silent --accepteula --language 1033 --msi-property-ehs PRODUCTTYPE=eav

Optional parameter:
--msi-property  ADMINCFG="%path_to_the_cfg_xml%"

I  now get an unattended and silent install with the EXE but I too have not been able to get the config.xml to apply

SOOOO Close

@Marcos hoping you can shed some light on this last little tidbit

 

Share this post


Link to post
Share on other sites

@Marcos Any word as to why the  --msi-property ADMINCFG="config.xml"  is not applying?

The prior unattended install steps work perfectly now but the config.xml still will not apply.

I have tried relative path to execution folder, absolute path and every variation I can muster with zero results.

I see the EXE boot strapper  appears to be written with Advanced Installer - are the MSI properties for the ADMINCFG option written into the Installer?

Something is up there with that property - Can you verify the optional command string to pass the ADMINCFG="config.xml" argument to the boot strapper?

You got us all this close to having the new EXE unattended method working - Don't give up on us now:)

The EXE method would ultimately be easier to keep the most up to date version installed

Make the folder and script and just drop in the latest exe version -- DONE!

Edited by NBPC

Share this post


Link to post
Share on other sites

as a possible solution i tried to import a config with 

ecmd /setcfg c:\config\settings.xml

which is documented here: https://support.eset.com/kb6382/

this also fails, maybe the import function is broken in eset 11?

Share this post


Link to post
Share on other sites
On 3/3/2018 at 5:02 PM, Allow said:

as a possible solution i tried to import a config with 

ecmd /setcfg c:\config\settings.xml

which is documented here: https://support.eset.com/kb6382/

this also fails, maybe the import function is broken in eset 11?

You have posted in a consumer product forum. This feature is available only in ESET Endpoint.

Share this post


Link to post
Share on other sites

I am still looking for the solution to the unattended setting import but I really appreciate the offerings - something new to try - all other solutions thus far have failed

@Marcos any solutions to this issue from the development team?? I suspect the option may not be rolled into the new Advanced Installer package. Only development team would be able to verify this.

Overall the unattended EXE install is much easier to keep latest edition in the new builds but have to take a step to assure settings are preset  

Hopefully this last issue will get resolved soon

Thank you for your input

Share this post


Link to post
Share on other sites

I agree. Installing silently with configuration is really useful to me, and if I didn't have the .msi workaround ESET would be the only software out of my approximately 15-20 software of all types that I install silently via my batch file every time I reformat and reinstall Windows (and I'm not even counting drivers which I also install silently).

For most software there is a way to achieve this, i.e. whether silent install or direct copy of the installed software under "Program Files", along with direct configuration as part of the silent install switches, copying AppData folder and/or merging registry settings.

I was unable to figure out a way to achieve this for ESET via the registry or AppData routes (I suspect it's possible though and that I just didn't dig deep enough, but this seems more complex than I'm used to).

Share this post


Link to post
Share on other sites

This issue has to be a developer issue.

Either the new Advanced Installer packaging does not have that value added into the compiler(?) or the --msiproperty  value is not correctly written.

It would be nice if the moderators would get with the developer team to verify or post the equivalent of the MSI installers version of  /ADMINCFG="config.xml"

Sooo close

I keep hoping and poking around trying to "trip" over it :unsure::wacko::blink:

Share this post


Link to post
Share on other sites
  • Group: Members
  • Posts: 12
  • Kudos: 1
  • Joined: November 19, 2017
  •  
  • Location: USA
 
BUMP - still looking for answers!!! going to go back to MSI method soon. to many missed settings on new systems

@Marcos Any word as to why the  --msi-property ADMINCFG="config.xml"  is not applying?

The prior unattended install steps work perfectly now but the config.xml still will not apply.

I have tried relative path to execution folder, absolute path and every variation I can muster with zero results.

I see the EXE boot strapper  appears to be written with Advanced Installer - are the MSI properties for the ADMINCFG option written into the Installer?

Something is up there with that property - Can you verify the optional command string to pass the ADMINCFG="config.xml" argument to the boot strapper?

You got us all this close to having the new EXE unattended method working - Don't give up on us now:)

The EXE method would ultimately be easier to keep the most up to date version installed

Make the folder and script and just drop in the latest exe version -- DONE!

Edited February 9 by NBPC

Share this post


Link to post
Share on other sites

@Marcos there is documentation with all parameters to use with  eav_nt64.exe ?

Share this post


Link to post
Share on other sites

Try this syntax:

eav_nt64_ENU.exe --silent --accepteula --msi-property-ehs PRODUCTTYPE=eav --msi-property PRODUCT_LANG=1033 PRODUCT_LANG_CODE=us-US ADMINCFG=“C:\Install\cfg.xml“

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.