The setup is straight out-of-the-box. Take it out of the box, run through the wizard, configure it with the settings that you should already know, and then it works and you get in online. That's the basic setup, because the Traffic Rules, by default, allow everything out and stop everything coming in. That's enough to just get online.

You then go to start defining your networks and your traffic rules. Putting multiple VLANs in there is easy. Even as it gets to be a more complex configuration, it's easy to do.

Sometimes it's time-consuming if it's a large configuration, but that's just what it is. It takes time to click boxes if it's a large network with lots of different scenarios, and to type in all the IP addresses.

But it's easy out-of-the-box for a basic configuration and still fairly easy if you've got that knowledge of the Kerio and networking. Just a little time-consuming. If there were some kind of import or bulk add, that would be nice, but that's on a wish list. It's really not that necessary.

If a customer just wants something out-of-the-box, we plug it in, make it work, and it probably takes a couple of hours, at the most. If it's a bit more complex, it might take a day. It might take longer if you don't know what you're doing.

I've always told customers that there is no fixed configuration. This thing will work and do what you want it to do. As time progresses, it evolves with the changing requirements. So we can give them a solution. They can give us some key config points telling us "Okay, we want this many networks and we want these users, and these particular rules," etc. We configure all that  in a day and test it the next day. After that, it's ongoing. They might decide, "Oh, we actually want to change the bandwidth allocation," or "We've got a new internet interface," or we want to block Facebook at a specific time. It's ongoing.

For us the initial setup is straightforward because we have been using it since the product was called WinRoute, which was 20 years ago, I believe. We pretty much know all about the firewalls and what we can do with them. So the setup for us is really easy to do.

On average, deployment of Kerio Control takes us maybe 30 minutes.

The implementation strategy depends on what the customer needs, and every customer needs something else. In general, the VPN setup is one of the things all customers need, and rules settings, open ports and closed ports, are part of some basic settings we use, but pretty much everything else is different for each customer.

The initial setup is very easy. 

We deployed it six or seven years ago, so I cannot recall the exact steps or how long it took, however, the deployment wasn't hard. 

We changed office recently, and we will need to set it up again. 

The initial setup is super straightforward. We can get a basic firewall running in under an hour. That is from opening the box  to getting it working. We tend to take it out of the box and do a little bit of preconfiguring for half an hour, maybe 45 minutes if it's a really complex multi-VLAN setup. Once you have it ready and bring it out to the customer site, then you plug it in and do a couple of final steps. We can get a sealed box to set up in under an hour.

We do have some basic guidelines that we try and use across all of our customers (minimum requirements), but because we deal with a wide range of customers, where some of our customers have four employees and others have 400, there will be minor changes. Everybody usually has a regular network, then a VLAN for guests, but sometimes our larger companies have VLANs for labs and other sections of the business: for example maybe development and admins get more rights. We always make sure the antiviruses, the IPS, filtering are running with a basic number of rules.

Don't over think the implementation. The biggest thing that you can do is start overthinking when you're setting it up, and be like, "Well, what do I have to do next?" You're probably already done. It's real simple. Anybody could take the manual home if they've never seen it before. They have a complete 30-day demo that you can download. Even if you aren't hooked into the Internet, you can log into the web GUI and look through it. It's great because it gives you an opportunity to do that and play with the product. If you're a technical person, you could take the manual home for the night, then the next day set one of these things up.

It's a very easy setup. KerioControl is very, very, very easy to set up, use and manage. A network administrator can set up KerioControl in just ten minutes. It's very easy to configure and install. I would rate KerioControl a nine out of ten for the initial setup.

For our main firewall, the setup was fairly complex at the time because we had multiple internal networks to deal with. We had test environments versus operational environments. We had a lot of rules we wanted to put in place for corporate, so it was complex. It wasn't confusing in terms of how to configure it, but it was fairly complex. 

