ReedMikelI can tell you their handling of command line switches is anything but intuitive.
firstname.lastname@example.orgThey are so unintuitive that the /fullauto does not run a full scan, it is a quick scan. You would think they would have used /quickauto instead.
saputo444ReedMikel have you tested your script on Windows 7?
CCDaveJust a quick comment on the license prices that have been posted here. The $8.35 rate is the starting rate for a 100 license pack. We contacted them, and eventually purchased, a 400 license pack for our initial rollout and received a $7.35 rate. Breaking this down this comes out to be $0.62 per license per month. For the great ongoing protection that the Malwarebytes' product gives, I feel $0.62 is a small price to pay (and pass on to clients).
ReedMikelHi Dave - are you using MB as a true AVAS solution with realtime protection, scheduled scans etc? If so, are you using KES/AVg too? Or maybe you use MB just for fixing infected machines? Thanks - Mike
CCDaveNow I'm going to be using MBAM as a second layer of defense with the AV client that's already installed (Symantec Endpoint in most of my cases). The only drawback right now to the MBAM solution is there is no administration console for management. I'm doing all installs, updates, log reads, etc. using the Kaseya scripting engine.
I don't fully trust it as a AVAS solution on it's own, but paired with a good AV solution I think it is a win/win solution.
ReedMikelInteresting approach. Assuming the MBAM version you'll be using includes realtime protection, I'd be worried about the resources two AVAS products will consume. I have some nonprofit companies that do not have the latest and greatest hardware, so memory footprint and resource consumption is a concern to me. But I agree that no single AVAS product protects one against all threats, so your idea makes sense. Hopefully it won't impact your clients too much - but only time will tell...