network Deploy

Discussion in 'NOD32 version 2 Forum' started by Josh, Oct 21, 2003.

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

    Josh Guest

    In NOD32 Version 1, there was away to deploy the software silently over a network.
    Is there a way to do this in version two?? I am unable to find it.
    Any help would be greatly appreciated.
    thanx
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hello,
    this will be possible by means of the new RA console available soon. Presently, ESET can provide you a special deploy utility (like Netdeploy for NOD32 v1) which serves to create installation packages with already predefined settings.
     
  3. davekempe

    davekempe Guest

    where can we get this netploy for version 2?
    the version 1 doesn't work for version 2.

    btw, after running strings on the setup.exe I found these command line switches.
    not sure what they do, but /cfg and /silentmode are pretty useful.

    /INSTMFC
    /REBOOT
    /TEST
    /UPDATE
    /FORCEOLD
    /UNINSTALL
    /SILENTMODE
    /AUTHSERVER=
    /PWD=
    /NUP=
    /SETTINGS=
    /CFG=

    does anyone know that /test /forceold /authserver /pwd /nup and /settings does?
    /cfg and /silentmode and /reboot all seem to work.
    we (josh and I) created a config file that seemed to give us the desired result.
    Basically, all we need is the setup to run silently, and point itself at the mirror.
    It still errors out and says there is no default client - can we suppress that error?


    this is the contents of the setup.xml file.
    we got this from cutting out the relevant bit of a working config file and sticking it in the existing config file. We got the location on the second guess.
    <?xml version="1.0"?>
    <NOD32GLOBALSETUP>
    <DISPLAY TITLE="NOD32 for Windows NT/2000/XP" />
    <SETUP REQUIRED_OS="NT" INSTALLPATH="%PROGRAMFILES%\Eset" DAT_CNT="0" />
    <COMPONENTS>
    <COMPONENT ARCHIVE="ntbaseen.nup" />
    <COMPONENT ARCHIVE="ntstden.nup" />
    <COMPONENT ARCHIVE="ntineten.nup" />
    </COMPONENTS>
    <ENGINES>
    <ENGINE FILE="engine.nup" />
    <ENGINE FILE="advheur.nup" />
    <ENGINE FILE="archs.nup" />
    </ENGINES>
    <SETUPINFO>
    <SETTINGS TIMESTAMP="1" ID="484F4BA9">
    <PLUGIN ID="31647055">
    <DATA>
    <NODE NAME="Config000" TYPE="SUBNODE">
    <NODE NAME="PROFILE_NAME" TYPE="STRING" VALUE="My Profile" />
    <NODE NAME="Settings" TYPE="SUBNODE">
    <NODE NAME="SelectedServer" TYPE="STRING" VALUE="http://192.168.0.1:8081/" />
    </NODE>
    </NODE>
    </DATA>
    </PLUGIN>
    </SETTINGS>
    </SETUPINFO>
    </NOD32GLOBALSETUP>


    Now using the above config file and the switches I discovered, we can probably do the deployment of nod32 throughout some networks we have (around 50PCs each).
    I wouldn't mind a netploy app to make it easier and some doco on the installer might be nice too.
    also a way to suppress the MAPI error would be good - I know it doesn't happen on every client, but it kinda makes it not silent anymore if the people have to click ok.

    thanks

    dave
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hi Dave,

    please contact Eset at support@nod32.com to obtain the desired utility.
     
Thread Status:
Not open for further replies.