Semeraro.Nick,  We did a trial of webroot and decided to not purchase their product. Everything we did with the program only alerted to infections it did not offer any removal. There were objects that were not detected by webroot but were with other programs. We decided to go with a standalone malwarebytes.

Thank you JamesB

Although my time so far with webroot is limited, I will throw my voice in as an advocate and very happy customer.

We just last week opted to replace both KAV and KAM with Webroot and have moved only about a thousand endpoints over so far this week, but compared to the time our previous KAV upgrade took us this is going amazingly quickly and smoothly.
I know when I ask questions like yours what I really want to know is "Why will I hate this?" so I can decide if what I'll hate is worth why I already know I'm interested in it, so here's the annoyance list so far:

1. Claim: "Webroot and Kaspersky can coexist, making your migration easier!"
   Reality: Mostly true.  Our method of deployment is push Webroot first, then pull kav + kam the next day and we've had more luck with this going smoothly than we thought possible. So far out of the thousand endpoints we've moved we've had less than 30 where Kaspersky reports the webroot installer as a trojan and triggers a pop-up on the endpoint.  This after we've white-listed both the installer and the installed application in all of our KAV profiles... but then again we're having KAV profile sync issues anyway hence the reason for abandoning it.  This isn't a show stopping problem but has resulted in about 15 or so calls to our help desk despite warning people ahead of time.  
2. While the overwhelming majority of our endpoints have installed flawlessly and shockingly quickly, we have had one minor issue or another with probably close to 100 of them.  These have all been resolved so far with an uninstall/cleanup/reinstall agent procedure and sometimes with the added step of disabling (or removing) KAV during the install process.  It's pretty quick/easy to do this in batches and we've not had to devote a large number of man hours to it so far.
3. Alerting is a little... simple.  "Alert upon detection" is basically the only option and frequently by the time a ticket is made and an engineer assigned to investigate, the issue has already been solved.  "Alert upon detection but only if I fail to do anything about it on my own" would be a welcome additional alerting option.
4. The Webroot plugin is great for deployment, auditing and some issue remediation so far, but one thing to be very aware of is that it does not have any influence at all over policy.  All policy assignment is done through the Webroot anywhere console on Webroot's own website.  This is a minor annoyance.
5. It's a bit of a stretch to call the plugin 1.0 instead of beta, there are lots of silly simple UI goofs, but it does the job without too much extra effort.  Here are some examples:
   1. The machine group and view selectors are different.  Different isn't bad (I rather like their look), but they don't stay in sync with the rest of Kaseya.  If you set a group and view in the "agent" module and then go to the Webroot module, you'll have to set it again.  Conversely when you set a group and view in the Webroot module and go to any other module the "machine group" field becomes populated with a long numeric string that doesn't match any actual group.  Mildly annoying.
   2. The Webroot module does not remember how many items you want to view per page - it keeps defaulting back to 10.
   3. The install/uninstall operations do not integrate with the Kaseya task scheduler at all.  If you select 500 machines and hit "install" - it will begin installing to all 500 of them immediately without any confirmation step at all.  This is a touch dangerous.

All that being said, the entire staff here is unanimously thrilled with the switch.  It has already detected more potential malware and alerted on fewer false positives than Kaspersky was doing on average over this same time frame and the impact on some of our customers ancient endpoints is so much less that they feel they've received a "performance boost" (which may actually hurt our ability to convince them to finally upgrade - but oh well).

To sum up: There is simply no doubt in my mind that this was the right move to make and I think we made it at exactly the right time.

Let me know if you have any other questions.

Disclaimer:  The above is written by a Webroot/Kaseya customer and was not sponsored in any way by any party... but *cough cough* I'm open to bribes from Webroot or Greater Intel if they're feeling generous next week at Connect.

grammar correction
[edited by: Anthony Kepler at 2:40 PM (GMT -7) on Apr 27, 2016]

Anthony; thank you for that very informative review.  We are considering demoing webroot to a few of our endpoints.   My concern is not the quality of webroot, but the quality of the integration with Kaseya.  The Kaseya/KAV integration has been quite the challenge over the last year.

Brutus, I find myself in the same situation as where you are, also looking for an alternative for Kaspersky with good integration with Kaseya. Will you be planning on demoing more Kaseya antivirus plugins (like Trend Micro)?

Hello guys,

I will not start any kind of "fight" to defend which AV product is better. I just want to say that actually we are very happy with this cloud AV and, in just 3 years, we become the number 1 reseller of this product in ITALY.

Regarding Webroot plugin for Kaseya, here you can see a video demo: www.youtube.com/watch

Actually the version is 1.x and is developed by "greaterintell" (that made also ccleaner integrations for RMM - www.greaterintell.com/webroot.html). With this version you are able to:

- see webroot endpoints directly from webroot kaseya integration module and details about it (see video)

- see endpoint infected

- deploy webroot install

- start "clean" command from Kaseya

- alerts and reports

We decided to remove it because GreaterIntell integrations are very "heavy" (not in term of resource allocations but in terms of files/folders that are edited inside a Kserver). Infact, after our trial, we were not able to remove completely this integration because it also edit many SQL tables.

Anyway the product works properly.

Soon will be release 2.x that will introduce the support to "Webroot API" (unityapi.webrootcloudav.com/.../APIReference), so, if you are a developer, you will be able to do many things via webroot kaseya console.

Cheers

Webroot has been an excellent solution for us, with one exception. The 1.0 plugin pushed out an outdated installer, which usually self-updated within minutes. Worked well except at our largest client (of course!), which caused their systems to blue-screen immediately after the install. We developed a procedure to push the latest version ourselves to solve the problem. At Connect, we learned that this issue is fixed in release 2, which is now available.

Glenn

The new plugin version released recently works well for us.  Install was easy as well.  Current Webroot client installer is pulled automatically.  Don't forget to setup the Webroot API information after you set it up.  If you're not seeing some of your machines in the console just run the discovery in the module for each site, that will run a one time script to bring them in.  No harm in running it again if needed.

Edit.
[edited by: bctirado at 8:37 PM (GMT -7) on May 14, 2017]