The initial setup was straightforward. In terms of the implementation strategy, the only thing that we had to do was to create policies to turn off Windows Defender. It is recommended that you don't have two antiviruses running at the same time. We did that with a GTO, and then we pushed out the software through group policy. It was a big process because we had Sophos. We had to get Sophos off the machines and then deploy Malwarebytes.

Its initial setup was pretty easy. They gave us a login. We generated an application download and a few keys, and we were off and running.

Its deployment probably took about a week or two. We could have gotten it done a lot faster, but we were having to schedule one-on-one sessions with our end-users to make sure that we could remote into the system and download the appropriate software and get it set up. Realistically, we could have done a full implementation in two or three days, but just due to schedules and other things, it was lengthened out to about two weeks. The implementation, however, was pretty simple.

For its deployment and maintenance, one person is required.

The initial setup is simply a one-click process. It's probably a quick process.

Malwarebytes is convenient because I can carry my USB thumb drive along with a copy of Malwarebytes on it and plug it in. If I have local admin access to the machine and can run the product.

If your organization is large enough, you can divide that and best practices in security. Say you should divide it up so the fox isn't watching the chicken house.

I am a small organization, and it's one thing if the company has enough employees. However, the majority of the businesses I work with are extremely lean. In many cases, if they're lucky, they'll have someone with even the most basic cyber security skills.

Malwarebytes's initial setup is simple. It is easy to deploy and configure the policies and the configuration. I deployed Malwarebytes for one customer and I did it in under two days. They had approximately 50 users, it took approximately an hour.

The steps I took for the implementation were downloading the Malwarebytes management console from the site, installing it, then running the discovery tool, scanning my network, and checking all of the PCs on my network. It's already pre-configured, you don't need to configure anything. The only configuration that I did on the administration console was some of the exclusion from the scan. This is the only rule that I have created.

I rate the initial setup of Malwarebytes a ten out of ten.

Initial setup is straightforward. 

The initial setup of Malwarebytes was easy.

The solution is deployed on the cloud. My customers have the tool deployed on their own cloud.

The time for deployment depends on the number of users, which can be a hundred, two hundred, or five hundred users. Depending on your approach, if you have Active Directory and domain controller, you can deploy it centrally from the console itself with the tools that can help you deploy faster. You can also deploy the tool one by one, a process in which you can install the agent and simply install the agent and the machines, after which it will be rest registered on the cloud immediately.

The initial setup was straightforward.

The initial setup is very simple and quite straightforward. 

The deployment process took only one day.

It was on the cloud. That made it all pretty simple.

Some prerequisites I integrated. It was really easy.

It's working in the background. There's nothing to do. Only administrators can do some tasks. For all users, there is nothing to do at all. It is automated.

You only need one person to handle deployment and maintenance. They are in cybersecurity. 

The solution’s initial setup is very simple.

Straightforward. We're a very large environment, so it took us a couple of days, but technically, you could begin deployment almost immediately. As is the case with any AV product, you have to fine-tune it to deal with false positives and performance issues. Aside from that, the deployment itself can be done very quickly. You can use SECM, PDQ. They even have their own deployment tool that you can use. It's pretty easy to get it out there. 

We did the implementation ourselves. My security department partnered with our patch management and asset deployment team. We gave them the packages and the switching, then they began deployment from there. It doesn't need a lot of maintenance. About three people should do it. Whoever deployed the solution will occasionally need to redeploy or fix an agent. You also need one or two frontend security staff to operate it.

The platform is straightforward to install. Its automation functionality runs updates seamlessly in the background, requiring minimal user intervention.

I rate the tool's deployment a ten out of ten. My organization has 200 endpoints, so deployment took a day to complete. We download the installation, set up the policies, and deploy them to all machines in the domain.

The initial setup of Malwarebytes is easy. I need to log in to my account, so nothing much is needed.

For deployment, you register for the account, and everything is automated.

The initial setup is not complex at all. It's quite straightforward, actually.

The deployments are pretty quick. It typically takes about five minutes per endpoint. However many endpoints you have will dictate how long it will ultimately take. 

You don't really need too many people for deployment and maintenance. If the client buys only the endpoint, the client usually implements it. If they need to, they may request a consult. We usually do the implementation remotely on the local server or whatever computer they dedicate for it. There is also a web solution that you can just add a console to. You always enter via browser, however, you can have it local or on the cloud.

It was very easy. It took about five minutes. 

In terms of the implementation strategy, we just decided that we were going to deploy to every machine. So, we just created a policy to do so, and it just happened.

The solution was not complex to set up. It was pretty straightforward for the most part. We found it to be rather easy.

The initial setup was straightforward and transparent. It took just a few hours and was deployed by our in-house IT people. 

The initial setup is straightforward. It took probably about 10-15 minutes to complete.

The initial setup was very straightforward for our team. We didn't find it complex at all. I'd say that the team considered it to be very easy.

Deployment took about an hour and a half. You just need a PC and WIFI. In total, to get everything set up properly, it took us about a month. It took that amount of time to make it work within our environment.

We only require about two to three people for deployment and maintenance. We used two people to deploy and have three people on maintenance duties.

I find that the setup and configuration are complex and difficult.  

I did the setup myself, it was very simple. I think it took maybe five minutes. 

The initial setup was straightforward. I just downloaded it, then it did everything itself. Once it was on my desktop, it was working.

The initial setup is very straightforward. It's not complex. You just install it and you are good to go.

There isn't too much maintenance needed on the solution.

It has an easy setup. It was quite straightforward and user friendly.

The initial setup was not too complicated. It deployed easily. I don't think there were any difficulties around implementation. The client actually did it before we were involved with them, so it must not have been too difficult.

The organization wasn't large, so the deployment only took about two to three days. It wasn't too lengthy. It went pretty quickly.

In terms of maintenance, one person can handle the job easily.

The initial setup was straightforward. It was just an MSI installable. Double-click it and then it installs.

The initial setup of this solution is complex because we had to understand the product before we can complete the process.

The initial setup was straightforward.