The initial setup was straightforward. Once all the right requirements are in place, such as installing the necessary servers, deployment takes less than one hour. The only aspect that may require more time is setting up policies and rules and determining where to apply them, especially if it's a fresh installation.

The initial setup is straightforward.

The deployment takes about two hours for server-side installations because it has many features. There are extra installations, and we have to add roles and features on the server manager.

There wasn't really an implementation process. It's pre-loaded on our Golden Image. It was in with the Windows 10 addition. We didn't have to do anything really.

The solution had a moderate amount of difficulty at the time of implementation. It was neither easy nor hard. 

The implementation of the solution is simple.

We have experience with this solution. Therefore, our technicians can deploy it easily. In the beginning, when implemented it for our initial customers, it was easier. They were PGP at that time. When PGP became Symantec, it was a little hard because of the integration of the products with the Symantec suites. With Broadcom, it has been easy for us. We could work with almost any kind of change that we have received or found with the rebranding of the product.

The deployment duration depends on the number of users that our customers have, but, typically, the server and the configuration of the policies take about one week. After that, we start to deploy it to all the clients, which takes three or four days. We need to wait for the hard disk encryption to be completed, which takes around four or six hours, depending on the information that the users have on the disk. It is usually fast.

The initial setup is easy and takes ten minutes to complete.

It is complex to set up so you really have to know what you're doing. You must have someone with experience in it before you can deploy it on a customer's premises.

The installation is easy.

The Symantec setup is a bit complex. It takes time. It is simple, but it takes time. It also takes a bit longer when creating the profiles at first.

The initial setup is not complex, it's easy.

The deployment is easy. You enroll the users and the server, then go to the user and deploy it, reboot the system, then clarify that it is running. From there, you will have an operator to access it.

When the system is rebooted you will be asked for an encryption key. Everyone in the organization has to enter an encryption key.

We have five operators for this platform with four servers.

It is an obligation to deploy it. The scope of compliance, with the goal being to cover all of the infrastructures.

Currently, we outsource the managing of our infrastructure to another company, and we have a dedicated team for our bank. We have the help desk, all of the infrastructure, the networking, the security, and the systems.

The initial setup was straightforward. We downloaded the software, put it on a disk, sneakernetted it over to an isolated network, dropped it in the drive, initialized it, and enabled it. It was pretty easy.

The solution’s installation was easy.

The solution's deployment could be done in a couple of minutes.

The solution is deployed on-premises.

The initial setup was easy but we had an issue with the product. We used a consultant for implementation and deployment took around two months. The senior system engineer and the managing director used this solution.

The initial setup is of medium difficulty. It is neither simple nor complex.

The installation is pretty straightforward, especially for an engineer. It's a process that just flows. It's pretty easy whether it's deployed on-premises or in the cloud. 

Compared to cloud the initial setup is complex.

The cloud version is easy to set up. It's one gateway and you connect it and it's pretty much a configured service on the cloud.

Generally, the deployment takes a month for seven hundred endpoints per customer. This includes installing endpoints for customers.

To frame the policy and set up on-premises, it's approximately a week.

At first, the initial setup was a little complex. Once I understood what I needed to do, it became straightforward. So, initially, there was a bit of a learning curve. For example, I needed to understand that I wasn't overpaying for the number of seats that we needed based on how we expected to scale up for that number of employees that we had.

We upgraded to the latest version within the last six months.

The initial setup was straightforward. It was fast, easy, and not intrusive on my company.

It was hard to install and took us about three months. The installation was outsourced.

The initial setup is not complex. It's very easy. Deployment time depends on the client and on the machine. Some machines take 24 hours, some machines take three days. Some machines even take up to a half-day. It depends on the hardware.

The initial setup is straightforward. The deployment duration depends on your hard drive. It can take 5 to 10 minutes, half a day, or one day depending on the size of the hard drive. For 80 GB of data, it will take 7 to 8 hours depending on the hard drive and the RPM of the hard drive. For an SSD, it will take less time to encrypt the data.

This product is very easy to install.

For me, the initial setup was intuitive, but then again, I'd had experience with deploying software for 10 years prior to that point.

Back then, deploying software was not like what it is today; it was much harder. You had to do a lot more customization. However, I have a lot experience, so I wouldn't have been phased by any issue I may have encountered.

I wasn't with the company when the product was installed, but I presume the initial setup was complex. The deployment of the product usually takes very little time. I installed the software for new computers and I encrypt the disks. That is all that has to be done so the installation of the product is very quick. It is the encryption of the disk that takes time.

The initial support was straightforward.