The initial setup was straightforward. Before deploying Meraki MX, we did a POC for three months, and this POC was successful. In fact, we were given only 60 days, but we took over 90 days to do a complete assessment to see whether this fulfills our needs. When we were sure that this is the right solution for us, we deployed it across the group.

The initial setup is easy and maintenance is minimal.

I rate the ease of setup a seven out of ten. The product is a cloud-based solution, and it has a cloud-based controller. The deployment took a few hours. A single site can be deployed in a maximum of four hours.

The initial setup is straightforward. When we are rolling stuff out, it is always fine. When we have redundancy or multiple networks to configure, that takes time and is tedious. However, the setup itself is not complex. There is plenty of documentation on it.

There are two schools of thought on implementation strategy: 

1. We clone out from a very similar organization, then try to mirror it and switch the hardware, e.g., the actual inventory in the organization. 
2. We build a new org from the ground up, if it's a small organization, then we just throw Meraki in, and we are good. I find it is easy. There is a standard practice that we are developing. It is so easy that once you have done it once, then you can train someone the first time that they do it. It wouldn't be something you would need documentation to reference, because of how simple it is. It takes one to three hours to set up. If it is a larger organization, then we will take three hours and refine things. If it is one site, then it is about an hour, just to make sure we are not screwing anything up.

The initial setup is very complex. We need some expertise to set it up completely, including the configurations.

The initial setup was pretty easy and pretty simple.

The setup is straightforward.

One single person can deploy the tool for all the branches. Only two people are managing Meraki, and they are from the same team managing Citrix SD-WAN.

Meraki MX is simple to deploy and manage. You only need to plug it in and configure it.

Since Meraki MX has a graphical user interface, its initial setup is pretty straightforward. However, you need either a consultant or a technical expert to install the solution.

The initial setup is quite straightforward.

Meraki MX's initial setup is very easy, and you can easily install the solution.

Meraki MX has a straightforward setup.

The product's initial setup phase is very easy. It has a very good web interface that is easy to manage and operate.

The solution is deployed on an on-premises model.

The deployment was carried out in two sites, which took around two days to complete.

The initial setup for Meraki MX is very straightforward.

Deploying MX is easy. It takes maybe half an hour. I didn't need any support. I could do it all myself.

The initial deployment was very straightforward and simple. The solution doesn't require much knowledge and the customer support is readily available. We don't have to do any maintenance at all, the vendor notifies us of scheduled firmware updates and they handle everything. 

Setup requires deploying the firewall to the internet, setting up the inside addressing, and possibly a DHCP scope or VLANs.

The solution's setup is straightforward and easier than Cisco's. There is a subscription and you need to activate it. 

It was straightforward. It is easy to configure. Meraki dashboard is intuitive. Of course, you need to know about networking, but it is intuitive and very fast to do the initial configuration. It took two hours.

In terms of the implementation strategy, we planned the network, the addresses, and the segmentation before starting the configuration. We planned the ports that should be opened and the ports that must be closed for security. We also planned the rules of the firewall.

We just configured Meraki through the dashboard. In switches, we configured the segmentation and the addresses. In Meraki, we configured the rules of content filtering. We then blocked the required things. The VPN configuration is supposed to be easy, but the problem is that if the VPN goes down when we are using it, it is too complex to bring it up.

Its implementation is very new, and it was done around one month or two months ago. At this time, no maintenance is necessary. If required, our administrators or a third party can take care of maintenance. Once configured, there is no need to change anything. Its usability is very good, and it is not common to make any changes or do any maintenance. It just works.

The initial setup requires basic technical knowledge. It is easy to install. You can use the Zero Touch deployment method if your organization is spread across multiple locations worldwide.

The product's initial setup phase was simple, considering how Meraki's documentation is very intuitive, which explains how to use the platform, its configuration capabilities, and its administration.

The solution is deployed on the private cloud.

The initial setup is easy via the cloud portal, primarily because managed support is needed for internet access. Without this, the direct configuration of the box becomes unattainable.The duration required is significantly shorter compared to alternatives. Occasionally, when dealing with a larger number of branches, like fifty or more, we managed to complete the implementation within 14 days. In cases involving complex processes and discussions, additional time might be necessary. However, once the system is set up and connected to the cloud, other configurations can be done within an eight-hour timeframe.

Like any new equipment or networking gear, it did take a bit of time to learn the ins and outs and limitations of the Meraki gear. It’s not the Cisco CLI console that I was used to, so it was different to learn.

The initial setup is complicated when the Internet is unavailable. However, it is easy to configure and takes two years to complete.

The solution is easy to set up. If you are familiar with it, it will take only a few hours to complete the deployment.

The initial setup was easy. Some features need more investigation (client VPN). SDWAN is great. Some more training on how to set something up would help like VLAN. Even if it is that easy to configure it, the basic concepts might be missing.

Setup is rather easy but with templates or using an existing MX as a template to create a new MX configuration setup becomes even easier.

I have never had a problem setting up a Meraki device, other than one time when the unit was dead on arrival. Once they are set up, they work fine.

The initial setup of the Meraki firewall was straightforward. Deployment took a few days. 

It is easy to install. It took us one hour to deploy it.

You only need to know about firewalls, content filtering, and networking.

The initial setup is pretty straightforward.

Initial setup was straightforward and extremely easy.

It's very simple.

It's easy to set up and configure.

It was a very small project and it only took four or five minutes to install.

Four or five switches can be deployed in a day.

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

The initial setup was straightforward. The deployment took around four hours. 

The installation is straightforward. With Cisco Meraki, it takes only half-an-hour. For very specific, customized rules that some clients want it takes more time. The standard firewall working with regular rules would take one-hour maximum.

The initial setup is straightforward for a simple firewall. Deployment takes no more than one working day.  For deployment, you only need a technician, a well-trained technician to go onsite and just install it. The rest could be supported online, if they need on-site support it's very rare.

The initial setup was very quick and straightforward.

The initial setup for me was straightforward and was not that difficult. The first time, it took a bit, but after that, I configured templates so it made it faster. I can roll out a firewall in five minutes.

The basic configuration takes 10-15 minutes which is great. 

The initial setup was very straightforward. Deployment took roughly two hours, max.

The initial setup was simple.

The initial setup is simple. Our deployment took around 30 minutes.

I really didn't experience any areas of complexity. The most complex part of the initial setup was setting up a conference camera. We host a lot of international board meetings that require video calling. 

Meraki setup is really easy.

The initial setup can be complex. It usually depends on the scenario. The deployment usually takes half a day, but it again depends on the scenario.

It is very fast to implement and very easy to configure.

The initial setup was very straightforward. Deployment takes less than one day.