The product's initial setup phase is a bit complex.

The solution is deployed on an on-premises model.

The solution can be deployed in three working days.

The product's initial setup phase was very easy since a lot of documentation was available.

The solution is deployed on the cloud and on an on-premises model.

For the Fortinet FortiGate-VM's installation, Fortinet provides the list of system resources needed, including details of the VMs, RAM, and CPUs needed.

The solution can be deployed in an hour.

It's easy to install and configure FortiGate-VM. One engineer can finish the job in half a day. 

I rate the product's initial setup phase a ten on a scale of one to ten, where one is a difficult setup phase, and ten is an easy setup phase.

The solution can be deployed in an hour or two.

The initial setup was very easy.

The setup is straightforward for me, but our customers might find it a bit challenging. Overall, following the provided steps and consulting the official materials or documentation makes the FortiGate-VM setup relatively easy.Firstly, we establish a console connection to the firewall and access its default IP. In the second step, we create rules to enable the firewall to access the internet. Following these two steps, we register a rule with Fortinet Broadcom, download the necessary licenses, and upload them. After uploading the license, we set up an interface rule, check the license, and configure interfaces such as LAN, WAN, and VPN. Subsequently, we create profiles, including web filter, application, antivirus, and IPS profiles. The last steps involve configuring interfaces like LAN, WAN, and VPN, as well as attaching profiles to outbound policies. We also consider additional configurations, like server publishing, destination netting, or integrating with PBM for Alibaba Cloud. The final three configurations are optional and depend on the customer's requirements.

The setup is not that complex. I wouldn't say it's simple, but It's relatively straightforward as long as we follow the guidelines and work with the recommendations.

I would rate the initial setup a nine out of ten, where one is difficult, and ten is easy. You need to deploy it on a virtual appliance. Deploying the appliance itself is usually straightforward, but designing the architecture and arranging the solution can be challenging for many customers.

The initial setup was straightforward. It got complex when we started adding in requirements for tunneling et cetera. The implementation involved VPNs and the general configuration of the firewall. Then they added in these other requirements that it needed to connect to AWS. First, it was to their remote hosted environment. Then, subsequently, to the AWS environment as well. It grew over time. Over the course of a year, we spent a lot of time on it.

I'd rate the initial setup experience at a four out of five. Most of the stuff went pretty well. We had one issue and we had to drop down into it. However, their support was very good. We were able to contact support, and they were able to stay online and walk us through that problem, so without any issues. They didn't balk at it. We didn't have to beg them to help us. Some support you get in there and have to say, "I'm sorry, yes I've done all those things. Get me to the next level."

They had good quality support.

In terms of deployment, it was there when I got there. They had purchased it out of the box and they hadn't configured it. For six months it just sat there. We had it up and running within a month of me getting there. Then over time, we added more and more requirements to it. It didn't take very long to figure out what they wanted to do with it and get it set up. The actual configuration was very quick. It was just the planning beforehand that took time.

Besides myself, there were about four other people in the IT department working on the product. However, really, only one person is responsible for the gateways.

Fortinet FortiGate-VM is easy to implement, provided you know your network architecture and the basics.

On a scale from one to ten, where one is complex and ten is easy, I rate the solution's initial setup a nine out of ten.

The initial setup is straightforward and quick.  

We moved the equipment to the site, connected it to the internet, and configured it through the console.

The product's initial setup phase was easy.

The solution is deployed on an on-premises model.

The product's installation phase takes three hours if our company's customers provide us with all the prerequisites required for the deployment.

The initial setup process is very easy and straightforward. It's not difficult or complex. 

We only need three people for deployment and maintenance. It's not a solution that requires a big team. You might need one or two field engineers. 

There is a little complexity to it but not more than other solutions. I haven't noticed greater complexity.

The deployment duration depends on how detailed you are and what you don't want to get. You can deploy one of these firewalls in half an hour, but if you're going to add a bunch of complexities and things to it, it can take at least a couple of hours to get it all set up the way you want. It ranges from half an hour to four hours.

The initial setup is straightforward, earning a rating of ten out of ten for ease of use. Compared to other options, it stands out as exceptionally simple, largely due to the extensive documentation provided by Fortinet. Additionally, numerous YouTube tutorials are available online, making it easy to find solutions without necessarily having to consult the documentation.

The initial setup process is easy. It can deployed on the cloud and premises based on the client's requirements.

The initial setup is very easy. It's not complex. I'd rate the ease o setup eight out of ten. 

The deployment might take two to three days. It's pretty fast to get everything up and running. 

