The initial start-up was fairly straightforward thanks to the specialist support of the vendor. No major incidents were detected.

The first implementation was difficult since the tool has a fairly high learning curve.

If you are using all products as cloud, implementations are very easy. However, if you want to use on-premise for regulation purposes, the implementation becomes a little complex. You need to install a connector on your environment to encrypt the data in the cloud.

The initial setup is extremely straightforward. We received an email saying to scan a QR code to install and set up the app. We input the login details provided, and we were done. From the company perspective, they had to log into the management suite, set the rules they wanted to activate, and send the emails. 

It was very brief and fast to set up, and extremely quick to review and ensure compliance was universal. As soon as threats were found they were flagged. Users could not use any malicious apps or networks. The devices are protected immediately. 

The initial setup was relatively easy, with no issues to review.

The product can be easily deployed on our mobile devices. We can create login credentials and easily work on it.

The initial setup is straightforward (though version to version - device to device it may vary) and the deployment takes no more than ten minutes, but when it comes to 'fine-tuning or customizations' (some specific need/business requirements) it takes time and a series of testing for its fitment.

Deploying Harmony was straightforward.  You can deploy it using an MDM solution, but we didn't have one at the time. We deployed by email or SMS, and was relatively simple. 

We explored the MDM part with Google but ran into some issues because the feature required for this integration requires an enterprise license. We have three staff members responsible for implementing and managing the solution.  

The initial setup is very easy and straightforward.

The product's initial setup phase is very straightforward.

For the product's deployment phase, you just need to install the agent to the end user and configure the policy on the cloud management console.

The solution's deployment phase is a one-day task.

The product's deployment is easy. You only deploy the tool on the mobile device for the client or customer who wants to use it.

I would rate my experience with the initial setup a ten out of ten, where one is difficult and ten is easy.

The management console is on the cloud. The deployment takes around five to ten minutes. 

The solution has a straightforward setup - especially with Intune integration.

One of the parts that worried us was its configuration and administration, however, it was extremely simple.

The initial setup is very easy. The cloud solution is easy to deploy and integrate with our MDM.

The initial setup is straightforward.

The process involves getting a license from Check Point and enabling a module/blade on the security gateway. After this, start on the configuration (Published data, which needs to be made available on the endpoint to access).

Its initial setup is very simple. If any additional configuration needs to be done, I just receive an email. When a user is added to the portal, you receive an email with information about the server and the password. You can just click and start the application. It is very easy.

It is pretty fast. It just takes one minute for the installation and the first scan.

The initial setup was pretty straightforward. There were a couple of ways to handle the roll-out. We could send an email with a barcode for the users to install it and there was also an option to send an SMS. They could then install it and it was pretty straightforward.

Prior to that, we sent out a communication explaining that this was what we were embarking on, that it was an executive security initiative. We still had a few calls from users because it was a new area and people were very concerned. We had to keep reassuring the users that we were not spying on them, that we were just protecting the company assets. We explained that it was no different from a laptop or a workstation that the company issued. We had to continually reassure them that it wasn't an issue of privacy. In fact, we told the employees that apps were leaking privacy information and this would turn that off and prevent it from happening.

Initially, there were a lot of concerns about privacy with users saying, "This thing is going to spy on us." But we did not roll it out to every employee's handset. We rolled it out to the company-issued handsets. We took that approach and, at a later date, based on how we run this solution and how we get it to "soak in," we'll move to the other area. But there were a lot of concerns. 

We didn't find any complexity around the installation of the solution on end-user mobile devices. Without the MDM integration, we were not able to force the install and the user still had the option not to install, and if it was installed they still had the option to remove it. But it was straightforward. There weren't any complexities.

Our deployment took about a month or a month-and-a-half. The problem we had wasn't with the roll-out, rather it was about our being able to separate company-issued handsets from the list. We went to the team that issues the handsets and they did not have accurate lists. The audit they had done was a month or two prior so we only had accuracy in the list up to a month or two before. The challenge wasn't about the solution itself.

The setup was straightforward. The configuration was easy and understandable, and we relied heavily on built-in objects and groups.

I rate Check Point Harmony Mobile's deployment an eight out of ten. 

The initial setup was straightforward and the documentation was excellent. 

It was pretty straightforward. We had a solutions engineer walk us through things and helped us tie into our MDM, which went well.  

I rate the solution's initial setup process a nine out of ten. We take help from its documentation and execute the implementation manually. Although, the documentation needs to include a few crucial steps for onboarding users.

Not having an MDM is somewhat more complex as it cannot automate, and in the iOS environment, it is more complex than in Android.

The initial setup was quite easy for me. It was deployed within one day.

The initial setup was very straightforward, not complex at all. For us, it was simply sending out an email link to our users. They installed it from the App Store, and that's it.

The initial setup is easy, and deployment takes just a couple of minutes.

The initial setup is straightforward. It's an easy setup with just a flip of a switch.

We were set up and ready to go very quickly. Because it's a cloud offering and hosted online, it's made to be much quicker.

The deployment was less than a week. We installed it manually on the devices then integrated with an MDM that automates the process for all manual devices.

The initial setup was pretty straightforward. Setting up individual networking is a little bit more complex besides depending on how granular your organization uses it, but for us, it was pretty straightforward.

The installation of the solution on end-user mobile devices was not complex. It's straightforward. It's very simple. Our end-users are able to install it themselves, we don't have to really be involved in that process so they're able to do it without help from IT for the most part. That is super helpful to not have to handhold as an IT team all of our users, they can just do it and it works. 

There is no enforcement mechanism that depends on the user if they installed it or not. We don't enforce it in that way, but we do enforce it based upon if they want to have email access. We require them to have it so we validate that it's installed before we install email, but we don't enforce it.

There was definitely concern from end-users about their privacy. Especially with the networking part, the way that it's able to see everywhere they go is a big security and privacy issue. We addressed it by not requiring all our users to have it, but if they want to email, they have to have it and so that's how we ended up getting around it. We had people that ended up using a company phone and a personal phone separately because of it.

The deployment is still in process actually, but that's mostly on our end, not really Check Point's end. We don't have all the policies in place to have that process set forth of how we're doing it so we're still kind of working on that. 

In terms of our implementation strategy, as of right now, we have emails set up on people's devices using a different application. That application is no longer working and so as users want email, we implement it, but we aren't pushing users to have email on their phone. And I think in the future that's going to be the case, but right now it's not because we don't have company policies in place for that.

I'm responsible for the deployment and maintenance and I'm a system administrator.

The initial setup is straightforward. 

The initial setup is very simple & less time-consuming.

The deployment took around three months. 

The initial setup is pretty straightforward. It's easy to deploy.

I would say that the setup was fairly good enough. 

The initial setup was quite simple.