I implemented it myself both in-house as well as for our client.

We handled the initial setup in-house.

A team in my company takes care of the deployment phase.

We installed the solution through the vendor ONLY.

The implementation was completed by our in-house team with the assistance of the OEM.

Check Point Remote Access VPN's installation process is something that my company can manage with the help of our in-house members.

We had a partnered team with highly qualified engineers to deploy the solution.

The deployment was conducted with the help of our in-house team.

The product was integrated with in-house personnel.

A Check Point engineer who had a lot of experience in his work helped us with the implementation.

The implementation took place through the vendor.

The implementation was handled by an in-house team.

We were able to manage the setup in-house. We did not use a consultant or integrator. 

We implemented this solution ourselves.

Our in-house team set it up. That said, I have been working with network devices for a long time.

We handled the setup in-house.

Implementation was through the vendor.

Implementation was handled in-house.

We handled the installation in-house.

A vendor team assisted us with implementation and deployment.

We do the implementation for our clients. 

We used both a vendor and in-house talent. 

We used a vendor to set up the solution. 

Our deployment was completed by our in-house team. We have a Check Point Certified engineer working in the engineering team.

We handled the entire process in-house.

We implemented the solution via a hybrid approach. Check Point professional service is really good, however, our third-party implementation team was not very good.

I did the implementation myself. We have our IT department that is supporting and doing the maintenance of the solution.

I've done this twice already because I know that we didn't upgrade it. I built out two new servers for it. I have a primary and a policy server. We have a primary endpoint server. Then, we have a secondary, which is called a policy server. This is operational because our clients will connect round robin to one, then the other. It's just that one of them has more precedence over the other as far as enforcing policy. We have those in two different environments, and they're virtual. All the standard things that go along with setting up a virtual environment.

We had to create the policy on the new endpoint server, which isn't too complicated. It includes a list of ports that we needed for our users to be able to use certain applications, like their chat and VoIP, because it has a local firewall. That took some time, like a week building that policy out and testing it. It's really about making sure that it can connect to the endpoint server through the main firewall. Then, it gets its policy from the endpoint server that it downloads and enforces on the local firewall, allowing for the connection to the main firewall. I wouldn't say it was too complicated as far as deployment strategy goes.

Two team members did the deployment. 

We require three full-time network security engineers for maintenance. We manage all the solutions on the security side of our company. Specifically Remote Access VPN requires three hours of maintenance a week.

We handled the implementation ourselves with the assistance of resellers.