Nod32 Enterprise - Configuration variables?

[xija07]

Hi there I am currently involved with supporting over 100 client/server networks which we are trying to migrate to NOD32 EE, but I have a quick question:

Because they are all different servers and domains, what is the easiest way to take the same configuration away to different networks? For e.g, can I use dos variables like %LogonServer% or others to make rolling out new installations easier and save me changing configurations every time? I would need to use %LogonServer% for the update LAN server details and console reporting.

Cheers!

[anotherjack]

{QUOTE-> Hi there I am currently involved with supporting over 100 client/server networks which we are trying to migrate to NOD32 EE, but I have a quick question:

Because they are all different servers and domains, what is the easiest way to take the same configuration away to different networks? For e.g, can I use dos variables like %LogonServer% or others to make rolling out new installations easier and save me changing configurations every time? I would need to use %LogonServer% for the update LAN server details and console reporting.

Cheers! <-QUOTE}

Create an XML file for each of the installation locations, then install NOD with a batch file like so:

setup.exe /silentmode /instmft /cfg=path_and_filename_to_your_XML

That's how we did it for our 20+ different sites. They all have their own local mirror server and we needed to point that site's clients to their own server. The only difference between the various XML files was the definition of the mirror server.

HTH

[xija07]

Yeah I see what your saying, but that kinda defeats the object of what i'm trying to do...

I'm trying to create one XML to use throughout different server/domains, so creating a different XML for each domain (which would mean creating over 120 XML's!) would be what I'm doing now.

But thanks for trying to help, much appreciated.