The deployment takes around two to three hours. If you manage the product, one person could be enough, but if you need some kind of additional integrations like ADA integration, you need someone from ADT to access products. One person is enough, but one or two additional personnel may be included. To deploy Check Point Remote Access VPN, you must purchase a license, enable the blade, and purchase client access licenses. You can then follow the instructions to deploy the product, write the necessary rules, make the integrations, deploy the agent to the clients, and provide them with a login solution. I rate the initial setup an eight on a scale of ten, where one is difficult, and ten is easy.

The main implementation was quite simple. Implementing it correctly in our corporate area took us a few days. However, it took us one month to fully implement it in all areas of our company. 

I found the initial setup to be fairly quick and provided a pretty useful system for protecting data leaks during remote connections.

The product is easy to download, set up, and configure. The official site documentation is pretty good and helps you to understand the process in order to get the VPN connected.

The product's initial setup phase was easy. I haven't had any formal training, but I have learned everything related to the tool.

The solution is deployed on an on-premises model.

The setup is effortless and smooth.

Enabling the VPN was simple and straightforward with the purchase of an additional license from the OEM. Once we acquired the license, it involved enabling the module on the security gateway. The solution was ready to go live within 10-15 minutes.

Check Point Remote Access VPN's installation process is easy.

Check Point Remote Access VPN's installation process can be done in two hours with the help of a person who takes care of the configuration part while also taking care of the respective routing configurations that are required.

The solution is deployed on an on-premises model.

The initial setup is not very easy and we are partnered with highly qualified engineers to deploy the solution. The process involves designing the overall network module, carrying out installations, configuring appropriately, and initiating the initial setup. The array agent is then deployed to individual personal computers. It takes almost one quarter.

I would say that the initial setup was straightforward. The deployment process took place on weekends and during non-banking hours. In our organization, we only need around 10 to 15 employees, who include network administrators, developers, and project managers, for the deployment and maintenance of Check Point Remote Access VPN.

It was a straightforward setup.

The configuration was very simple. The application is a very user-friendly tool apart from training and courses for implementation.

The initial setup was straightforward.

The initial setup was a little complex as it was the first time working with Check Point.

The initial setup is very fast and straightforward. It only takes about five to ten minutes. 

You simply set up your firewall and handle settings and then send links to your IT team that can connect them.

The VPN Setup and initial configuration are tricky and not straightforward. For example, you need to:

1. Do some configuration in the gateway option, then:

2. VPN Communities

It would be preferable if step 1 and step 2 were available in one place.

3- Lastly, you must apply the firewall policy

Setting up the VPN Clients is simple once you've already got the gateway in place. If you have to setup the Gateway, it will take a bit of knowledge and expertise.

Installation of Check Point Remote Access VPN is straightforward and it involves agent deployment to user laptops, enabling easy connectivity. Maintenance is low-cost and manageable, even for small teams, as configurations are straightforward. Network security engineers need to specify network segments for traffic segregation, but overall, deployment is automated, minimizing manual intervention and complexity.

The initial setup is straightforward, simple, and centralized. 

The initial setup was successful.

The setup was straightforward.

The initial setup was not overly complex.

The initial setup is straightforward.

The product is easy to maintain. It takes a few days to install and troubleshoot.

There was complexity in the initial setup. With one client, once we installed it and then tried to set the policies, the firewall was not responding very well. I was doing it for the first time, so we were unable to do it. The customer was not pleased with that, so we had to send another engineer to deploy that device. That's not to say it's overly hard - it was just my first attempt at an installation.

We had three engineers handling the initial setup. We deployed it over two days. 

I'm hoping that the next time I'm deploying it, it should be done perfectly, without any support from any other engineer.

Just pull the trigger on a 3rd party. Not complex at all. 

I rate the tool's ease of deployment an eight out of ten. Integrating the solution with the firewall is easy. Implementing a new user typically takes only five to ten minutes. You create the user in the firewall, install the client, and configure the username, making it ready to use.

