The setup is straightforward. However, we did have bandwidth issues. We have about 36,000 systems in our network and in some remote locations, and we found it difficult to maintain bandwidth. For certain endpoints, there were issues around operation and installation. However, for the most part, it was simple. Overall, I would rate the process a 4.5 out of five in terms of ease of implementation. 

The initial setup of McAfee Total Protection for Data Loss Prevention requires some support and good knowledge.

Initial setup is very easy. I would rate it 4 out of 5.

We use a team of two people for maintenance.

The solution's initial setup was straightforward, but the configuration from the server end was a bit complex.

The initial setup for McAfee Total Protection was straightforward. I set it up myself as it was for home use, but if it's the enterprise version, you would probably need a consultant or an integrator to implement the software.

The initial setup of McAfee Total Protection for Data Loss Prevention is not straightforward. When implementing a protection solution can take a lot of time.

The initial setup is straightforward. It only requires installing the agent on the end nodes, and the management console, installation and configuration are not difficult. 

I found the initial setup to be complex. If I rated it out of ten, it would be a four for ease of setup.

The deployment itself took one month. 

We had about five people involved in the initial setup process.

We are able to maintain the solution ourselves in-house. We have two people from IT handling maintenance duties.  

DLP was a very difficult solution to set up and use. It took an expert with a lot of experience to do that for us. It's very hard to implement across the enterprise with the different faces of where the DLP engines live. One of the challenges was that we weren't setting a generic policy, we have many different levels we're dealing with. It touches so many different things that it takes an army to maintain.

The initial setup is very straightforward and simple. it's not overly complex or difficult. 

The deployment only takes five to ten minutes. It's pretty fast.

The tool is easy to setup. I would rate the product's setup an eight out of ten. The product's deployment takes 10-15 minutes to complete. 

For the Data Security product, McAfee is easy to install and it is easy to use. This is not the setup and usability that are part of the problem when it comes to this product.  

The initial setup is smooth, especially when handling data in Gmail. We typically collaborate with local IT partners who manage email services for our customers, which simplifies the process. It takes about a month and a half to implement the solution at a company with 2,000 users. For a smaller company with 20-50 users, it takes three to four days. The deployment process involves downloading the software, installing it on the servers, and then exploring its functionalities.

The initial setup is complex. The configuration requires that many points have to be considered before it can be done properly.

McAfee Total Protection for Data Loss Prevention's deployment is straightforward and takes 30-40 minutes to complete. You need to configure it to the part that needs to be filtered out. 

The solution was already pre-installed in an on-premises environment by the time I arrived. I wasn't a part of the initial implementation. 

The maintenance is pretty straightforward. 

The initial setup is quite complex. Each scenario is different depending on our customers. We have multiple teams providing multiple services. I have three engineers who work with McAfee and we also provide support. 

The installation and initial setup are not so hard. I would have to give it a mid-range score. Some of it is easy and some of it more difficult. Let's say fifty-fifty as that is the best way to describe the initial setup: half easy, half hard.  

The initial setup of McAfee Total Protection for Data Loss Prevention is complex. The configuration can be complex. For example, configuring the policies and filters.

The initial setup is simple and quick, but the configuration is complex. We have to put documents and other pieces which cannot be sent to an outside company.

With some initial supervision, the initial setup is straightforward. 

I wasn't involved in the implementation for this client in particular. 

My experience with McAfee from a vendor perspective is if you have the right skills, it can be deployed quite easily. The only challenge is it uses a lot of hardware.

The time it takes for deployment depends on the variety of clients. Some clients have 1,000 users, so it's quite easy. 

The actual deployment before rollout to all of your users is not long. It takes approximately two weeks.

The number of people required to maintain this solution depends on the scale of the project, the customer itself, and the number of users. There is a lot of awareness that needs to go into DLP and Endpoint DLP to train the user.

The initial setup process was easy.

The solution is deployed on the cloud and on-premises.

The initial setup is complex, and on top of that, when you try to reach out for help and try the customer support number, they tell you that you are calling the wrong place and redirect you somewhere else instead of helping you. You need to go through a vendor to get any help, and they have to go to McAfee on your behalf.

In terms of maintenance, many other antivirus companies have software that provides maintenance. If you're going for the on-premises solution, maybe a server requires maintenance every six months or one year and there is usually a printed maintenance checklist. It's an offline process. However, no one can sort out this process on my team. On top of that, if you are going to increase the volume, you will need to upgrade and it is another platform that you have to buy and that will require maintenance.

The initial setup was straightforward with McAfee's help.

The implementation of the solution is complex. Based on the architecture, it should integrate with different solutions. The full implementation took approximately one month.

The initial setup was somewhat complex. It was a little time consuming just to get everything functioning and set up correctly. I would say it wasn't heavily complex, however. 

The documentation on how to do it was relatively good. It was something that, without a lot of skill, could be deployed. It just requires some focused knowledge. 

Overall, I would say it has a moderate level of difficulty as far as ease of deployment.

The deployment takes quite a bit of time, based on the variety of applications in the system. For us, if it was a very homogeneous environment and all systems had the same applications, and they were all sort of built off the same images, so it would be relatively easy to do. There would still be some complexities with the unique differentiation between systems.

If we were deploying to an environment that was very heterogeneous and a highly varied array of software in the different systems, it would be much more complex and time-consuming to deploy.

The maintenance would be pretty difficult if it was an actively managed environment. If the environment has new applications and updates and changes on a regular basis, it requires quite a bit of management within the technology to keep up and authorize new known items for protection. However, in a less dynamic environment, it would be much easier to maintain. My concern, and one of the concerns we had just with the technological approach, was how easy would it would be to maintain and manage the system long term.

Generally, the solution is pretty straightforward to setup. It's not complex. That said, there is a common issue with an installation video. It's something about TLS support, TLS version 1.1. There's a command you should execute, however, there is a conflict of KBs. We had to do a bit of research and we were able to troubleshoot it ourselves in the end.

Ultimately, deployment takes about two to three hours. It doesn't take too long.