1tb
4
Agree - this particular client opens at 8:00am but does not get busy until 9:00am. As they switch off pc’s overnight (in some areas) we try to capture a scan on those pc’s that get switched on early before they get busy. However we don’t want pc’s that switch on at 9:00 firing up a scan.
@wpn- unfortunately many of our clients have older pc’s that barely meet the spec for their line of business app (old P4 with XP Pro on 1MB). Running a scan on these makes their critical app crawl. So in a perfect world we would ask our clients to upgrade everything to support the latest AV? Not feasible, so we want to switch off all unneeded shields (these group of pc’s are only used for billing/accounting- not surfing, email or P2P) and tweak the AV to cover the basics with the lowest footprint. Hence the need for more customisation in the BPP console groups (eg have a group for old low spec pc’s).
As I seem to recall ‘footprint’ or lack of it, was a great advantage of avast AV (specifically v4.x) over competitor AV.
Unfortunately avast developers need to be careful that catering for ‘feature set’ without focusing on ‘customer needs for performance and small footprint’ is no guarantee of success in the future AV world. Case in point (why enable P2P and IM shields on a server by default? Shields on a server should ONLY be those needed for that machine to optimise the performance vs AV coverage!)