We used a third party in conjunction with higher level Fortinet support for deployment. We had to get a certificate and the third party helped us with that, and then we had to talk with Microsoft too, so it was tricky.

During setup it was hard to make sure that the solution was doing what it was supposed to do. There were different factors that made it difficult, but it might have been because the person who was trying to implement the solution didn't understand it fully. There were some inconsistencies in standards for active directory account names, for example, usually you'd have first initial, last name, and that would be your domain name. However, we had some older users, myself included, that had a different format that included their department name, like 46-JMoore for example, and the authenticator didn't understand that. You'd have to tell the user, "Okay, you're using this old formatting for your username, but you need to put it in differently so the authenticator can understand it." It wasn't really the authenticator's problem, but more so had to do with fitting the environment into the authenticator's configuration.

We deploy the solution in-house. Our team supports our clients and manages their environment.

Our company provides professional software development services to different clients.

The deployment time is variable. Due to occasional weaknesses in the API, deployment time can vary. Sometimes it's easy, and sometimes not due to these factors.
We managed the deployment ourselves. In another business unit of my company, we're integrators for this tool. We handle the sale and implementation projects, so we have the required competencies.

For example, we need to set up the network and integrate it with the desired resolution for the deployment process. Then, deploy the client zone to the users' mobile phones, enabling them to use virtual authentication configurations.

The solution is deployed both on-prem and cloud. The staff needed includes engineers, developers, and sometimes even technical support for custom API creation and customer designations.

In-house engineers, properly trained, are responsible for deployment and maintenance.

We provide implementation and maintenance support for all our customers.

It was easy for me, but I had to read the documents about LDAP authentication. I did an in-house self-configuration. It was time-consuming.

We design and then, Fortinet team will implement.

We did the deployment in-house. 

We did the implementation of Fortinet FortiAuthenticator in-house and we have two people for the maintenance.

We used a team of three people for deployment and maintenance.

It is quite straightforward to set up the FortiAuthenticator. We mainly deploy as a virtual machine. An OVF file is provided by Fortinet and you just simply compile the file in the VMware environment. Upon simple configuration, such as IP address and default gateway, you can access the web GUI and do any configuration, as you like.

We had a system integrator to assist us with the implementation and deployment. The implementation partner does not have sufficient expertise.

One or two engineers can implement it.

We had certified Fortinet engineers assist us with the initial implementation. They handled the setup and configurations as well.

We handled the implementation ourselves.