PRJUS
December 2nd, 2007, 10:55 AM
In version 2.7 you could unpack the installer and inject your own XML configuration file and get a configured NOD32 without having to use the nod32installer.exe (now einstaller.exe).
This was very usefull in situations where you had clients that never or almost never came online with your Remote Administrator server.
In version 3.0 we have an MSI-file (which by itself is a good thing) but I can't find a way to tell the installer to take a preconfigured XML-file and use that so I can send an installation script to users that are offline.
I have looked into the MSI-file but can't find any properties that would allow this.
As far as I can see the only option is a manual installation and manual configuration giving the end users the userid/password for the update site and locking down the configuration would also be useless.
Is there a way to do this?
Kind regards
Preben Justesen
This was very usefull in situations where you had clients that never or almost never came online with your Remote Administrator server.
In version 3.0 we have an MSI-file (which by itself is a good thing) but I can't find a way to tell the installer to take a preconfigured XML-file and use that so I can send an installation script to users that are offline.
I have looked into the MSI-file but can't find any properties that would allow this.
As far as I can see the only option is a manual installation and manual configuration giving the end users the userid/password for the update site and locking down the configuration would also be useless.
Is there a way to do this?
Kind regards
Preben Justesen