We started off focusing on corporate first. This was the least risk and then we moved our production phases over to that as we were confident in that we were secure and connected up correctly, so to speak, or the data center configuration was the way we needed it to be. Then we did a little post-testing in the configuration, not just with the firewall and stuff, but overall with penetration testing.

The deployment didn't take very long. TechPath took care of most of it. In terms of the site to site stuff, we do that fairly regularly. It might take an hour to configure devices, but it's not onerous. You've just got to make sure you get the settings right. The setup required a few engineers from their end, myself, and another employee. 

We do maintenance once a month and it requires one person. It doesn't quite a lot of maintenance because we just give it a courtesy reboot more than anything like we do with a lot of our gear. We just make sure that the updates are up to date, from time to time.

The process was pretty straightforward. Something that I expected to take days to weeks took about two or three hours.

A basic initial setup is very simple and straightforward. They offer a straightforward set of rules to make it work, then you can create all the rules you need for the customer depending on their demands. It can do almost anything.

The deployment time frame varies. For example, if I am deploying to a shopping mall, that shopping mall has all kinds of offices. Every office has its own demands regarding the IP system that they use. Every shop has its own software supply and concepts. Sometimes things get complex, then I start from scratch to make sure everything is maintainable, but this is very easy in Kerio Control if you know how to do your job.

Because of the coronavirus, for people who want to work at home, it is very easy to set up VPN Clients because that is a piece of cake.

The solution was easy to deploy. Documentation was available online so that we could install it easily.

The solution is easy to implement and can be installed in less than ten minutes.

It has a wizard to sort of get it up and running very quickly. I think I did start with that, then went into the manual configuration for setting up VLANs and DHCP scopes. They were fairly straightforward to set up. 

It's a product that you can get up and running pretty quickly. Then, if you want to get into advanced configuration, that's what takes a bit more time.

Out-of-the-box, I had something running in an hour or two, but that's probably because I've been using the product for quite a few years. I know what to look for. But as for the advanced configuration, that's days of work. It's ongoing with the administration and tuning the network. I spend maybe a couple of hours a month just making sure everything is configured and working correctly. The logs are pretty good too. It's good to keep an eye on the logs as it gives you an indication if anything's wrong or if things are going haywire.

You need to have a pretty good idea of how you want to structure unit work and what you want your network to do, especially when you want to set up things like authentication. You need to preplan your subnets and IP address ranges for different users so you can then map them to the user accounts. If you're going to a new organization and setting this up, then there is a bit of work in planning all that and what you want the device to do.

On average, it takes around one to two hours on a small to medium business to set it up. But it's totally dependent on their applications and that can vary up to quite a few hours if they've got some complex application issues. Typically, it's because I have to wait on getting responses from vendors. So we go out and we put in a default setup and modify off of that.

Our default setup pretty much locks their network up to only having HTTP, it turns off FTP and things of that nature. We have a pretty secure default setup and then we go open things.

After you've done it a few times it's pretty smooth.

The product's setup is straightforward. 

I've been with the company a little over three years now, but when I came in as general manager it was already in use. The upgrade is the closest that I've been to a deployment.

From start to finish, when doing the upgrade, we were back up in an hour, including the issue we had. Our IT guy let us know what was going on and that there was a series of events he had to do and he did them and we were good to go.

The initial setup is easy. I know what I want to configure so it's easy, no problem at all. 

The biggest problem I have is using it as a container on a virtual machine. You have to connect your hardware network cards to the internal virtual machine. That's a problem that Kerio won't be able to solve because it's the environment I have to create to let Kerio work in the way I work, and that is probably different than most users. But if you use it on a simple PC, it's no problem at all.

I reinstalled it recently and it took me about half an hour, and part of that was getting backups right, etc.

As for an implementation strategy, I changed the system my Kerio was installed on, so I first did a trial-install to figure out if everything worked. After that, when I did the actual production install, it was done very fast because I had tried it out before.

