Sorry, but I’m not fully agree with you. :wink:

We have a lot of customers working in a workgroup environment with more than 100 PCs, especially in an education environment where an administrator need a central management to know what is happening in every classroom. Currently these kinds of customers are using ADNM.

The problem is not the installation procedure; in a workgroup environment you have a public folder in a server where you can put a setup file to install the clients. This is the easy way that people is using now with ADNM. Why SBC hasn’t a MSI procedure to create a setup file for clients like ADNM?

When you have more than 10 PCs and you are the administrator you want to know what is happening in your network. SBC must be the tools to help administrator to manage his network, not only to install, to know how many virus are in the net, to know how many PCs are protected, to know the source of the virus: email, pen drives, Internet… to know what the AV solutions is doing with a virus: delete, move… to schedule regulars scan on the network… To do some of this managed task is not important is you are in a domain environment or if you are in a workgroup.

If in a workgroup of 10 PCs you use a non-manage clients, maybe the installation procedure is easy, but then you don’t know what is happening. Who has a virus? The virus is deleted? Where is the source of the infection? How can I schedule a boot-time scan in all the machines?