Maintaining the solution is my responsibility. However, managing the firewall and VPN involves only two or three people. If you consider the entire security area, there are more people involved.

The initial setup is not easy. We need to be skilled in Check Point to install the solution. The time taken for deployment depends upon the number of boxes we install. If we install one or two boxes, one or two weeks is sufficient.

Our customer needed to install more than 100 boxes in every region. It takes months to deploy the product at that scale. We need a team of 20 people to implement the tool for an enterprise. Once the installation is done, maintenance is easy. The product runs smoothly.

The setup was straightforward. Everything was populated on Check Point, so it was easy to select what we wouldn't allow. We deployed on-premise because we have the space and infrastructure to support it. 

The deployment didn't take long. Two IT people are responsible for the deployment and maintenance. The online documentation will walk you through the process. When you do a manual reset by pressing the button, it guides you through the setup process. You only need to follow the steps. 

After that, we import our backup file, and it populates. Next, we run the updates and check we forgot to configure anything else. Some backups are older and might not align with what we have running on the ground. 

The initial setup is straightforward if we are knowledgeable about the task at hand. However, it is recommended to consider a few things and to have a reliable technical support team to assist with the initial deployment. For a small company, the first step is relatively straightforward. However, if we are looking to scale up, we may need to enlist the help of a consultant to properly configure the necessary parameters, as there are many of them to consider.

Once we have configured users, access lists, written firewall rules, and deployed clients to endpoints, the next step is to educate employees on how to use the solution.

On average the deployment took around two weeks to configure all the certificates. This included preparing laptops and PCs. For just the VPN with central management deployment, it would take one week.

Our deployment was completed by two people.

For a basic setup, implementation is quite easy.

The initial setup is straightforward.

The installation of Check Point Remote Access VPN is straightforward. The time it takes for the client installation is two minutes. It is a standard installation.

The setup was straightforward and simple.

The initial setup was straightforward.

We did not find the initial setup to be overly difficult or complex. It's pretty straightforward. A company shouldn't run into problems with the initial setup.

The initial setup of Check Point Remote Access VPN is simple. The deployment took us approximately two weeks.

At first, the implementation was not easy to set up. We found many bugs and we had to install different hotfixes and upgrade the version more than one time.

The initial setup is straightforward during the initial configuration.

The initial setup wasn't too complex. I think their documentation is pretty good for the initial setup. It took a little while, but it wasn't difficult. We did the deployment successfully in probably two months on our own, without them doing anything, by just reading the documentation and having other stuff going on too. We didn't just focus on this deployment.

I just wished the upgrade process was easy and the configuration initial process was easier. In the past six months, they did a fix, where if I push out a new install to users, it doesn't reboot their computer. Now, it will install their client and not reboot.

They need to keep up with Windows updates faster. There have been a couple of times where Windows is updated and they didn't have a new version ready for when Windows was ready, which means the clients that are running on the newer version of Windows won't be able to VPN. If they can keep up to speed with that, then it would be good.

The initial setup is not complex. Plus, we've got the Kryon system. So these systems make it easier for the user. We have known this product for a while, that's why it's not a problem to configure the system.

The initial setup has a moderate amount of complexity. It's acceptable. However, the graphical display of the user chart of network usage, and the ability to zero in on the current graphics could be improved.

The solution’s initial setup is somewhere in the middle, from easy to difficult.

The initial setup was straightforward, especially because we already have the firewall implemented. So we only needed to enable the features and do some configurations, which were not hard to do. They were really fit. 

It took two days. We did our own thing. The implementation strategy was to first have only two or three users from the IT team to test it. Then we allowed it to extend to some teams.

The process is mainly straightforward. 

We started only with the firewall components and this part was straightforward. Once we started to implement the VPN, we had to work with the reseller. Now, we are handling it ourselves.