It's not complex at all, however I have to modify the virtual appliance because it came with the E1000 virtual network adapter. I removed them and put VMXNet3 in instead. I also had to change the amount of default configured RAM. It's now working great.

The fact that the setup is so easy is one of the solution's great selling points. It's straightforward. It's not complex at all.

It only takes one person to deploy and maintain the solution. The deployment itself only takes about an hour or two. Looking at the branches, it may just be 10-15 minutes of work for them. It's pretty quick. Of course, it depends on how many walls. A super basic setup is 10-15 minutes, however, if you have to put in a lot of rules, it will take longer because that process takes time.

The initial setup is pretty good. The guys are used to it now. They've done a fair number of machines and they're very used to it.

It has become familiar and they're consistent from one model to another. The instructions are straightforward and a good tech should have no problem with it at all. The thing is that they're not a home machine, they're for business. If it has a tech working on it is no problem at all. It's quite simple.

An average deployment takes two and a half hours. 

Network engineers set it up. Even one of our web developers has set up some of them. They have been very happy with training other people to do them. They don't have any problems. It's quite simple. The engineer was the first one to start working with Kerio back when we took them on, and he found that even in the beginning, from learning on his own, it only took him about four to eight machines to feel confident that he could do it without having to follow the instructions every time.

The size of the companies we work with vary. We call them medium-size, but some of them are only one location with 5 to 20 employees. We host a lot of our e-commerce systems and clients have those on their machines so that when the e-commerce inquiries come in, they go through that router. They become a medium-sized business very quickly because of the amount of business they're doing.

Kerio is a good solution for companies of this size. It comes down to the same thing, reliable, cost-effective, the VPN connections are good for the security between the e-commerce sites. Our eCommerce site is dynamic, so it's connected between the customers' inventory, warehousing, shipping, and billing system, directly to the e-commerce site. It makes it a lot tighter and more security is required because they are connecting directly to the customers' business machines, as well as just e-commerce hosted sites. Reliability and security are very highly needed because it does run their e-commerce sites. 

The initial setup is straightforward for us now because we've done it for so long. The other side of it is that there haven't been a lot of changes per se. There have been tweaks. The consistency of the platform has pretty much stayed the same. So while they have optimized certain components of it, it's kind of like Microsoft Word. You could go back to a version of Microsoft Word 10 years ago and know exactly how to use it because everything's going to be in the same place. It's just an evolution of the platform.

It takes around an hour and a half to license and configure.

We have a uniform deployment process and then that's followed by adjustments based on the client's specific requirements. They may have more LAN connections than somebody else, or they may have less of a need for additional VLANs. It's on a case by case basis. But I would say 95% of everything that we do is standardized.

I'm not the one that actually implements it. Full disclosure, I order the device, I get the device, I license the device, I update the device and then at that point in time, I have one of the engineers come remotely into the unit and then they do the final configuration.

It is straightforward. It is easy to configure.

The initial setup is straightforward. You receive a box and then you receive the activation keys. When you receive the activation keys, it will work fine. Without the activation keys, your subscription for firewall, antivirus, and web filter, is not going to work.

If you are doing a fresh installation without the VPN, you have to set up all your routers on each different location to have a site-to-site VPN. However, if you are migrating from a firewall to Kerio Control, you have to migrate the users, DHCPs, and static IPs, that you want to have on the devices to keep you from losing service. For up to a five-site location, it could take approximately one hour for each location to set up the firewalls.

Given that it's a Linux deployment, the support it offered, like giving you a Hyper-V client out-of-the-box, is fantastic. It's a really clever idea because you're not then left with a painful configuration of spinning up some sort of Linux host and then trying to do an installation. The fact that it comes pre-packaged with Hyper-V images was a very smart and clever move because that made it a lot easier to get it going if you like. Getting that up and running was quick, it was just a configuration, and finding the right configuration was the hardest part.

