Initially, we required an integrator. There was a vendor who deployed this service, but after the first-time implementation, it was very easy because it's a very quick thing to do. We did not require any assistance from any of the vendors. 

We have got in-house resources. When we get a new device, we don't require any implementation or installation support. We do it ourselves. It's very simple. We've been doing this deployment across the group. Initially, we had about 30 sites. Now, we have 40 sites, and the number of sites is increasing.  

The number of people required for deployment depends on the customer’s number of sites.

For Meraki MX, it takes just one person to set it up. If we are training someone, then it takes two people.

We took almost a day to deploy the solution because we got help from a partner. The partners were helpful. In India, vendors are well-trained in Cisco products. Also, Cisco employees help us set up the solution on call. They help us not only with the setup but also with anything critical that comes up.

The time taken for deployment depends on the environment. In some cases, it takes just a couple of hours. It could take a lot longer if it’s a larger environment with multiple locations. Usually, it can be done on the same day. We've got hundreds of clients, so we have a team focusing on upgrades and maintenance. For an individual environment, especially a smaller one, the maintenance can easily be done by one person. We need a team to maintain the tool for a medium or enterprise-level company. If it's only a couple of firewalls or within ten or twenty, it's pretty easy to maintain it. It's all cloud-based, so it's really simple.

The implementation can be done via Meraki's central portal. If we give access to any device, like MR or MX, it automatically reaches the portal and can be onboarded within five minutes.

We did the implementation of the solution in-house.

Meraki MX can be typically deployed within one to two hours. We implemented the solution through an in-house team.

You need to know the business use case for which you want to use the solution. If you want to use the solution for load balancing, you need to specify the use cases for which you want to use it and all that will be considered.

Once you know the dashboard serial number and license key, you can configure the dashboard before getting the devices and then add the devices. Later, you just need to plug in these devices with the internet, and then you can easily configure it.

If you get four hours, you can take a small downtime from the customer and install the solution very easily. Even the updates will take over the night. So there is no manpower or time required to do these activities. You can initiate the patches and all kinds of downtime activities from home.

One or two people are needed for the solution's deployment. The solution's maintenance is very easy and not difficult at all.

We implemented in-house with just one person.

We used a third party to help with its deployment. Our experience with them was medium. 

Other provider did not jump on Meraki as I would expect. Most of them do not support nor use Meraki. It is difficult to find support provider to help if there is a problem.

We perform all Meraki implementations in-house.

We bought Meraki from a Greek company called Dataways. They made an initial configuration of the Meraki device.

You need a consultant or integrator only when you have a complex installation. We are an integrator and one of the larger resellers of Meraki. We have about 50 people, and we also have a 24/7 service desk.

I deployed this product, although I relied a lot on Cisco support when I set it up.

No need for a vendor team to implement. Used in-house expertise.

We did it in house, across five offices and the data center.

I deployed it myself. 

We are certified by Cisco. As we are certified technicians we do the installations. We do it with a two-person crew deployed to our clients.

I did the implementation myself. I oversee the maintenance as well.

I did the setup by myself. Sometimes I referred back to the integrator for support if I need to for a specific tool or policy.