I did not handle the deployment in a hands-on way, so I don't have information on the technicalities in terms of what steps were taken.

The initial setup was difficult because we were all new when it came to the Azure environment. It was a little difficult to create space and understand that you have to have more than one interface. But once you get used to it. It's pretty straightforward.

It's straightforward if you have all that is required when you're clearing your traffic. If you're clearing your traffic already into your internal length to communicate with the firewall range, and you have information and understand it before the implementation, it will be very seamless. It will be stress-free when you understand the environment where you're going to implement it.

The initial setup of the solution is simple because everything comes with GUI. The entire infrastructure for the customer is simple to set up with the GUI.

The choice between an on-premise or cloud solution is a decision that ultimately depends on the specific needs and requirements of the customer. Currently, there is a trend towards utilizing cloud-based products as they offer a wider selection and can be easily deployed. On the other hand, some customers may prefer an on-premise setup, which involves deploying physical equipment on the customer's premises or a virtual machine from an OEM. The cloud solution offers greater agility, flexibility, and speed but can also present challenges, especially in the semiconductor industry where delivery times may be longer due to stress in the market. In conclusion, both options have their own advantages and disadvantages, and the decision between them should be based on the specific requirements of the customer.

Taking into consideration the magnitude of the entire implementation, the deployment process could potentially take approximately three weeks, assuming all necessary components are readily available for the physical setup. After this stage, the User Acceptance Testing (UAT) phase commences, which may last for an additional week. Subsequently, before the final implementation into production, the customer would conduct a final UAT to ensure all elements have been successfully deployed and functioning as intended.

I rate the initial setup of Fortinet FortiGate-VM an eight out of ten.

The product is easy to implement.

The solution is deployed on the cloud and on an on-premises model.

The complexity of the organization determines the time required to deploy the solution. Basically, it takes three hours to deploy the product, and for a big company, it takes two days.

One good engineer is enough to take care of the deployment phase of the product.

The initial setup is easy and doesn't take more than one hour.

The initial setup needs to be handled by a person knowledgeable in Fortinet products. 

The installation is really easy. There's HA deployment in the marketplace involving Azure and AWS. I handle the installation myself. 

The initial setup of Fortinet is easy. 

The initial configuration is very easy, even for non-technical users.

The initial setup was not complex. The implementation proved to be straightforward.

The project took about one week in total, including deployment and configuration.

There was only a single person needed to handle the deployment process.

The initial setup is complex because we use CLI. The solution is cloud-based. We have moved our on-premise VM to a private VM.

Fortinet FortiGate-VM's deployment is easy. 

FortiGate offers straightforward planning and a user-friendly interface. This simplicity is seen through graphical user interfaces (GUIs), enhanced visibility and effective troubleshooting. I would rate it eight out of ten. 

In the industry landscape, approximately seventy per cent of businesses predominantly rely on on-premise solutions. Specifically, our focus is directed towards banking clients, who are aligned with the guidelines of the Central Bank due to their emphasis on security, governance, and compliance protocols. However, the manufacturing sector and telecommunications companies are more inclined towards cloud adoption. This inclination is rooted in factors such as cost efficiency and power savings, internal infrastructure maintenance and resource allocation, including power and human resources.

In Sri Lanka, the banking and finance sector still prefers on-premise solutions. This choice is aligned with their security compliance needs and regulatory considerations.

In our proposals involving FortiGate, it's common practice to include FortiManager and FortiAnalyzer. Over the past two years, many clients have adopted FortiManager for cloud-based management. We've facilitated this by providing cloud subscriptions, allowing them to manage their FortiManager through the cloud. This approach is well-received, and it's worth noting that even in the banking sector, some customers prefer on-premise setups for their FortiManager.

The solution's initial setup and configuration are straightforward. But if someone is trying to put policies and restrictions in place, then one has to understand many things. It takes one and half hours to configure and requires two executives for maintenance.

The initial setup is straightforward and it takes approximately two hours to deploy.

The initial setup was a bit difficult. It's not perfectly straightforward. This may have been due to the fact that we were using ISA, which is pretty determined, and we had to migrate from ISA to Sophos and from Sophos to Fortinet. It was a little difficult, but not that complex.

For us, the implementation took about two weeks.

Each quarter we have a managed service contract with the integrator and they do any preventative maintenance every quarter. We have four visits in a year that we have agreed upon. Every quarter they come to us and they do some penetration testing and see the usability features and give us a report.