The deployment was less than half an hour. It was very quick to get it up and running and get it operational. It was just fine-tuning that configuration to suit my environment that took the time, which I would expect of any device, no device is going to come out-of-the-box and just work like magic unless you've got a really simple environment. Whereas I've got a home environment, where it's just me as a small business, but I've got that many servers and hosts running.

Our strategy was to take it out-of-the-box and get it working.

The setup was pretty easy. The external remote control was really good and simple. It gave extra manageability on the road which was good. It was pretty straightforward.

In terms of maintenance, it's just me. In terms of my time, it doesn't take much time at all. I'll hardly make any changes to it. Now it's running fine. The only next thing I'll be doing is trying out the HOA.

The initial setup was pretty straightforward and intuitive. I just need to have some of the information of my clients in front of me. The only thing would be to tweak bug filters and content filters a bit, depending upon your client requirements. However, getting it up and running, it's pretty straightforward. 

There are wizards. You can just follow the wizard, pay attention, and be all right.

I haven't used all the features yet, e.g., I still don't integrate Active Directory.

The initial setup is a bit complex, but it was fine for our IT department. Deployment took around one month and it only required one person. One person works on it, and it takes him about two or three weeks. Maintenance requires two people.

We hired a guy to do the initial set up for us. I think he was a Kerio reseller and we used him for consultancy before it started and then he actually did the work on the Kerio as well, and the network in general.

Our experience with him was excellent. We've used him a couple of times since. He's brilliant. His knowledge of everything is incredible. We tried to do it all ourselves at first, but he came in and knew exactly what the problems were. Something that had taken us about four days, he did in five minutes. He's just incredibly knowledgeable about everything to do with networks: Cisco, Kerio, everything.

I've set up another one since, for the same company. I just copied the configuration file of the one and put it straight onto the other. They're in separate buildings, but they wanted them exactly the same so it was really easy.

That deployment took an hour, but it was because we already had one set up.

As for deployment and maintenance of these solutions we generally need just one person: me.

The initial setup was straightforward, with the exception of the VLANs, and setting up a second LAN. Other than that, it was straightforward.

The deployment took two hours. 

The IT company went through and showed me all of the settings and gave me a tutorial on which features I needed to use and how to turn them on and what they meant. As far as the rest of our office staff is concerned, they just needed the VPN protocol setup. I was able to do that on my own because that was really straightforward and easy.

They set it up for me. They plugged it in for me and then explained all of the features to me and helped me set up some of the features. I was then able to easily find videos online and some instructions to set up other features that I wanted, like content filtering.

Having seen the process, I could easily do it again without their help. I just needed a little bit of a push from them.

The initial setup of KerioControl is straightforward.

For the initial setup, it walks you through a wizard. I've just never used that. But the wizard can set up a very basic bare bones, don't let anything in kind of a setup, which works. My setup is more complex. I have VPNs and tunnels. Any IP on my network has to be logged in, in order to get out. Mine is more of a complex setup. The ease of setup is pretty easy if you use the wizard. It just asks you a few questions and that's it. It's a bit more complex when you do it yourself. 

The deployment took a couple of hours. 

The initial setup was complex. The system itself isn't complex in terms of actually using it. It is user-friendly. It is complex in terms of the capacity to control the situation.

We didn't spend a lot of time on the deployment. In the beginning, we did need to dedicate some time to implement the infrastructure internally. In terms of the operations and maintenance, we don't spend a lot of time on it.

It requires two people for maintenance.

The initial setup was simple, it was standard. It only takes a few minutes.

The initial setup was very simple and took one or two days - it's on a Linux-based machine, so we just got the setup files and installed it. 

The initial setup is straightforward. It is easy to install. You just put in a memory stick and boot it up. Or, you just start up the device and follow the on-screen prompts. The deployment takes five minutes.

The initial setup for this solution is very easy.

