Jump to content

NBPC

Members
  • Posts

    18
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by NBPC

  1. @Marcos

    Final verified working unattended command is below:

    eav_nt64.exe --silent --accepteula --msi-property PRODUCTTYPE=eav PRODUCT_LANG=1033 PRODUCT_LANG_CODE=en-US ADMINCFG="Config.xml"

     

    One final tweak that I am looking for - Is there command line switch to enable / accept the Live Grid during install?

  2. Finally have it working in full now!!!!

    eav_nt64.exe --silent --accepteula --msi-property PRODUCTTYPE=eav PRODUCT_LANG=1033 PRODUCT_LANG_CODE=en-US ADMINCFG="Config.xml"

    EDIT: >>> Another glitch was found where the everything installed correctly but product license key would not activate - the PRODUCT_LANG_CODE=us-US  should be  en-US

    With this correction it is working 100% unattended

    My final install package is as follows:

    Make a folder with any name on any drive or folder.
    Download the latest eav_64.exe and eav_32.exe and place that in the created folder
    Export the config from EAV that has the settings you prefer and put that in the created folder as well
    Create a CMD (mine is ESET_GO.CMD) and copy script below. (Be sure to match the exe and config names)

    This will launch from any drive or location - old dos trick >>>  %~dp0

    @Color 0a
    @ECHO OFF
    :: Asks for admin privileges
    :-----------------------------------------------------------------------------------------------------------------------------------------------------------
    REM  --> Check for permissions
    >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"
    REM --> If error flag set, we do not have admin.
    if '%errorlevel%' NEQ '0' (
        echo Requesting administrative privileges...
        goto UACPrompt
    ) else ( goto gotAdmin )
    :UACPrompt
        echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs"
        set params = %*:"=""
        echo UAC.ShellExecute "%~s0", "%params%", "", "runas", 1 >> "%temp%\getadmin.vbs"
        "%temp%\getadmin.vbs"
        exit /B
    :gotAdmin
        if exist "%temp%\getadmin.vbs" ( del "%temp%\getadmin.vbs" )
        pushd "%CD%"
        CD /D "%~dp0"
    :-----------------------------------------------------------------------------------------------------------------------------------------------------------
    ECHO     Silently installs Eset AntiVirus and preconfigures settings . . . Please wait . . . 

    IF EXIST "%PROGRAMFILES(X86)%" (GOTO 64BIT) ELSE (GOTO 32BIT)
    :32BIT
    %~dp0\eav_nt32.exe --silent --accepteula --msi-property PRODUCTTYPE=eav PRODUCT_LANG=1033 PRODUCT_LANG_CODE=en-US ADMINCFG="%~dp0\Configx86.xml"
    GOTO END
    :64BIT
    %~dp0\eav_nt64.exe --silent --accepteula --msi-property PRODUCTTYPE=eav PRODUCT_LANG=1033 PRODUCT_LANG_CODE=en-US ADMINCFG="%~dp0\Config.xml"
    GOTO END
    :END

     

  3. Ran some tests and it looks like ALL MSI values need passed using -- msi-property switch or the config does not get applied.

    When I was testing I did not try a product key since the goal was looking to see if the settings took the Config.xml 

    Using PRODUCTTYPE=140 is telling the EXE it is Internet Security - you get the Banking and ?? shortcut and at the license screen it says ESET Internet Security

    The product key (for EAV) gets rejected with an error which was the alert to the problem

    @Marcos - Can you verify proper PRODUCTTYPE code? In the registry I see a ProductAType code of 106 on an EAV install

    is that the value that is being passed?

  4. OK there may be a glitch yet - The Install shows up as ESET Internet security instead of ESET Security - an EAV product key is not accepted.

    @Marcos - I need to verify ProductType=140 is indeed NOD32 Antivirus

    I will try again on a clean install to double check and report back the results :blink:

     

  5. Thanks to Marcos we have a working script to install and preconfigure :D

    Quote
    Marcos said:

    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“

    or

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

    This works for EAV so if you would like to install EIS or ESSPand the first method didn't work, let me know and I'll find out the code for other product types as well.

     

    This first one silent installs but still did not pass the config settings during install

    The second one was a success!!

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

    Many thanks to everyone for their input

    @Marcos  Is it possible to get the product code list for the other security products???

    :D:rolleyes::)

    My final install package is as follows:

    Make a folder with any name on any drive or folder.
    Download the latest eav_64.exe and eav_32.exe and place that in the created folder
    Export the config from EAV that has the settings you prefer and put that in the created folder as well
    Create a CMD (mine is ESET_GO.CMD) and copy script below. (Be sure to match the exe and config names)

    This will launch from any drive or location - old dos trick >>>  %~dp0

    @Color 0a
    @ECHO OFF
    :: Asks for admin privileges
    :-----------------------------------------------------------------------------------------------------------------------------------------------------------
    REM  --> Check for permissions
    >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"
    REM --> If error flag set, we do not have admin.
    if '%errorlevel%' NEQ '0' (
        echo Requesting administrative privileges...
        goto UACPrompt
    ) else ( goto gotAdmin )
    :UACPrompt
        echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs"
        set params = %*:"=""
        echo UAC.ShellExecute "%~s0", "%params%", "", "runas", 1 >> "%temp%\getadmin.vbs"
        "%temp%\getadmin.vbs"
        exit /B
    :gotAdmin
        if exist "%temp%\getadmin.vbs" ( del "%temp%\getadmin.vbs" )
        pushd "%CD%"
        CD /D "%~dp0"
    :-----------------------------------------------------------------------------------------------------------------------------------------------------------
    ECHO     Silently installs Eset AntiVirus and preconfigures settings . . . Please wait . . . 

    IF EXIST "%PROGRAMFILES(X86)%" (GOTO 64BIT) ELSE (GOTO 32BIT)
    :32BIT
    %~dp0\eav_nt32.exe --silent --accepteula --msi-property PRODUCTTYPE=140 PRODUCT_LANG=1033 PRODUCT_LANG_CODE=us-US ADMINCFG="%~dp0\Configx86.xml"
    GOTO END
    :64BIT
    %~dp0\eav_nt64.exe --silent --accepteula --msi-property PRODUCTTYPE=140 PRODUCT_LANG=1033 PRODUCT_LANG_CODE=us-US ADMINCFG="%~dp0\Config.xml"
    GOTO END
    :END
     
    • 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
  6. 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:

  7. 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

  8. Trying to get Nod32 Antivirus to install in a truly unattended method used to be done by downloading the MSI and install via a script.

    The new version 11.x versions failed due to the new EXE version and new installer parameters being passed.

    As per ESET the MSI install method is a rejected method and wants the ESET home products install using the EXE 

    After some juggling and information requests the script to silently install using the EXE file is given below

    This is for Nod32 Antivirus 64bit -

    eav_nt64.exe --silent --accepteula --language 1033 --msi-property-ehs PRODUCTTYPE=eav --msi-property ADMINCFG="path-to\Config.xml"

    The EXE method works well except the option --msi-property ADMINCFG="path-to\Config.xml" does not apply the settings

    During the MSI install the option /ADMINCFG="path-to\config.xml" worked perfectly. (and still does if the MSI is extracted from the EXE)

    Without the ability to apply the settings during install, this is not an unattended method

    The old MSI method requires extracting the MSI from the EXE and now requires a registry entry to be injected prior to install or it fails, It is an easy fix to make the MSI method work but ESET wants the EXE method used.

    I have tried different locations installation and the Config.xml to assure permissions where not an issue.

    I am looking for any help or information or ideas to apply the ADMINCFG option

    The new version 11.x looks like they are using Advanced Installer to build the package. Hoping someone may know a trick to pass the MSI switch through the EXE options

     

  9. @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!

  10. 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

     

  11. 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!

  12. This is very frustrating - I feel as though I am missing something obvious but still no joy

    I am trying to break down the problem to its simplest level till it works them move up from there but still cannot get it to go

    I am not even worrying about the admin config right now since I cannot get an install without all the usual prompts

    Here is were I am at right now.

    downloaded newest eav_nt64.exe (11.159) and dropped in into windows temp

    with a elevated command prompt open and in the windows temp folder I type

    eav_nt64.exe --silent --accepteula --language 1033 - US English is 1033

    From same folder I typed the full absolute path C:\Windows\Temp\eav_nt64.exe --silent --accepteula --language 1033

    Still no joy - the installer starts to run, creates the eset security folder and the eula bits and pieces then just quits

    I though there may be a permission issue going on with windows temp folder so I did try a first users profile download folder to verify it is not an issue like that - still no joy

    I also want to verify the -- double dash is not being converted with language controls here - I have never seen double dashes - single dash and forward slash yes but not double dash.  Just want to verify this

    Still looking for answers

  13. I to have tested this method as stated directly from Marcos

    eav_nt64.exe --silent --accepteula --language 1034 --msi-property  ADMINCFG="%path_to_the_cfg_xml%"

    current version 11.159 is now named EAV_NT64.exe again

    I have the exact same behavior as COCH with the process starting but only the eset security folder and the eula bits and pieces 

    Back to working MSI install methods again

    Hopeful but yet another fail :( -  OEM builders need automation to be truly unattended installs and configuration  

     

  14. @ Marcos

    You are offering the switches for unattended installs using the EXE file but you have not responded to "coch's" question - Is there a switch to incorporate the preconfigured settings, similar to the /ADMINCFG=cfg.xml using the EXE method you posted.

    Without the ability to preload settings the silent install I'm my case is of little value.

    For me, the whole point is to script a preconfigured package that leaves the end user the ability to enter a license key or begin a trial with all recommended settings preset at first login

    The MSI method does this. The MSI is extracted, not hacked, and ESET will uninstall or repair cleanly and without errors.

    The method to achieve this can be EXE or MSI - we just need ALL the switches to be documented or posted if ESET prefers the EXE method as they did the MSI methods years ago

    OR > If ESET would build an OEM installer with the ability to add a "Provided by %companyname%" and a small graphic spot for a company logo (Similar to Microsoft OEM) - That would be fantastic!!!  

     

  15. I tried to use the switches suggested by Marcos on the exe and on the msi just to be sure.

    There was no effect on the exe and the msi just threw up the options windows for msiexec.

    Here is a work around that works well for my needs - use this at your own risk

    Create a registry file to inject the values needed BEFORE using the msi install method.

    This was created using a sample exe installation in normal interactive mode,  and exporting HKLM\\Software\ESET\ESET Security\CurrentVersion\Info

    It took a little testing to trim down the keys to the bare minimum that had to be in place to allow the install to work silently and without error.

    One value of concern was the "ProductVersion"="xx.xx.xx" but I found this was not needed so this should work thru the 11.xx versions - 

    Here is the final registry key. I named mine "eavsilent.reg", adjust to your file naming methods accordingly. 

    ------------------------------------------------------------------------------------------------------------------------------------
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info]
    "ProductACode"=dword:0000006a
    "ProductACodeStr"="com.eset.apps.home.security.windows"
    "ProductBase"=dword:00000000
    "ProductType"="eav"
    "ProductName"="ESET NOD32 Antivirus"
    ------------------------------------------------------------------------------------------------------------------------------------
    So now the heart of the final working script is like this

    ::Installing Eset AntiVirus
    reg import %your_path%\eavsilent.reg
    msiexec.exe /i %your_path%\ehs_nt64_enu.msi /qb! REBOOT="ReallySuppress" ADMINCFG="%your_path%\Config.xml"

    Perhaps one day ESET will supply the OEM markets (hopefully with a "Provided by" branding insert) with a supported solution for the partner deployments

  16. I to am having the issue with installing Version 11 Nod32 in unattended mode.

    As a system builder we use ESET exclusively. Systems are prepped for shipment with a logon script that installs the apps into the end user profile at first login. The last being the ESET ready to accept the license key or start a trial

    We have used the script method below for years, though in the last 4-5(??) years we had to grab the MSI from the temp folder after the MSI files were no longer downloadable.

    ::Installing Eset AntiVirus
    msiexec.exe /i %windir%\Factory\Apps\ESET\ehs_nt64_enu.msi /qb! REBOOT="ReallySuppress" ADMINCFG="%windir%\Factory\Apps\ESET\Config.xml"

    Starting with version 11 the following error occurs

    Could not write value ProductACode to key \Software\ESET\ESET Security\CurrentVersion\Info.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.

    To test, installing from the EXE in interactive mode does not cause the issue and installs without an error.

    So I'm guessing a value needs passed with the msiexec command but not sure at this point what that is.

    ESET has never provided an OEM method of installing and though I have spoken to sales team about this I have always had to come up with a scripting method. It would be great to be provided official OEM preinstall tools but will definitely settle for the value that needs passed with the MSI install

    Any input form admins or users that have worked this out would be greatly appreciated and I will look into method proposed by "Coch" 

     

×
×
  • Create New...