Exported Settings (XML file)

Discussion in 'ESET Smart Security' started by Stoner81, May 5, 2009.

Thread Status:
Not open for further replies.
  1. Stoner81

    Stoner81 Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    30
    Howdy folks its been a while!

    Anyway I have now upgraded to v4.0.424.0 (latest version) and I have set all the settings how I want and exported them a XML file.

    Now my question is thus, is there any way to use this file (XML) during initial install? I want to build this installer so then if I need to wipe or whatever then I can simply run it and it will have all the settings I need.

    Sorry if this is already posted elsewhere but I could not find it :(

    Stoner81.
     
  2. Najem1992

    Najem1992 Registered Member

    Joined:
    May 2, 2009
    Posts:
    53
    Location:
    In The Heart Of Eset
    hi
    to export a settings file do the following :
    1- press Ctrl + M in the keyboard
    2-from the main menu click on " setup "
    3- choose " Import\export settings... "
    4- a new window will open , tick " export settings "
    5- click on the " ... " button to choose where to save the file
    6- click ok

    to import a settings file do the following :
    1- press Ctrl + M in the keyboard
    2-from the main menu click on " setup "
    3- choose " Import\export settings... "
    4- a new window will open , tick " import settings "
    5- click on the " ... " button to choose the settings file
    6- click ok

    about how to import settings during install
    I don't know about that
    but hope I helped you
     
  3. Stoner81

    Stoner81 Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    30
    Not quite there m8 but thanks for trying, what you describe I have already done its just the initial install part Im really after.

    I really appreciate your time and effort though.

    Thank you.

    Stoner81.
     
  4. Bubba

    Bubba Updates Team

    Joined:
    Apr 15, 2002
    Posts:
    11,271
    I can not speak about an ESS install, but for an EAV install, one names their XML file cfg.xml and places it in the same folder where the msi package resides\runs from.

    Bubba
     
  5. Najem1992

    Najem1992 Registered Member

    Joined:
    May 2, 2009
    Posts:
    53
    Location:
    In The Heart Of Eset
    thanks mate
    but the question is would it work with ESS ?
     
  6. Stoner81

    Stoner81 Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    30
    Thanks guys, I have found out that the switch to use could be ADMINCFG=[xxxx].xml

    would this work?

    @ Bubba - hey dude will EAV just auto call the xml file during install or does it need calling manually via a switch or something?
     
  7. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    Yes the configuration will be automatically applied if the .xml file is in the same folder as the installer (ess_nt32_enu.msi). I belive it HAS to be called cfg.xml.
    The admincfg switch is only when the configuration is in another location or has another name (eg; ess_nt32_enu.msi ADMINCFG =””\\server\share\settings.xml”). To have it all unattended you may want to add ' /qn REBOOT="ReallySuppress" '
     
  8. Stoner81

    Stoner81 Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    30
    Thanks for you help there on this! Very much appreciated indeed... now I have used the ADMINCFG=config.xml but it didnt import the settings i have built a WinRAR SFX archive which calls the msi file to run in silent using msiexec /i "setup.msi" /qb (not sure on the last switch without looking lol) ADMINCFG=config.xml and it didnt import the settings.

    Is this because I have renamed files or named them wrong?

    Thanks for any and all help folks!

    Stoner81.

    EDIT - I have tried naming it cfg.xml and left the installer with the standard name but still it will not use the settings I want :(
     
    Last edited: May 31, 2009
  9. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    I never used it with a selfextracting RAR file. My guess is the installer cant find the XML cause its first being unpacked in a temporary folder. You can try to point the ADMINCFG switch to that place.
     
    Last edited: May 31, 2009
  10. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    Hey,

    Cause I was a little interested in making a own self-extracting file I did a little 'research' on how to do so. Here is what I did:

    I have found out how to make your own executable (.exe) with the help of 7zip (www.7zip.org). You can make your own installer for, for example ESET software with non-default parameters to make it all unattended (and to import a xml file).

    To do this with the EAV installer you have to do the following steps:


    - Place both the ESET installer (eg. eavbe_nt32_enu.msi) and the optional xml (cfg.xml) in a .7z compressed file. I named it esetinstaller.7z

    Note: This is a 'normal' compressed 7z file. I guess you can make it with other programs who can compress files as .7z also, but I did not test this. I used 7zip for this.


    - Open a text editor (notepad) and save the following information as config.txt (save as UTF-9 format!!). Save this file in the same directory as the 'esetinstaller.7z' file.
    Code:
    ;!@Install@!UTF-8!
    Title="ESET Installer"
    Progress="No"
    ExecuteFile="msiexec.exe"
    ExecuteParameters="/i eavbe_nt32_enu.msi /qn"
    ;!@InstallEnd@!
    
    Note: This will install EAV silently and unattended (no dialog windows are displayed). Use '/qb!' instead of '/qn' to show a progress bar only.
    The 'Progress' options is whether or not you want to see the unpacking progress of the files inside the compressed folder.


    - Download and copy 7zS.sfx (http://ovh.dl.sourceforge.net/sourceforge/sevenzip/7z465_extra.7z - it contains 7zS.sfx among other files.) in the same directory.


    Now you should have at-least these 3 files in your directory ;
    - esetinstaller.7z
    - settings.txt
    - 7zS.sfx


    - Open this directory in a command line prompt and use the following command to make your own installer:
    Code:
    copy /b 7zS.sfx + config.txt + esetinstaller.7z esetinstaller.exe
    

    ..and your done!

    Now you should have a 'esetinstaller.exe' in that same directory. In above example you should not notice anything until the ESET splash-screen pop-ups after installation. (This is what I like in my environment)

    I tested this with cfg.xml in the compressed 7z file and it also imported my settings without using the admincfg parameter.

    Perhaps you can do something with this information.
     
  11. Stoner81

    Stoner81 Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    30
    WOW!!! amazing reply buddy thanks a million will defo be trying this out I just hope it works with ESS!
     
  12. Stoner81

    Stoner81 Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    30
    I have made this now using EAV just to test it out thanks for the help!
     
  13. Stoner81

    Stoner81 Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    30
    Ok I have tested this and I think it has worked after a fashion. All the cleaning options etc are set but it still shows the splash screen at startup even though in the options file (xml) it is disabled?? Very strange but overall it seems to have worked for the most part.

    Thanks for everybodys help much appreciated!

    Stoner81.
     
  14. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    Well the time I used this to test it out the config file, it was imported correctly. Perhaps the xml file wasn't good. Try making a export from a current running configuration and use that xml file instead (If you didn't do it like that already). Else you might be looking at a bug, but the import from the self extracting exe should work.
     
Thread Status:
Not open for further replies.