As I said, if there were best practices or a template, the setup would be a lot easier because you start and then you change the setup according to what you think is right. But later on, when you encounter problems and look in the documentation, you see that another way is better. That was a bit of a problem when setting up. It all works, but in managing or adding rules, for example, or we just didn't do it properly. It was a bit of trial and error and that was a problem. It's too much trial and error when you start.

Deployment time, for some customers, is fairly quick. A basic setup can be up and running in 15 or 30 minutes. With other customers that have a lot of rules we do testing so it could take three or four hours.

For our implementation strategy, we just look at what the client wants. For some clients, we have a basic template now, where we always use a backup from an existing Kerio. If it's a new customer, we check if we have an existing Kerio that's pretty much the same, or we just do it from scratch if there aren't too many rules or networking behind it.

The installation of the product is very easy. We have five technical engineers on our team for maintenance and troubleshooting. 

The deployment of Kerio Control was easy and user-friendly. We have no problems deploying the Kerio Control, Kerio Portal, and Kerio Connect for our customers.

The initial setup is straightforward. It's a bit tricky because I do it a lot, but it's pretty straightforward. It has a Wizard if you need it, but I don't need it anymore. I know what I'm doing. I find it quite easy to set up.

A basic deployment takes an hour. Just the box standards are set out for everybody, and then if they need something specific, we'll add it in afterward. But a straightforward, standard, basic setup takes about an hour.

We have a unified implementation strategy that we start with and then we tweak it if need be. We don't use MyKerio to put a standard implementation across all of them.

Our standard implementation strategy is to implement dual internet connections, standards, and standard traffic rules with VPN access.

The setup of Kerio Control is very straightforward. The initial implementation is about three hours, with various points of review. We are a managed service provider, so there are ongoing reviews and adjustments for the clients.

The initial setup was straightforward. It's the most user-friendly UTM out there. The deployment was very fast, less than half a day.

The installation is straightforward. We have done this many times. 

The initial installation's level of difficulty all depends on the requirements of the customer. Some customers just want it there so that they can actually monitor and see the traffic usage, and, if necessary, they can go and speak to people and ask them to stop using up so much data. Some clients use it more as a deterrent and just as a way of monitoring what's going on. Other clients like even more control, which can make it a bit more complicated. They want to put in quotas for users and block certain sites, which is possible, and just a bit more work. It will all depend on clients.

Deployment typically can be done within one day. However, a lot of time users may be upgrading the whole network with wifi switches. Everything gets built together. For us, we're trading our gateway and our networks on board. It shouldn't take more than a few days for a full network installation.

I found the initial setup to be easy. 

The initial setup is pretty straightforward. I learned this product on the job, and I never got any hands-on training. I just went to YouTube and oriented myself with it, and then I set it up quickly.

Simple initial setup.

The installation is straightforward.

The initial setup was straightforward. We deployed Hyper-V Appliances and everything worked as it should. Connecting the Appliances to MyKerio was pretty simple and hassle free.

It was pretty straightforward. It took about an hour.

This initial setup is straightforward. It is a no brainer, and anybody can get in there and just do it. They deployment takes maybe half an hour, if that.

It all depends on what they are requesting. It's not just "one size fits all". Some boats have a LAN they need set up, while some boats don't. We set up the unit sources and assign different ports.

These days they have a dedicated internet port, and they've got four or five land ports. We'll take one or two of the land ports and assign them to the Internet port, so that way they'll have a ship-to-shore connection, as well as a VSAT (Very small aperture terminal) connection. We'll also have another device with a cell router coming into the third connection, so that way they can switch between the three Internet connections when they need to.

For example, if they are out at sea they're going to use the VSAT, but if they are in the port then they will either use the ship-to-shore Wi-Fi, or the cellular connection, to save money.

We have eight technicians on site, but it only takes one person to handle the deployment. The maintenance is quick; we can log in remotely and update it if we need to. I prefer to be on site for this in case something goes wrong, but nine times out of ten everything is just fine.

The initial setup was straightforward. The deployment took one week. 

Setup is simple. The Kerio interface is very intuitive.