The solution's initial setup process was very easy. The solution was deployed on the private cloud. The deployment process can be carried out in two weeks, and only three engineers are required. Maintenance can be carried out efficiently.

The implementation process was not complex or difficult. It was straightforward. 

The deployment takes around two to three hours.

Maintenance aspects are handled by the vendor. 

The initial setup is straightforward, although the configurations can occasionally become involved. 

We rely on automation for deployment, making it easy for us. We clone the existing infrastructure for additional customers. Our challenging aspect is coordinating with clients to set up the infrastructure. Understanding the existing infrastructure of business customers, especially their premises and specific requirements, is a crucial step.

The initial setup time of Fortinet FortiGate-VM depends on the policies and filters that need to be applied to different users. The time can vary a lot on the environment. Its time ranges from minutes to a month. However, we can do the process remotely and it takes approximately 10 minutes.

The setup was straightforward because of the integrator's help. Deployment took about two days, and only my assistant and I were required for deployment and maintenance.

We are still getting help from Fortinet for the deployment. We have been able to push this to two clients after we onboarded this. In the next couple of months, we believe that we will be able to take over the implementation and they can take a little more of a backseat. We want to be more independent, locally, with the local support and local team to be able to deploy it. We want to ensure that the service is seamless.

The initial setup is pretty straightforward. With the deployment of any type of firewall, you do have to do some workarounds. As long as you know the specifications, you are good to go. I'd state the ease of setup eight out of ten. 

The deployment, so long as it is not a migration, only takes a few hours. 

The initial setup is very straightforward. I started out in the Cisco world with Cisco firewalls and switches. Then we started deploying FortiGate and I found that FortiGate was easier to learn, especially for junior-level engineers. We were able to get junior-level engineers up to speed quicker than if it was a Cisco platform, especially if they haven't used the command line before.

Deployment usually takes a day, depending on the complexity of the firewall. It might be a day to two, depends on if we are using multiple IPSec tunnels if it's at a data center or a remote site. 

In terms of deployment and maintenance, in my experience, by a rough order of magnitude, a company would need one technician per 30 firewalls. For our company, we had a team of three network engineers and we had a fleet of about 120 firewalls.

The solution's setup was pretty straightforward. It took the team about two to three weeks to deploy it.

In terms of the initial setup, a vendor did that for us. We just manage it. The solution was already in place before I started at the company. I don't have details in relation to its initial complexity or how long it took.

The product's setup is not complex. The tool's deployment gets completed in a couple of hours. 

The initial setup is very user-friendly.

The initial setup process is simple. It involves defining the parameters for deployment, such as the number of sites, PCs, and Wi-Fi users.

The company that provided the solution that was installing it took approximately three days.

The initial setup depends on the types of connections that you're bringing into it and the complexity of the business requirements for individual networks. It depends on how you want to route across the company. Overall, I'd say it's less complex than Cisco but it really depends on who's doing it. 

The solution is easy to install.

The initial setup is fairly straightforward.

The implementation varies from being complex to being straightforward. It can take two to three weeks to implement with some tweaking afterward.

The initial setup is straightforward. Deployment time depends on the case but can normally be done anytime from two hours to two days for it to be functional.

We have not faced any difficulty. We recently migrated our data center from on-prem to the cloud and then established the firewall.

The solution is easy to set up. There is a lot of documentation provided. For 70% to 80% we can do just fine, and for the rest, we just request documentation and can finish the job. 

We do not need much maintenance. We handle that ourselves, and it's not too difficult. 

The initial setup was simple.

We don't require a lot of maintenance. Most of the maintenance is carried out by Microsoft.

It is a custom operating system that is available on FortiGate Firewall, and Palo Alto Firewall.

Microsoft doesn't do anything in terms of upgrades of the patches. They only do basic maintenance at the host level and the VM level.

We only have one person managing the device.

The initial setup was straightforward. A company just needs to get requirements from its customers and then they can just deploy. It's not complex at all.

Deployment takes about two weeks. The setup itself is very fast and you will have limited downtime. However, there will be fine-tuning that will be required and this may take weeks. If a customer gives new requirements at any time, you'll need to make some tweaks.

The initial setup is straightforward. We didn't find it complex at all.

For somebody who does not have experience with Fortinet appliances, the initial setup is very easy, but basic networking knowledge is necessary. The Setup Assistant will guide you through the first steps, and you can config basic settings for basic security.

The initial setup is a little complex. Not too complex, but it's good because we like to work. It takes half an hour at most to install and deploy this solution.

Its initial installation wasn't really that hard. It was very much doable. It was a scaled rollout, which makes it a bit hard to measure.

