The implementation is fairly straightforward. AWS works well. Deployment takes about a week. 

Our implementation strategy was by the book. We didn't have to go too far out of the box. Our clients bought it. I walked them through it. They had a little bit of pain, but it wasn't so bad.

Our clients are using between six and 12 individuals just to maintain this, partly because it has a huge compliance overhead and partly because, as PRRC, I require that. 

It was a straightforward process. We were on-premise. We were using group policies to manage this whole EPM solution, and it was easy to move to the cloud. Wherever you have agent-based deployments, there is always a little bit of complication, but we were able to make it work.

On-prem deployment took almost three to four months. We had a very large and wide-scale environment. A lot of legacies were also built-in, so it took a while to build the policies around, get the local admins out from the endpoints, and take over with Defendpoint or the BeyondTrust EPM solution.

The migration to the cloud was pretty good. It wasn't that bad. When we had it on-prem, it was a single client. When we had to go to the cloud, two clients were needed. One was the iC3 web adapter that makes a connection to the SaaS cloud, and the second one was the existing Defendpoint client. Having an extra client adapter needed a little bit more packaging on the endpoint side, which added a little bit more to the transition to the cloud. Policy-wise, everything was straightforward.

The complexity of the initial setup depends on the organization it's applied to. If an organization has a complex IT environment with multiple applications or legacy systems, it can be quite complex. However, if an organization mostly uses cloud-based applications, it's relatively straightforward.

The tool’s setup is straightforward compared to other products. The solution’s deployment depends on remote databases. We should also install a challenge-response code. For Password Safe, we need to install the EPM database, challenge-response code, etc.

It was complex because every organization has its own needs. Initially, we were looking for some solution, but they didn't have that. We had to work around that, and finally, we devised a solution. It was a little bit complex for us to achieve what we were looking for. It took about a month.

It doesn't require much maintenance. The upgrades are done at the backend by BeyondTrust. So, there is not much, but for testing, three to four people are enough. They are from the operations teams.

The initial setup was very difficult. Even if you are an expert in EPM, it is still very difficult. It's not straightforward like Jamf.

We need two to three people for solution administration. We have a big configuration and complicate it with the script that we are running. These scripts are very complicated, and it took us quite a few times to wind it to this case. But now that it is automated, we need half a person to do it. But in the beginning, we needed a lot of people.

And now that it is running and automated, every user has been added automatically without any intervention.

Before, we had a division where we had to add local users all over the systems. But now we are using BeyondTrust Endpoint Privilege Management. All are controlled by the privilege management, and we don't have so many problems.

The initial setup is straightforward, requiring the fulfillment of certain prerequisites. This includes setting up ports and, if opting for reporting through SQL, configuring the SQL server along with the necessary accounts. When all these prerequisites are in place, the implementation process is smooth and not overly complicated.

I rate the solution an eight out of ten for its ease of deployment and integration with our infrastructure.

The solution is easy to deploy. However, it is complex in terms of configuration and customization. The process takes nearly two weeks to complete.

It is easy to deploy. The deployment duration depends on how many servers or routers you have, what kind of IT stuff you need to grant access to, and how much stuff you have. I am referring to the entire environment with all the customers and all the users. If you have five routers, five firewalls, it might take up to two to three days to deploy the entire solution. It also depends on the number of administrators you have.

The initial setup can be tricky in that, if you get the implementation wrong, it will affect everything and won't work as it is supposed to. 

That said, I was not a part of the implementation team, and therefore cannot discuss specifics. I can say that the deployment took some time, however.

The ease of deployment depends on your requirement and your setup. If you are handling the cloud, then it's fairly easy. You simply download the agent and install the agent. The reporting is inbuilt. Policy management is inbuilt. If you consider other deployments, there is some friction, depending on the architecture.

It's a straightforward setup.

The initial setup is straightforward; the way that they provide the UVMs, and the whole package when it comes to deployment. What they do is provide you a complete setup package. Everything in there is preconfigured, so all you have to do is to provide the basic IP addresses and other stuff and that's it.

BeyondTrust Endpoint Privilege Management is easy to deploy. 

It is pretty straightforward to get the agent installed. You install the agent and the server component, and you let the users do whatever they've been doing for the last 10 or 20 years of their life. You also create profiles. For example, I had a developer profile for both Windows and Linux, and I had a profile for a regular user, help desk, and engineering. After you create profiles, an administrator can look at their activities in the log and analyze things like the following:

• Why did he install CCleaner on the machine?
• Why did he install this application?
• Why did he elevate a command prompt to do something? What is he doing?
• Why does he need administrator command prompts?

You can then add things like this to your blacklist, and you can create a profile that will allow or disallow that.

The setup was straightforward. The appliance build was very simple and was completed with minimal effort.

The initial setup was very straightforward and simple.

The deployment time depends upon the size of deployment. If it's a single company with DC and DR, where you have an HA in DC and DR, the maximum time if they have 500 assets, for example, would be two weeks. If everything is smooth, it should be a maximum of two weeks. It could also be shorter.

The product is available in the software as well as virtual appliance form which is a hardened Windows server, shipped securely to the end-user. It does have initial setup and configuration tasks. I would not say it's simple for naive users; however, having said that, it's backed up by very strong, simple and straightforward step-by-step documentation, which is very simple to understand and can be followed by a beginner to mid-level engineer.

Easy.

The initial set up is quite quick. BeyondTrust implementation does not take much time. However, it depends on the complexity of the client. It'll take months sometimes if the customer does not know their requirements. For example, a basic implementation takes 10 to 15 days. However, if there is more access needed it takes months sometimes. Access has to be defined based on the number of end-users. It may take as long as four months or so.

The initial setup is complex.

The initial setup is a bit complex and not particularly straightforward. Deploying this solution for the first time took about a month.

The initial process is not straightforward. It's a bit complex. Deployment took about a month for us.

For a production environment, the setup is easy. For a PoC it is a different scenario.

The implementation is quite easy because the documents are always online. So you can do the installation yourself. But it is always better to have certified engineers to do the implementation so that you can design the infrastructure in a more secure way. When you have certified engineers, they have their own strategies to do the implementation, which is good in the long run. The deployment, however, is easy and very straightforward.

For a program like this, you want your infrastructure to be stable for more than five years or 10 years. So when you do the deployment with the help of certified engineers, they will have their own strategy of doing the installation and implementation so that managing the operations of such solutions will be easy for you. Yes, you can do the installation on your own, but it is always better to have some certified engineers.

The initial setup was easy.