Install new NOD32 with XML file not working

Discussion in 'ESET NOD32 Antivirus' started by phil2627, Aug 3, 2010.

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

    phil2627 Registered Member

    Joined:
    Sep 26, 2008
    Posts:
    2
    We are trying to package the new 4.0.58 NOD32 client and are custom config file to deploy through Appdeploy. We were able to use a file of 090910.xml before with 4.042. However, when deploying with the newer NOD32 client does not appear to work. Is there a naming format such as config.xml in order for this to work ? Thanks.
     
  2. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    If you want the configuration file to be automaticly picked up by the installer it should be named 'cfg.xml'. Otherwise you have to use the "admincfg=pathtoconfigfile" parameter, see ERA manual for more details.
     
  3. phil2627

    phil2627 Registered Member

    Joined:
    Sep 26, 2008
    Posts:
    2
    Brambb,

    Thanks. Worked like a charm. I appreciate the knowledge.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.