The initial setup of the McAfee ePolicy Orchestrator In a Microsoft Windows environment is very easy. In the Linux environment, we have faced a few difficulties. However, with the support from McAfee, we installed it successfully.

I rate the initial setup of McAfee ePolicy Orchestrator a four out of five.

The product's initial setup phase was difficult since only a professional can do it. A fresher or a new person cannot take care of the installation of the tool. A fresher or a new person cannot take care of the installation of the tool. Agent installation is easy, but the other features related to the antivirus and DLP functionalities can be implemented only with the help of a professional or skilled person since they can be deployed only from the server console. The person should be aware of the server console functionality.

I faced many challenges when deploying the product, especially some connectivity and compatibility issues.

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

The solution is deployed on an on-premises model. 

The time required to deploy the solution depends on the number of endpoints where the solution needs to be deployed. If there are 5,000 endpoints where the solution needs to be deployed, then the product can be deployed in a week. It is a robust product, and through McAfee ePolicy Orchestrator, users can deploy the product, including the deployment of a few third-party products, which are minimal in terms of size. My company has experience deploying CrowdStrike Falcon Sensor with Trellix ePO, as users just need to create a package and deploy it from the ePO server itself.

It's easy to set up the solution. It's not overly difficult or complex. I'd rate the ease of implementation nine out of ten. 

The initial deployment was one week.

Right now, only one person is in charge of the McAfee Orchestrator. Every time a new computer comes out, they already have the agent on it. It's one person handling everything, including maintenance, and he's the infrastructure manager.

The implementation process is complex and requires four to six people, including a QA person.

It was a complex process because we needed access approvals to use SaaS, and the URLs would get decommissioned most of the time. We also faced problems with end-to-end encryption.

The initial setup is straightforward, and the upgrades are complex.   

The solution's initial setup is easy.

The initial setup is easy. It de[pends on the way you install it. The solution was deployed within a couple of hours. Four to five people are required for the maintenance.

The initial setup is easy. I would rate it a ten out of ten. The deployment process depends on various factors, such as the network. Usually, it takes a few days.

The initial setup was long before I arrived. Sorry, I couldn't tell you more.

The deployment is strongly dependent on our environment's size, the number of workstations to deploy on and to deploy new versions on. But in general to get to 90% coverage when we have to deploy a new version, it takes at least a month. That's mainly due to the number of endpoints and then to manage and to control them, to make sure they're communicating correctly, that they're powered on, and that they're on the network.

It's easy to deploy. This does depend on the complexity of your environment, and it depends on how you set it up. You can make it as granular as you want. 

It is not something that's very easy to administer. You have to go for a course with training modules. Once you understand how to use it, it becomes easy. For a beginner, it's not that easy. It's a very complex system. If you know what you're doing, it becomes easy.

The initial setup is very easy and the system only requires one person that has reasonable knowledge to manage it. 

Bringing the ePO and central management on board was very easy and very straightforward.

The initial setup of this solution is straightforward.

Our deployment took place within one week.

Its initial setup was straightforward. It took a couple of days. It has been pretty easy to add new machines ever since.

Over the years, I've noticed that the initial setup is very easy. It may be because I've worked with it for a long time, but the initial setup is easy, and even when it comes to doing the configuring for the projects, it is not complex.

Most of the setups that I have done are on-premises, where I have to set up the physical machine, and I haven't had any problems. It usually takes less than thirty minutes for everything to be set up and the deployment complete.

The deployment process is pretty easy. Soon, I'll have to go to the latest version, and we will have to do two sequential upgrades to go to another version and then to the latest version. I'm seeking to install it from the beginning to a new server and so far it looks to be pretty simple.

The deployment of the McAfee ePolicy Orchestrator is very easy on the endpoints. However, deploying the solution in a large enterprise is very difficult. In terms of all the components of McAfee, it is difficult. There are lots of false positives and manual effort required for deploying the advanced component section.

The initial setup was straightforward, not complex.

I don't recall how much time it took for the initial deployment but it was a very easy setup, and updates, new versions, etc. are also easy to setup. Deployment is quite a quick process, maximum one hour for a console but now we just do the regular upgrades to the latest version which is a simple process. 

The initial setup was not straightforward. It takes time to deploy and configure. 

The implementation of the McAfee ePolicy Orchestrator is simple, it took us approximately 45 minutes.

The initial setup is quite simple. We didn't find it complex at all.

I was not there during the original implementation. I'm very new to this organization. I had just joined the team a few months ago. This solution has been running for the last five years, so I don't have more historical data in relation to the original setup.

We have two software engineers overseeing the project.

The solution's implementation is pretty easy to install. It's very straightforward once you have your database. It's not complex.

When I joined the company, it was in migration. I wasn't there from the start, so I can't say how long it took. However, I was around when they did the migration and that took less than a month.

I have managed the setup to new servers (kind of a migration). I will admit that it was very straightforward. My policies were easily accessible and managed.

The initial setup is very straightforward. The IT administrator can install and setup basic functions of the system without a user manual.

However, for some complicated functions like drive encryption, it is better to read the user manual before deployment.

It was not the easiest projects I did, but with help from McAfee it was not that difficult.

It's a little bit complex to configure it, but when you start using it, it is much easier. There are many policies that you need to create, and in three or four places. When you assign the policies then it starts working.

In terms of an implementation strategy, we need to get the requirements from the customer. It depends on their requirements. You have many options, many features. It depends on what you want to configure. If you're looking only for a particular part, only DLP for example, it depends what you need within that. But for DLP it will take about one day to finish.

The initial setup is quite straightforward. You just need to set up an SEO database in the backend and couple the SEO database in the ePO management console. It's quite simple. 

The initial setup is neither easy nor difficult, and I would rate it a five out of ten.

I rate the solution's initial setup a five out of ten since it was neither easy nor difficult.

The installation process is straightforward.