I’m currently looking for a new antivirus product that we are planning to use on a large number of networks (1000+). We have to manage and maintain the AV software for all of these networks. Of course we want to do our maintenance in as little time as possible.
Therefor I have the following questions:
Is it possible to unattendedly install and configure adnm?
Is it possible to update the license file using a script? I saw that the license file (license.dat) is placed in the maintenance installation folder. Perhaps it’s just a matter of replacing the license.dat file?
One of the major advantages of the Avast product is the deployment of the client packages through AD using a MSI. Can this MSI be generated using a script?
Can i create a task using a script? or can I create a task that I copy to all my servers. In that case, where are the tasks stored?
Is it possible to unattendedly install and configure adnm?
If you’re talking about the management server, than the answer is No. However, this should be a one time job, really.
In case of the managed clients (ie. the actual antivirus protection agents), then the answer is (of course) Yes.
Is it possible to update the license file using a script? I saw that the license file (license.dat) is placed in the maintenance installation folder. Perhaps it's just a matter of replacing the license.dat file?
Yes, replacing the file and restarting the avast! Management Server service is all it takes to update the license. However, again, this isn’t something you’d be doing too often (or on too many systems) to actually deserve scripting, is it?
One of the major advantages of the Avast product is the deployment of the client packages through AD using a MSI. Can this MSI be generated using a script?
No, but it can be generated using a schedule. I.e. you can have a scheduler item that regenerates the MSI file daily (with the latest data).
Can i create a task using a script? or can I create a task that I copy to all my servers. In that case, where are the tasks stored?
The tasks are stored in the SQL database. Again, you can’t create them via script, but is that really needed? The typical use case is that the tasks are created in the beginning, and then, they are only executed. Why would you need to create new tasks on regular basis (i.e. via scripts)?
So, if I understand it correctly, the number that you indicated (1000+) is not a number of machines, but really a number of different networks? And these are like networks belonging to the same organization? Or they are completely unrelated networks?
In a nutshell. At the moment we have a proven concept for primary schools in Holland. This concept runs on Windows 2003 and Windows XP.
Currently we are developing a new version of this concept. Therefor we are evaluating all the products, including virus protection, we are currently using in our concept.
We plan to launch this new version of our concept Q3 2008. After the launch we plan to migrate the existing networks to the new version.
So, if I understand it correctly, the number that you indicated (1000+) is not a number of machines, but really a number of different networks? And these are like networks belonging to the same organization? Or they are completely unrelated networks?
The 1000+ are the number of individual unrelated networks (servers). Al together about 33000 workstations.
If you're talking about the management server, than the answer is No. However, this should be a one time job, really.
True, the installations should be an one time job. However, we want to totally automate the installation process of a server. That means not only the Server OS, but also 3th party software like UPS tools and Antivirus software. Because we do not want our people to install software by hand, the total installation process is automated. This ensures that every network is configured exactly the same and no personal signatures are left on a server.
Then there is updating/ upgrading. If for some reason it’s necessary to update the ADNM, we absolutely do not want this to be done manually. Is the ADNM software able to update itself?
Do you know how ADNM behaves when we Sysprep a server installation. This would solve our unattended initial installation problem.
Yes, replacing the file and restarting the avast! Management Server service is all it takes to update the license. However, again, this isn't something you'd be doing too often (or on too many systems) to actually deserve scripting, is it?
True again, but we have to consider the future. When the licenses expires after for example 3 years, it is absolutely necessary that a license update can be performed whitout having to manually import a new license file on all of our servers. Thats not the kind of work we are waiting for. After all we love to automate ;D
[Quote][Quote]
One of the major advantages of the Avast product is the deployment of the client packages through AD using a MSI. Can this MSI be generated using a script?
[/quote]
No, but it can be generated using a schedule. I.e. you can have a scheduler item that regenerates the MSI file daily (with the latest data).
[/quote]
Okay…I’m going to try that. This could perhaps cause trouble with MSI GUID’s when deployed by AD. I’ll find out…
[Quote]Why would you need to create new tasks on regular basis (i.e. via scripts)?
[/quote]
Creation of task is indeed not a common thing to do. But you never knows what going to happen and therefor it would be nice to be able to create a task on demand using a script or perhaps a SQL query in case of emergency.
I don’t know if I’m too late or not, but I wanted to respond to two questions that you had.
I haven’t tried a sysprep installation of a server with ADNM installed, but I do know that a sysprep of a workstation with Avast installed works wonderfully.
As for automatic updating of the ADNM console, I don’t think this is possible. As far as I know, the only way to update that is to go into add/remove programs on the server, click on the Avast Management Server, and click update. I know that you only have to do this a few times a year, so it might not be too bad.