nod32umc 2.50.6 vs.2.70.6

Discussion in 'NOD32 version 2 Forum' started by Megachip, Jun 20, 2007.

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

    Megachip Registered Member

    Joined:
    Dec 4, 2006
    Posts:
    243
    Hello,

    I use nod32umc 2.50.6 for creating and updating an NOD32 Update Mirror...

    Is it recommend to upgrade to ver 2.70.6 ? Are there new features or bugfixes regarding the mirror creation and updating!?

    THX

    Regards, Meg
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    v. 2.7 supports automatic server selection
     
  3. Megachip

    Megachip Registered Member

    Joined:
    Dec 4, 2006
    Posts:
    243
    what about official support for client configuration files like in the windows versiono_O
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    RA serves for configuring clients remotely.
     
  5. Megachip

    Megachip Registered Member

    Joined:
    Dec 4, 2006
    Posts:
    243
    yes, but not all clients can connect RA, because of LAN/WAN/Firewall etc.

    So it would be nice to have an option to configure all theses clients, which cannot connect to RA.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    It's possible now, just add an xml file to the mirror folder and add the following to update.ver:

    [config000]
    type=config
    file=my.xml
    platform=all
    id=1374889882
    timestamp=3

    where my.xml is the xml file in the mirror folder. If you make changes to the xml file you'll need to change the timestamp both in update.ver and the xml file for the changes to take effect. ID is the decimal number of the ID from the xml file where it's stored in hexa.
     
  7. Megachip

    Megachip Registered Member

    Joined:
    Dec 4, 2006
    Posts:
    243
    thx marcos,

    i've already done it this way... (copy the entry from windows update mirror)

    the only "problem" is, that it must be added every update, because nod32umc or something else overwrite the update.ver ...

    but its not realy a problem, because update is script based
     
Thread Status:
Not open for further replies.