We always deploy it by ourselves, I think anyone with some IT experience could do it. I mean its not for Grandma but if you understand routing you can do it.

We're rolling out a four location non-profit right now that pretty much had zero network infrastructure. We're bringing our third site on out of four next week. Getting the firewall up is the easy part. It's been more of tying in their computers to the rest of the network and stuff, but eventually we're going to replace this hodgepodge of laptops and emailing files with central shares backed up and secured with the proper permissions all through the VPN.

When you look at Kerio Control, they are able to maintain it in a way that I had no problems because I was always careful with updates. I first test them on-premise before I roll it out to my customers. That's also no guarantee, but we are able to maintain it in a good way.

Implementation strategy changes per customer. Some customers have very strict policies about the sites that they can access via the Internet. Others have limited bandwidth. For example, I had a customer who could not visit some Internet sites because most of my customers have two Internet connections. I found out that connecting through the other interface wasn't a problem. It had to do this with the networks between them. It's very easy in Kerio Control to make another path where another Internet connection is used for that website.

I built a large network of freelancers over the years in the Netherlands and foreign countries to get the best solution for each customers. I am working with all types of people who are trustworthy and have good knowledge of the product. I tell my customers, "The IT world is the same as the medical world. You don't go to a heart specialist for an eye operation, and you don't go to your normal doctor for a heart operation. They're all specialists on their specific terrain." That is the way I operate for my customers.

I handle the deployment and maintenance of Kerio Control myself.

We installed the product in-house in a couple of months.

For deployment and maintenance, it takes me few hours here and there.

The outsourced contractor that we used for the setup was great. There's nothing wrong. I've been using him for a while.

I implemented it myself as it's really easy to setup and use.

I handled the implementation myself.

We do it internally. On the maintenance part, it requires patching, seeing if we want to block anything from our network, and adding more rules.

I use the Kerio Control Boxes. So, I receive it, test it, register it, and update it, then take it out to the client, reconfigure it, and tweak it. This takes three hours.

We did use an integrator. We have an IT manager.

The implementation of the solution was done in-house.

At the beginning, we did need a consultant to set up the system but now we have our own resources in our company who manage the system.

We have approximately two people that do the implementation and maintenance of the solution.

We used an in-house team.

We do use the online services Kerio provides for our implementation strategy.

The implementation and deployment is something that I do myself.

We did the implementation ourselves. It required just one person. 

We have three IT support engineers.

I am self-employed, so I work with other companies that usually do the installation of the hardware and I come in at the end to just make sure everything's all configured correctly and set up properly for Kerio configuration.

An internal team implemented the solution.

In-house.

We deployed it ourselves.

We do the implementation ourselves.

I implemented it myself.