The initial setup is not too difficult. It's not overly complex. I'd describe it as pretty straightforward. A company shouldn't have any issues with implementation.

For deployment, we did one site and then the other site and it took probably two weeks to deploy it, with maybe 30 days to get it fully configured. Then, once we had one site deployed, configured, and functional, we implemented a copy of that to the other site. We followed this pattern for each of our locations.

In terms of maintenance, it's hard to quantify what you need for the firewall. The firewalls are relatively low in terms of required maintenance. We have one IT administrator that may be a day a month has duties that are firewall-related. It varies, however, it's not significant work to maintain the firewall.

The initial setup is very easy. Somebody who has a little bit of experience in VMware or with firewalls will be able to do it in no time.

FortiGate-VM setup is pretty straightforward. It depends on the implementation size, but it takes a week for an organization of around 100 users. Normally Fortinet helps their customers with deployment and post-deployment adjustments, so you don't have any problems. If anything goes wrong, Fortinet is there to support you. 

It is straightforward for deployment

The initial setup is straightforward and only takes hours to deploy. 

Template or marketplace on Azure can be employed. The credentials one will select while doing the deployment can be used in respect of VM with Fortigate. 

The initial setup is straightforward. We didn't find it to be complex at all. 

Deployment is quick and easy. It takes a maximum of two hours to handle everything.

The initial setup was a little complicated due to our engineers working on knowledge of Checkpoint and trying to replicate the same configurations.  Hindsight finds it may have been less complicated to build the rules from the ground up rather than importing them.

The initial setup is not complex at all. It's very straightforward. It's simple.

I can't recall exactly how long the deployment process took.

We had two technicians that handled the implementation. It doesn't take a lot of people.

The initial setup is very easy.

Initial setup is very straightforward with a wizard, if needed.

We deployed the solution locally, to our server.

The initial setup is easy and took approximately six months.

The installation is very easy and user-friendly. 

The initial setup is not very complex and involved only a few settings.

The deployment took us a couple of days.

Before installation, you are able to download the solution online based on the platform you are planning to use it on. For example, if you are going to use it on ESXi, Hyper-V, or AWS, you will have a separate specific installer file for each. The installer is based on the platform you are trying to install it on.

If you have some experience with using virtual technologies or virtualizing software, it is not that complicated to do the installation. For beginners, it might get a little complex or complicated because you have to replicate the properties of a physical device in a virtual container.

The initial setup was very straightforward, and deployment did not take a long time.

The solution's initial set up was pretty complex. There were a lot of on-site VPN connections to set up, so we went through a lot of additional setup for the clients.

The deployment was pretty quicksand was probably completed in just a couple of days.

The initial setup was straightforward, and I'd rate my experience as four out of five. Depending on the environment, deployment takes between two to three months.

The initial setup process was straightforward.

While the product is easy to configure, I cannot get into specifics in regards to the initial setup. It's handled by a partner. We pay them to do the setup.

The actual installation process is pretty quick. It might take about half a day or so. 

I'd rate the experience of setting up the solution at a five out of five. 

There are bout five people that can handle the maintenance of the product across our different data centers. They are all administrators. 

We only have one person for deployment and maintenance.

It took us only two days to deploy it with our desired configurations.

The initial setup was quite straightforward. 

You The initial setup was quite straightforward. 

The initial setup was simple.

The setup period can vary. I believe it did not take us more than a week. 

To install a FortiGate is a complex task. The installation engineer need to be strong technically and familiar with FortiGate. The end user also needs to be well versed in their network and have a firm technical grasp on their business requirements and how those translate to what the firewall is capable of doing/ enhancing. This can drive a prolonged pre-install and installation process.

The first setup is easy and very simple. After that, you may require assistance implementing the new rules.

It is always complex when you migrate from a complex solution to another one.

The deployment is easy, there are no issues with the deployment of this solution.

We deploy on-premises and sometimes on a private cloud.

Initial setup was quite straightforward, as we can simply head to the required sections to apply the planned network.

The installation process is very easy with FortiGate VM. We can easily deploy it. That said, we did run into issues with some customer requirements and our engineers were forced to get involved. Occasionally, it takes too much time to configure certain aspects. However, a basic configuration is pretty easy.

This product was nearly plug and play. There are some tables and rules to make custom decisions based on our daily workloads and philosophy as an educational setting.

Setup is straightforward. I am certified in the Fortinet line of solutions. Even without this knowledge, it is easy to adjust the product to your requirements.