The installation of Fortinet FortiADC rates around six or seven out of ten in terms of difficulty.

The setup process was straightforward.

The process seems to be straightforward if one has basic skills and understands the prerequisites in the support database.

I rate Fortinet FortiADC's deployment a ten out of ten. It takes a couple of hours to complete, and it's usually deployed in a network that's already set up for application delivery. The interface is very similar to what you would see on a FortiGate firewall, and is very intuitive. Once you have set up basic networking, setting up your first VIP takes a matter of minutes - the majority of the rest of your setup time is testing the application and fail over to ensure that the apps teams are happy.

The initial setup and configuration are very easy because the solution includes a simple OS. Initial configuration takes about ten minutes for simple environments. 

It is important to assess the environment and decide what services, servers, and web applications are needed. 

The solution can be configured in router mode or one-arm mode which uses source NAT as destination NAT to send traffic to the firewall. One-arm mode is more complex and requires discussions with our engineers. 

For example, you have a website with Node.js for your programming language, Amazon S3 for your CDN, NGINX for your web server, and you use both React and reCAPTCHA. Our team meets with your developer to learn your website and OS through a multi-step process and then we configure the solution to protect everything. 

I carefully reviewed the documentation and configured the product, avoiding default settings. While the setup was complex, thorough preparation facilitated a smooth deployment. It took approximately a year to complete it.

Because, I had already used multiple products, including ADC, load balancers, and the Forti web, I didn't have any difficulty. 

I had assigned one of my proteges to do it, and he was feeling a lot of pressure because he didn't understand the documentation.

If the documentation is good, installation should be simple because you can do it if you understand the document.

I would rate the initial setup a four out of five. I am reducing one because of the documentation.

This solution requires maintenance because it has web features enabled and for the web, the vulnerability features are required. If I want to stop the zero-days, I need to update directly. I'm fairly certain. Because we aren't using it for that purpose, I'm not certain, but I'm 80 to 90 percent certain it requires those kinds of updates, the security update.

The product's setup is straightforward. The WAF took more time because we had to find a configuration that avoided a lot of false positives. We required only two people to handle the tool's deployment. 

The initial setup process is easy for me as I have experience working with FortiGate. It requires half a day to complete.

The initial setup is easy to install. The process is straightforward.

The deployment takes around two to three days, considering the installation and configuration of some applications. We can easily configure the profiles.

The initial setup was quite straightforward. You work with some network interfaces through configuration, plug it in, and have a default rule in place, and it still runs. It does the job on its own.

The initial setup is straightforward. You bring up FortiADC and you configure the interfaces, then you configure the load balancing profiles. That's it. I carry out the deployment myself and it generally takes a week or two. Deployment time is based on the customer configuration, load balancing profiles, but it generally takes a maximum of two weeks. 

The deployment plan is to get the topology of the customer. Once that is complete, we create this HLD and LLD and also the solution diagram. Those are the main things that we do before deployment. Once we have the HLD, LLD reports, then we implement within the customer environment and we test if everything works, and if everything is good it gets put into production. 

The initial setup is straightforward and depends on the number of nodes and applications. Deploying one node takes around 50 minutes.

It depends on the node and server application, source address, communication delivery control, URL, or port ID.

The solution has a relatively complex setup. 

The initial setup was not complex, but it was not simple either.

These types of machines have complexity, but with a good engineering team, it is much easier to do the jobs.

We have a team of two to deploy and maintain this solution.

The design, installation, and configuration took one week.

We had some complexity when it came to the initial setup, although I think that it was because of us, rather than the product. It took us a total of five days before we went online, which included setup and testing. This involved connecting to our backend networks, creating the VLANs, and so forth.

Overall, it was not difficult and the vendor gave us great support.

The initial setup is sort of easy but you go through a lot of screens to do it.

I think they can make it easier. The company's homework is to redesign those menus to configure with the smallest number of steps.