A potential user has a good question. They're running 300 computers (in Papua New Guinea) over a VSAT line - 3mb down, 1 mb up. Not a whole lot of bandwidth :)
Naturally, they'd like to know how much bandwidth will be used by Webroot!
My additional question: what settings can help minimize bandwidth, and minimize impact on link performance, for low-bandwidth and/or slow links?
Obviously the initial install file is quite small and could be a single download. But what then...
Anybody have any data or insight?
Best answer by jhartnerd123
In my case and most of my clients, it's waaaay less than a MB per update. Those are only a few Kb. More or less a ping to the cloud to see if there's anything new to report.
My work notebook (that I heavily use online), only used 11.73MB of data for 30 days.
Plus, you also gotta realize that the systems aren't always all going to be on all the time. They also aren't going to always be encountering new files to "check on." They also, by design, won't all check in at the exact same time. This is to avoid network storms that other AV products get when they dispense their multi-megabyte updates.
Believe me, I've had clients on Sat connections using ESET previously. The stub installer alone is several MB, then once you execute it, it has to download 60-90MB of the actual program, then after install, it has to download a further 40MB+ of definition updates. That's just to get it installed initially. Then once or twice a day, ESET issues a definition update that can range from 5MB up to another 20MB+ file.
No brainer for me and my clients once I've switched them all over.
Where some clients on Sat and Fixed Wireless connections would experience slow downs due to several endpoints doing updates at any given time, once we switched them over to Webroot, all that wasn't an issue anymore.
Just because the Webroot agent relies on the cloud, doesn't mean it is a bandwidth hog. You'll never even know it's running once installed.
Hope this helps
Nerds On Site
Webroot Champion & Ambassador