Wilders Security Forums  

Go Back   Wilders Security Forums > Archived Forums > Closed Sub-Forums > Archived ESET Support Forums > NOD32 version 2 Forum
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
 
Thread Tools Search this Thread
  #1  
Old June 20th, 2007, 08:04 AM
Megachip Megachip is offline
Frequent Poster
 
Join Date: Dec 2006
Posts: 243
Default nod32umc 2.50.6 vs.2.70.6

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  
Old June 20th, 2007, 08:40 AM
Marcos Marcos is offline
Eset Moderator
 
Join Date: Nov 2002
Posts: 14,193
Default Re: nod32umc 2.50.6 vs.2.70.6

v. 2.7 supports automatic server selection
  #3  
Old June 21st, 2007, 06:36 AM
Megachip Megachip is offline
Frequent Poster
 
Join Date: Dec 2006
Posts: 243
Default Re: nod32umc 2.50.6 vs.2.70.6

what about official support for client configuration files like in the windows version
  #4  
Old June 21st, 2007, 09:01 AM
Marcos Marcos is offline
Eset Moderator
 
Join Date: Nov 2002
Posts: 14,193
Default Re: nod32umc 2.50.6 vs.2.70.6

Quote:
Originally Posted by Megachip
what about official support for client configuration files like in the windows version

RA serves for configuring clients remotely.
  #5  
Old June 21st, 2007, 09:57 AM
Megachip Megachip is offline
Frequent Poster
 
Join Date: Dec 2006
Posts: 243
Default Re: nod32umc 2.50.6 vs.2.70.6

Quote:
Originally Posted by Marcos
RA serves for configuring clients remotely.

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  
Old June 21st, 2007, 05:59 PM
Marcos Marcos is offline
Eset Moderator
 
Join Date: Nov 2002
Posts: 14,193
Default Re: nod32umc 2.50.6 vs.2.70.6

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  
Old June 22nd, 2007, 05:48 AM
Megachip Megachip is offline
Frequent Poster
 
Join Date: Dec 2006
Posts: 243
Default Re: nod32umc 2.50.6 vs.2.70.6

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
 

Wilders Security Forums > Archived Forums > Closed Sub-Forums > Archived ESET Support Forums > NOD32 version 2 Forum « Previous Thread | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -4. The time now is 04:10 PM.


Powered by vBulletin® Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums