I rate the initial setup phase a ten on a scale of one to ten, where one is difficult, and ten is easy.

In general, the solution's initial setup is very straightforward.

I do the deployment of the solution through RMM, so I cannot specifically state whether the solution is deployed on a public or private cloud.

The solution can be deployed in five minutes.

The initial setup is okay. However, they don't have a way to scan and deploy, and just about every other virus program has scan and deploy. With this product, you've got to use PS tools and push it out, make it MSI and deploy it through the active directory, or send the customer a link by email to install it.

I can't log into a server or workstation, scan the network, and push the product out. It doesn't have that capability, and people have been asking for it for years. They're just not going to do it.

It doesn't require anyone dedicated to maintenance. It's pretty much self-updating. We haven't really run into problems with installing or reinstalling updates and patches and so forth. It seems to do a good job automatically of keeping itself up to date.

The solution is deployed on the cloud, which could be an advantage or a disadvantage for some, but personally, for me, working with the cloud-based version is better because it is less work, and I don't have to fiddle with the area of on-premise installations. I am definitely sure that my RMM solution cannot be deployed on an on-premises model. Since Webroot Business Endpoint Protection is integrated with the RMM solution I use, I think it's probably going to stay in the cloud. Some of my managers have expressed concern about cloud-only solutions for reasons related to availability.

I haven't deployed Webroot Business Endpoint Protection yet, but Webroot offers a very nice guide to deploying the tool with Active Directory (AD). The only thing I have managed to do so far with the product is set up the user account and company accounts, which seem to have worked quite well. I managed to integrate the tool with the RMM solution I use, so I was able to establish the API connection. Though things have worked out well for me with the solution, I haven't deployed it yet.

Webroot's initial setup is straightforward. I rate the process an eight out of ten. I can access all the documentation to set it up according to the manufacturing standard, where most of the benefit comes from.

Apparently, is more complex than I originally thought. I had my server set up wrong initially which caused some slow down. But other than that, it was fairly easy.

Very easy, the default is good.

It also has the ability to be deployed in a watch and report only style when cutting over from another AV. This allows proprietary software to be identified and whitelisted rather than quarantined (=broken) then fixed. It makes for much happier end users and a quieter help desk.

The initial setup was very straightforward. It wasn't complex at all. We found it to be quite easy.

We use a remote management software program that allows us to get into computers remotely and make sure that everything is up to date and do the virus scans, etc. There is an integration with the one that we use. It is really easy. It is with the touch of a button.

It is easy to manage. Through our remote management software, we set up the schedule for updating and scanning, and it sends us reports.

The installation is straightforward.

I accessed their cloud platform and downloaded the file setup file for the initial setup. Then I ran a policy on my domain controller with the file installed. The initial step is to have an account with Webroot and then activate the license. And then, you get the user admin user portal, download the setup, and install it, like any other software on an endpoint.

The initial setup was straightforward. A very critical point was missed at the beginning, which meant the only solution was to reinstall it all, which I haven't bothered to do. 

It was a real shame to find out months later that a certain function was based on a poor setting and that setting can't be changed. It's unfortunate. 

The setup was very easy, but unfortunately, we missed some details along the way. You can't change it. The bad news is if you don't do it right the first time, it's not going to get done.

Its setup is straightforward. It's a clean setup. You just install it, and it does all its own setup. From that perspective, it's great. The admin dashboard makes it easy to maintain and track. We had looked at using more of the tools that they've got integrated into the dashboard, but we started having some issues and the lack of support killed that.

Its initial setup is very easy.

The initial setup isn't complex. It's relatively straightforward. You just have to install it on the platform. From an admin standpoint, that's the gist. You install it and let it go and then verify it on the dashboard. That's all.

Deployment is very fast. It only takes about two to three minutes.

The initial setup was straightforward. One simple file to run that had our serial key built into it. It was very quick to install.

Setup was fast and very straightforward, thanks to the training provided.

Incredibly simple. Register, download and run. (Back to the Kaspersky model last used 2015). It runs pretty much straight out of the box, and deployment is simple.

The initial setup was straightforward. I think we spent about a couple of hours on the phone with their support nailing down the right settings for our various categories of machines, and we broke down the machines and added policies for our general servers. 

Here's a policy for our RDS and Citrix servers. Here's a policy for general workstations. Here's another policy for engineering, chat, or graphic design machines because they tend to need slightly more or slightly less restrictive settings. We had to put together five or six different base-level policies. Once they were gathered, there were some white lists added at different times. 

The initial setup is not complex at all. It's very straightforward.

The deployment took a couple of months.

The initial setup was straightforward. It took five minutes. I installed the solution myself.

Yes. We had a quick rollout.

The initial setup for the product is straightforward. We do not deploy it to all our customers at one time because it needs to go on individual devices. When a customer signs up for using the product we need to deploy it on their device. The process does not take more than a few minutes and it is an easy process.  

The installation has been straightforward and it took a few minutes.

The initial setup is very simple.

The initial setup was very easy and didn't take a long time.

The initial setup was straightforward. It only takes one week to deploy all of the infrastructure.

It can be installed next to existing solutions.