Cisco Meraki Wireless LAN Reviews

We have been using the latest versions of Cisco Meraki Wireless LAN because we were deploying them in a new restaurant, we had all new solutions. The only difference was that because of COVID everyone has devices on backorder and we had to compare different Meraki devices. We had to redesign our plans based on what was in stock in the wholesaler inventory. They were all enterprise-level Meraki devices.

The deployment is on-premise but we manage the solution from the cloud.

The owner of the restaurant where Cisco Meraki Wireless LAN was implemented wanted to receive very detailed analytics and metrics based on the customer traffic that he would have. We wanted to capture the information from the customers either walking outside of the restaurant or enjoying the food inside, then adjust his marketing accordingly.

Cisco Meraki Wireless LAN has improved our organization by providing us with a sense of security. When anyone is connected wirelessly, you're not going to get compromised. You're not going to receive a bunch of pop-up ads, and the beneficial functionality of Cisco Meraki Wireless LAN has been great. It has strong encryption and since my customer has a fast internet speed, they have good wireless speed.  The owner was extremely happy with the solution, not only the functionality, the daily use, but the analytics and metrics that he wanted were available.

The settings of Cisco Meraki Wireless LAN can be very granular. You can lock down and block devices with the controls. For example, we have four different wireless settings, such as guest, employee, security, and backup. For example, the settings for the employees, if they use laptops, they're required to have certain settings, such as an antivirus installed. If they do not then Cisco Meraki Wireless LAN will not let them connect. This is very good protection because the network works on the bringing your own device(BYOD) principle. It's a BYOD environment now, and you also don't want them to bring infection into the environment because these people are connecting to the LAN via wireless connections. We have to be careful because we're managing it, we have to be very strict with regards to the rules and policies.

The way Cisco Meraki Wireless LAN groups certain things, as far as the devices for either monitoring and or configuring them should be done better. They should be grouped a little bit differently because if I want to configure something, a different setting on an SSID, I have to go to their specific area where I would have thought it should be clumped as a dropdown menu in another area.

It would be a benefit for Cisco to make an application for mobile devices. For example, an Apple or Android application for either a smartphone or a tablet. It would be useful to log in and use the dashboards to have a central control panel. It could be used to allow alerts to be received quickly if they went to mobiles devices. 10 times out of 10, you will have access to your phone before you have any other device on you. For example, one of the managed services that I use is Continuum which was purchased by ConnectWise making it a ConnectWise solution. They have an application for alerts that I can click on, and it will open the application on my phone. I can go in and see the alerts and trouble tickets and receive information, such as which client it is, which computer, server, or laptop. At that point, I can either click on another link and remote into it, or I can call the customer and notify them of the alert and that they could experience some delay or lag or problem with the internet connection because of their network card on their laptop. I do not have time to sit in front of the dashboard and if the alerts could be managed from a mobile device that would be a big help. 

You could spend all day looking at the bandwidth, or who is potentially looking at what in the network. Once you know what to lock down from the users, such as social media sites. If you have the employees on a separate wireless network, you can lock down all social media, to where they have no access to the social media. Additionally, you can block eBay, or anywhere you can purchase from, no porn, no adult content, it works very well wirelessly. It is a good solution.

I am not the first to think about additional features or improvements. They most likely have a lot of features in the works. Since I have many clients now I'll subscript to their next newsletter that they put out. They may have a mobile application coming out in the near future.

I have used Cisco Meraki Wireless LAN for approximately 10 years.

I have not had any issues with the stability of the Cisco Meraki Wireless LAN. I am extremely satisfied with its performance and quality.

The stability of Cisco Meraki Wireless LAN has been great. I am highly satisfied.

I have contacted the support from Cisco. Recently I couldn't find where to do something on one of the main Cisco switches. It was a PoE switch, and I sent an email out to the support at approximately 10:00 and I received an email response early morning hours at approximately 5:00. I was very happy. They asked me a couple of questions, and then when I tried what they'd suggested that I should try, it worked. It was only one little setting that I missed, that I didn't check, and everything came up fine. Then I replied to the email, and they closed the ticket.

I'm very happy with their support. Additionally, they said in the email, if I have a critical issue that needs a more immediate response we can call a number to receive immediate support. I thought this was great. We are an enterprise client of Cisco because the solutions that we have purchased allow us this extra immediate service. 

The initial setup of Cisco Meraki Wireless LAN was straightforward. You create the network, you add in the license, it pulls in all the devices, then you only need to rename the devices to whatever you want. What I enjoy are the ones I always request or require is a floor plan from the architect. I upload the floor plan, and I place it on the map, similar to a Google map. I place where all the devices are located within that floor plan on the map, and I provide that as documentation to the clients and they love it.

I would rate Cisco Meraki Wireless LAN implementation a five out of five.

We do the implementation, maintenance, and support of Cisco Meraki Wireless LAN. You set the solution up and it runs, it is pretty simple to manage. 

We are very particular with email alerts when we receive them. When we receive the alerts, we will let the client know that on a particular evening or morning during the weekday or weekend, or early morning hours, we will be sending a firmware update or an update for the software. We do it in a way that does not affect them.

If everyone were to see all the features, utilities, and tools that can be used and the reporting that Cisco Meraki Wireless LAN can provide, I think they would be able to better justify the cost. Although, it's still a little bit on the pricey side, and for me to explain everything in plain English to a non-tech person would take a while. 

It would take me upwards of an hour because I would be a very big cheerleader for this solution. I'm an extreme fanatic about Cisco Meraki Wireless LAN. That's why I wanted to show them the comparison between the Ubiquiti and the Ruckus solutions next to Cisco, and the biggest hesitation is the price of the solution, which includes the licensing, and renewal. Otherwise, Ubiquiti would win, but the problem with Ubiquiti is, they don't have the granular type of customization of reporting that the owner of the restaurant wanted.  I'm sure that once he gets started and he gets people in there, he is going to see that it is worth it. 

He won't have a problem with it moving forward, but the price was a tough sell. We thought at first we weren't going to get it. We used a report from PeerSpot for two clients to compare solutions. One of the two we did receive as a client and the other one we did not. I feel that the client that we did not sell Cisco Meraki Wireless LAN to will come back to us because they were focused on purchasing a cheap solution. However, as they say, you get what you pay for. They might be calling us back in a month to potentially change solutions.

The customer we implemented Cisco Meraki Wireless LAN for found the reporting invaluable, and it paid for the cost of the implementation of the wireless devices.

My client has made comments on the price, indicating it is expensive, however you do receive a lot for the money that you did spend on the solution. The price of the annual renewal of the licensing of Cisco Meraki Wireless LAN is a little high. We wish the price would drop.

I have looked at our parts and labor sheet, for a three-year license for three access points and the A port PoE switch, will cost approximately $1,200. It is approximately $400 a year for licensing for Cisco Meraki Wireless LAN.

In the beginning, I had to find and figure out where to find certain functions. The logistics of where things are configured or located in the dashboard can be difficult to find, it could be more intuitive. It's not a perfect solution. However, if money weren't an object, I would suggest that everyone should use a Cisco Meraki Wireless LAN solution.

My advice to those that have not used a Cisco Meraki Wireless LAN, I would recommend them to check the community forums that are available and ask questions there. They're very helpful. There are several YouTube videos that can be used to receive a good overview. They do provide useful documentation with the solution, but they tell you to go online to this specific link and it'll explain in great details step by step what you have to do. 

There are consultants, such as myself, that have YouTube channels. They show you step by step how to set up your first network from start to finish, what to change, what settings to use, what not to use, and depending on the scenario, what changes you need to make, how to use the dashboard, how to add licenses to assigned products. How to create a splash page for a guest login and if you want them to click through, and after redirect them to that client's website before they click on and connect to the internet and go someplace else. There are a lot of other outside non-Cisco vendors and consultants that put a lot of information out there. I've always told people, Google and YouTube are your best friends.

I grew up where, to find something, you would have to physically go to the library, and you had to go through the Rolodex card catalog file to find a book. The process would take a couple of hours, with the technology today the process now can take a couple of seconds, and you can download a digital copy of the book and read it on your Kindle, iPad, or whatever device you choose. 

Cisco is very picky about their solutions, they strive for accuracy and non-buggy software. I commend them for that, and there's a price to pay for research and design.

I rate Cisco Meraki Wireless LAN a ten out of ten.

At World Vision, we run most of our applications in the cloud. So most of the people need to have a strong and stable internet connection. Our offices are kind of in a box with not much infrastructure in terms of the LAN. So I deploy Meraki WIFI access points and they become the connection to the internet so that people can get to the systems that they use wherever they are.

We have a centralized dashboard in the cloud. I send the access point somewhere and I configure it remotely on cloud. Ours is on premise, managed from the Meraki dashboard itself. So I could be anywhere and manage it, but we are deploying them for World Vision offices across the country.

It benefits the organization and my work because we do not have a lot of IT guys here. Before, we used to manually deploy wireless and I needed to drive miles and miles across the country to configure an access point. When it goes off, we lose connection to it. I still need to drive there, but these days Meraki has reduced the workload because I can just send it wherever it is going and configure it wherever I am. I can be in many places at once.

First of all, it helps with the workload, but also with the flexibility in that I can do everything remotely. I can view when the app is off, I can view when it's on, when it's acting up, when it's fully loaded, I can do the RF setting, even on my phone right now, in case there is any issue. This is what we found good about Meraki.

I like the fact that the deployment is so easy. Deploying and setting up a network have become so easy - like 1, 2, 3 steps and you are up and running, whereas originally we needed to log into the app and all those things. Now, it is more robust for me to deploy networks. And because of the field we are in where offices open up and others close, it helps my turnaround time to deploy these networks for the customers.

In terms of anything to improve, recently I have seen that the Meraki access point, maybe due to congestion, just kicks off my customers, mostly when they are in Zoom meetings or Teams meetings and they have to reconnect. It is not a good thing. I have been on the communities trying to find solutions, but I think Meraki is working around the clock to fix that bug. Other than that, I think it's okay. We moved to WIFI Fix, so I think that the improvements are there. They are already in R&D. So I look forward to more good things coming from Meraki.

It just kicks them off, because one minute they are connected and then they are completely dropped, and then after a minute or two, we connect back. I think it is an AP issue that Meraki might need to take a look at. If anyone has some hack around that, I would be interested in knowing what it is.

In terms of what I would like to see in the next release, for starters, I would like an air marshal not to interrupt service. I would like to be able to do a separate scan of the network while the service is still running. It is important for me to know what environment I am working in. But every time I do that, it tends to have the IP go off and everyone starts complaining. That would be a feature that I would like to be added.

I have been using Cisco Meraki Wireless LAN for about three years.

In terms of stability, it performs until lately, when it started to kick off my people. But it is not so often. It is during peak hours, like Monday mornings when we have so many Zoom meetings and then maybe Wednesdays when it is too busy. Other than that, it has been stable. We have been okay for the past two and a half years.

The scalability is as I want it to be. The only thing I need to do is add a few licenses here and there, but it is scalable. I get a new device, add it on the dashboard, and I don't need to pay dashboard fees. Not too bad for me. It is scalable enough. I wouldn't want that to be changed.

As a rough estimate, we are about 1,200 users. That is the breadth of the network across the country. We have about 30 offices, with some more populated than others.

I do the deployment and maintenance myself - only one person.

We use it everyday. Every time someone walks into the office, they are using the Meraki Wireless at that point to connect to the internet and everyone who walks in the office needs the internet to work. It is being used 24/7.

I have spoken to support, but not too many times because we have not had that many issues. But I have contacted support and they are quick to respond. I would say for the last issue that I sent them, they are still doing the investigation on that. I checked everywhere on the communities and I think it is still something they are working around. In terms of support, when I send a ticket, it is responded to, I get feedback and then I'm asked if it works or if I still have any issues. That is also a good thing they are doing there.

Before we started using Cisco, we were using the Ubiquiti UniFi.

We switched from UniFi, because at the time, the UniFi access points were being managed locally at each location here. So we had to set up local accounts for admin. At the time, most of those controllers were on desktops which were off all weekend. So we had the whole work of going back to each office and resetting them and reconfiguring them. It was a disaster for us. So we were looking for a more centralized solution where one person could do all this stuff in his office or wherever they are.

The initial setup is quite straightforward.

It takes me five minutes to set up a network, because I configure everything in the dashboard. I only have to synchronize. I need to onboard it and assign it a network and it is up and running.

I do this deployment myself. I buy the equipment. It comes in, I onboard it and I send it out to the field. I tell someone to power it up and it is good to go.

We have seen ROI, yes. Because we save. Just imagine for three years we saved all that transport costs, fuel costs, and admin costs that they had to pay me to go out of office. They had to pay for the driver, the car and all those things. So we have cleared on that. Originally, we used to employ temporary staff who would help with the manual work of removing the access point, putting it back up, and troubleshooting. All that now is at zero. And the beautiful thing is that this Meraki Wireless shows us our utilization, so we get to know how the internet is being utilized and we can possibly leverage ISP on reducing the cost on bandwidth, because we require more. I have conversations with them to reduce the cost of our bandwidth and give us more bandwidth for that data. It also has the analytics that know what our customer is doing. I really think that the organization has obtained its return on investment. This is why when I say that we need another $13,000 next year, they will gladly give it to me because they know that the solution helps us do our work.

Each Meraki license is around 130. We pay $139 for three years. So every three years we spend about $13,000.

We also checked out Ruckus Wireless. I went with the Meraki because it gave me more capability in what I was looking for

My advice to anyone considering Cisco Meraki Wireless LAN is, if you can afford it, I think it is a good solution. If your CBA, cost benefit analysis, is okay - I would recommend Cisco Meraki because it helps you reach many, many points from just one center. It has simplified my work because before I had to travel every day to a different place because of a different wireless issue. Now I have remote oversight over all of them. I can know what to do if someone called and said, "Something's wrong here." First take a close look, study some of these things, maybe come to PeerSpot and get some notes before embarking on Cisco Meraki.

On a scale of one to ten, for point to point for big crowds, I would give Meraki a nine. A nine because there is always a need for improvement. This is only on the technical part - of course if you factor costs and all, I may have a different score, but for me as an engineer, I give it a nine.

The solution was deployed in five locations in The Netherlands. We are in K-12 education. Around 2000 students and 500 staff have used Meraki WiFi for the past seven years. 

Younger students have Apple iPads and older students use Microsoft Surface. Staff have a mixture of Dell laptops and Microsoft Surfaces, and can move between sites using the same SSID on all sites. 

Infrastructure is mostly Cisco Catalyst switches L2 and L3, with Sophos firewalls. The use of mobile devices is mainly internet browsing, with some local access to internal database applications.

Cisco Meraki is easy to set up and maintain, yet has issues with firmware updates breaking functions, and not being fixed for months - in one case more than one year. 

Roaming seems to be a function they break regularly with their updates, and then cannot find a solution for. They ask us to wait 18 months for a fix, whilst telling us to upgrade to fix other issues, and not fixing the roaming issue. 

If you don’t discover the problem within two weeks, they refuse to downgrade you to a working firmware version, leaving you with a non-working one. 

And putting the emphasis on you to prove you have a problem. We are a Microsoft school and don’t have Apple, and yet they asked us to find a personal Apple device to install packet capture software on, so they can troubleshoot their issues. It took more than a month to get them to admit there was a problem with their firmware and roll it back to a working version. All the time, students were having problems with roaming.

Licensing is obviously an issue with these devices. You need to buy a license to keep it working. If the license runs out you have no WiFi anymore.

For the last issue I reported, the response from the helpdesk was ‘use a less complex password’. Our password was ‘password’.

On the positive side, they will replace any broken hardware without question.

After five years we decided to replace our old Meraki APs, and Cisco gave a quote for 80 thousand euros, plus they wanted us to relocate every access point to a different position in the building. Another company gave us a quote for a quarter to this price, with no licenses needed and access points in every classroom. Needless to say, we ditched Meraki.

It is very handy to have a support number to call. They will replace the hardware the next day if you prove it is broken.

The dashboard has a lot of functions and is fast, and you can configure everything you need from the dashboard.

The app is handy - when it works and you can log in.

Firewall and traffic shaping are very useful. Also, application blocking is handy.

You can see exactly which clients are connected to which device and trace traffic going to that device.

Maps and floor plans are very useful to see where a client is connected.

The licensing model is a terrible idea. Don’t buy a license for seven years, you will be stuck with old hardware that doesn’t work properly anymore, and can’t be replaced and you are expected to pay yourself to replace in order to fix their issues. If they can't fix the issues anymore in 7-year-old hardware they should replace the hardware at their expense, however, all they say is you have to buy new hardware. A maximum of a five-year license is my recommendation. WiFi technology moves fast and seven-year-old hardware is no longer workable.

The limit of two weeks on rolling back a firmware update is ridiculous. If you report a problem that affects a whole location they should let you roll back the firmware after any amount of time, not limited to two weeks. Then you have to spend a month every day on the phone trying to persuade them that you have a serious issue with their firmware.

I've used the solution for seven years.

The stability is fine until you upgrade firmware and then discover something doesn't work. 

The solution is good and easy to scale if you keep the same settings everywhere.

The helpdesk is always available to help you, but their help is very limited sometimes. For example, if you have gone over the 2 weeks deadline with downgrades, they can refuse to downgrade you until you prove to them that your new firmware isn't working properly. So don't expect to have working WiFi for a few weeks, whilst you try and prove to the helpdesk you have a problem. Then after a month they finally admit there is an issue, and agree to downgrade you, and all the problems magically go away. Until the next time, you upgrade.

Neutral

We used Cisco's traditional WiFi with hardware controllers on all sites - AIR-CAP and AIR-LAP

We switched due to the fact that the cloud dashboard to manage all sites seemed like a great idea, no more controllers on-site to maintain, and support was built in to the licensing.

The setup was done by a reseller, who said 'this is a standard install, nothing special' until we had 1,000 students all come into the school after the holiday and discovered it didn't work properly. 

Then when talking with Meraki, we discovered the reseller had set it up with default settings, hadn't accounted for high density, and didn't do the channel planning properly. After several re-visits, they did a channel plan and set it up manually, which did help.

Through a reseller. Level of expertise = nil. Meraki had to tell them how to setup the correct channels.

High capital expenditure and licensing costs make it an expensive option compared to other vendors in the market.

The cost of the hardware and licensing is extreme compared to other vendors. The Meraki model would be great for small/medium businesses with many locations to manage in one dashboard. However, it's not good for education, the roaming often doesn't work and the rollback is difficult, especially if Meraki decide they are not going to help you, and not fix their issues for 18 months.

We might have looked at Ruckus and Aruba, however, Meraki seemed like the best option for us. It was also recommended by Oxford University at an education event.

Make sure it's the right solution for your business. Don't buy a seven-year license as seven years is too long in the WiFi space. 

Get a good reseller who will give you good support, not just say "contact Meraki" every time you have a problem.

We are transitioning away from Meraki to another vendor, with four sites down and one to go. There are no regrets so far.

We installed approximately 20 Cisco Meraki Wireless LAN in our headquarters and we have a remote site, a satellite office, which has about seven more installed.

Cisco Meraki Wireless LAN is an on-premise solution, but it uses the Meraki cloud portal. We have to register the WAP with the cloud.

In our Satellite office, we have approximately 30 users and guests. We have a guest network that runs through the Cisco Meraki Wireless LAN and a corporate network that runs through it. Our headquarters network hasn't been used as much, everybody's working remotely over the last year and a half because of COVID. Prior to the pandemic, we would have up to 300 people in the headquarters and guests.

Cisco Meraki Wireless LAN has helped our organization because we are able to be connected to the network while moving around. For example, I am able to take a presentation from one conference room and walk across the building and present it in another conference room without losing connection. This is pretty good for us.

The most valuable features in Cisco Meraki Wireless LAN are that we were able to see all the registered users for each particular WAP, which is a big help. The roaming allows us to have continuous wireless throughout the building. The signal can carry over from one WAP to another. Which is probably the most important feature.

We're are not fully utilizing the features of Cisco Meraki Wireless LAN to know a more in-depth analysis of what areas need to be improved. However, the security could improve. It would be a benefit to be able to lock out particular clients that are trying to connect from outside the building.

In an upcoming release, it would be a benefit to have a security dashboard that could show additional information. In addition to our Meraki solution, we have a Cisco product called ISE, Identification Security Engine, and we can detect non-compliant or non-corporate addresses from our network. Instead of using a second product, the Cisco Meraki Wireless LAN should be able to isolate the non-specified MAC addresses into the network.

I have been using Cisco Meraki Wireless LAN for approximately three and a half years.

The stability of the network is very good. I think we had oversaturated our HQ environment, where we had too many devices in a particular location. We actually had to change some of our configurations because it was causing some connectivity competition between WAPs trying to connect. We had to remove a WAP to allow better connectivity.  

Cisco Meraki Wireless LAN is scalable. If we needed to expand, it's easy to add another WAP for a new location.

As we come back into the office, in January, we'll start out with approximately 100 users. We're going into a hybrid mode and we will not have as many users as we did, prior to COVID. We had upwards of 300 people connecting and that's mostly everybody with their mobiles or laptops that come into the office. At our highest, it is approximately 300 users but starting in January, we'll probably have approximately 100 to 200.

We do not have plans to expand our usage at this time. However, if we open up a new office then we will most likely expand usage.

We have contacted Cisco's technical support a couple of times and they're very responsive. I would give them a thumbs up.

We used the previous version of Meraki at our old headquarters. The only reason we switched was that we wanted a newer product in a new office. In terms of our office move, we decided to buy all new equipment and that's the only reason we switched.

The installation is straightforward. The wireless portion of the installation took approximately one week. This included  mounting and bringing activating the network.

We used a consulting group for the completion of our network completion in our building. I followed along with them, it wasn't too complex. My experience with the constant was very good.

We have three system administrators, one being myself, and my two coworkers. We're all capable of managing the Meraki environment.

We are on a SmartNet contract. All of our Cisco products are licensed under one contract. I do not think there are any additional costs.

We did not evaluate any other options when we switched over to the newer version of  Cisco Meraki Wireless LAN.

My advice to other thinking about implementing this solution is to look at other products that are out there. I don't want to say stuck, but we are using all-Cisco products at the time and there are probably products that may be less expensive that could do the same job. We're in contract with Cisco and this is why we went with the newer version of Cisco Meraki Wireless LAN when we needed a new solution. If anyone was looking for a wireless solution, look at different manufacturers.

I never rate anything at 10 because there's always room for improvement.

I rate Cisco Meraki Wireless LAN an eight out of ten.

I think the IoT integration is the most valuable. I started applying IoT solutions 12 years ago on location-based services. Aruba had implemented this at the time. So I think the integration, particularly into the applications and stuff, is pretty interesting in Meraki. It's a substantial network from my point of view. It's good.

You're starting to see CO2-type sensors come into the classrooms and stuff like that. So it would be nice to build some "if-then" functions into IoT-type sensors. For instance, if a classroom has high CO2 levels, you could automatically open the Windows and use heat exchange to bring in fresh air into the room. At the same time, you could have the temperature control adjust automatically so it doesn't get too hot or too.  So you would need to plug in some configurable where you collect the output from the sensors and have it carry out some small actions based on that. I think it's well within Meraki's capabilities. 

I've been working in IT for 40 years. I was working on Nortel products even before Cisco, so I have more than 20 years of experience in WiFi alone.

Everything works. I can't knock the product. I know a lot of the senior management within Meraki and used to work with them at Nortel. I know many people who work on the product side, and I've never had a problem. I've deployed Meraki for one customer with 2,500 sites in the UK, and I don't think I've ever had a wireless AP go faulty on me. We've just never had a failure, to be quite honest. That's unusual.

The only thing that always causes problems with Meraki is the license. It's a bit of a bugbear with Meraki, and it remains today. So it's an unusual concept compared to the other products in the marketplace, but then it does cause a bit of a nuisance from time to time. The license they sell is difficult.

I've worked on Meraki and other Cisco products as well as Hewlett Packard, Aruba, Siemens, and Aerohive. Aruba's first-class product is easy to work with, and I've done a lot of the complicated location with services on the Aruba kit. Most of the WiFi solutions are pretty good. The main difference between products is the application integration for location-based or IoT services, and Meraki has a good lead. You can buy IoT centers that work. So I know they're pretty basic sensors, and they are a bit expensive. However, I don't think you can beat Meraki when you're talking about multiple deployments, particularly in retail and stuff like that. It's very good for that. With loads of different sites and small amounts of kit, it works perfectly. I haven't had many problems, and in the many times I've worked with the kit, it's never failed me. That's unusual.

I rate Cisco Meraki WLAN mine of 10. However, it would be a 10 out of 10 if it could apply some conditional logic where the result from a sensor triggers an action on another IoT device, such as a motorized heat exchanger, to bring fresh air into the building. If you were able to do something like that, it would improve things even more. It's a good LAN, but there's always room for improvement. There are some things that I'd like to see, such as more applications, integrations, and stuff like that, but apart from that, it's pretty good.

When you look at the benefits, some wireless solutions are more flexible than others. Meraki is easy to configure and monitor. The best thing Meraki can do is give them a test AP on their network because there is some problem with APN allowing other kits on the network and letting people test, but handover between the APs is satisfactory. I've got four APs in my home that go between the office, workshop, and high space, and the handover is still seamless. The coverage is brilliant from my point of view. I deployed it in a large warehouse, and handover was seamless. It was covered. To me, the easiest way is to get a customer to test their network with two, so they can do a handover and allow them to test and configure. That's plug-and-play.

There are a variety of use cases. It is being used in a community center, a school, a gymnasium, and a youth center.

It's a combination of constituents. We have teachers, employees/staff, students, parents, and visitors. We have many different users.

The most valuable features are the multiple types of user groupings and access management. For example: what, when, how long for, what is the performance, and what device are they using are all groupings.

Some of the built-in capabilities need to be improved. The radius capabilities for filtering by MAC address, some of the group-based policy management, even though they have more flexibility.

They need a better reading of device TACs, which are terminal equipment codes.

When you read a MAC address or a serial number, you can detect if it's an iOS or an Android device. Specifically, within the Android world, it can detect if it's a Samsung, an Acer, or if it's a Dell. In the Apple world, you can detect if it's iOS, iPhone, or an iPad.

Their TAC reading and interpretation capability are not as effective. For example, they may be reading a MAC address and reporting it as an iPhone, but it may be a Samsung. It's not just iPhone and iPad confusion, but iPhone and Android cross confusion.

There is a processing limitation when you have multiple SSIDs, above three or four.

I have been working with this solution for three years.

We are working with the original version of Meraki, not the latest version.

In terms of stability, it's relatively straightforward.

It's a scalable solution. It's pretty good.

We have never had to contact technical support.

We work with Meraki, Eero, and Ubiquiti.

The initial setup is relatively straightforward. It's literally a plug-and-play, once you set up on the portal. I would be stretching to find an issue.

Anything that is common to all of the access points is the same, You have to run the cables. Once you have done the Delta it's probably a couple of days to deploy.

It depends on what you want to configure or the level of configuration complexity. We have, for example, access points in a specific location that are broadcasting on certain SSIDs and providing access to only certain users or certain devices, and for specific services which have to be configured.  

If you generate an existing configuration, you can just plug it in and it will boot. If however, it requires a specific configuration, it will take time to configure the specific set of requirements.

We had a deal and we went for it. If I had to go for it today, I would reconsider, unless I get more competitive pricing. The gap in terms of performance, quality, features, and functionality has decreased significantly compared to what it was five years ago. 

Now they have much more. They used to be a startup and they did pretty well. They got into growth mode, VCs pushed them to grow and they started developing features and functionality. 

Amazon bought them. Now that Amazon has its backing, they should be able to grow and improve features, which is going to put them on a similar pedestal as a Cisco Meraki, and the same for Ubiquity. But those are just nuances. 

Today, it would be harder for me to push for Cisco Meraki.

Their biggest challenge is cost. Since it's been acquired by Cisco, it's an even higher cost.

If they are going for the long run it's good, but if you go too long, there is a cost component to consider and figure out, because the cost is something that is coming down with a lot of new solutions.

I would rate Cisco Meraki Wireless LAN a nine out of ten.

Cisco Meraki Wireless LAN is a wireless LAN solution providing wireless access points for the organization.

What I like most about Cisco Meraki Wireless LAN is the cloud based management of the entire system. The product was also easy to deploy and easy to troubleshoot.

I haven't really come across anything that was a big issue with this product. I can't think of anything that would have raised a flag about something needing to be improved in Cisco Meraki Wireless LAN, but it could be their support. We had some issues, and we couldn't figure out why they happened, but some of their first level support staff does not seem to be well-versed with how to solve those issues.

Nothing really comes to mind about what I would like to see on the next release. I know they are using the six GHz band now for Wi-Fi 6, submitted out as an option, seeing use of the six GHz band down the road for Wi-Fi 6.

I've been using Cisco Meraki Wireless LAN for two years now.

Cisco Meraki Wireless LAN is a stable solution.

Cisco Meraki Wireless LAN is scalable.

Support for Cisco Meraki Wireless LAN needs improvement, as it seems their first level support staff isn't that knowledgeable on the solution, however, their response time on the issues is okay.

We used a different solution before switching to Cisco Meraki Wireless LAN. We decided to use Cisco products because the Meraki devices were much better than other platforms, particularly in cloud management, ease of deployment, and ease of troubleshooting.

The initial setup for this solution is a combination: it could be straightforward, or it could be complex, e.g. setting it up would've been complex in some situations.

Cisco Meraki Wireless LAN is a cloud solution with on-premise deployment, and we did the deployment ourselves, without an integrator, reseller, or consultant. The deployment did not take long.

We tried Aruba, but we didn't get any feedback from the vendor.

We try to have a relationship with the vendor, e.g. we have a Cisco rep for that, but they wouldn't really help us with the Meraki blocks. I'm a network engineer assigned to the company that uses Cisco Meraki Wireless LAN.

We cannot have more than 400 users of this product, and we currently have 200 to 300 people using it. For deployment and maintenance, we only have one staff who takes care of it, e.g. one engineer. We have no plans of increasing the number of users of Cisco Meraki Wireless LAN, unless we expand in size.

My advice to others looking into implementing this product is that it's definitely a good investment. They just have to be mindful and really understand the technology. They should be able to go through the documentation on the website, to really understand the product features and functionality, because sometimes they may need to exert effort in examining issues on their own, because sometimes support doesn't really provide a proper, tangible response.

I'll give Cisco Meraki Wireless LAN a rating of eight out of ten, because we're very satisfied that it meets all the technical attributes we were looking for, and it's a solid infrastructure. It works with our problems, e.g. any major problems.

The last company I was working for did an overall network revamp project where they replaced all of the access points, switches, and firewalls. We replaced all the aging equipment with new ones including Cisco Meraki Wireless LAN solutions.

The automatic VMware update is very useful because you don't have to worry about outages and planning for VMware updates. It is very advantageous from a management point of view. The ability to restrict and review the clients connected to each of our segments. Additionally, the solution is easy to use.

Cisco Meraki Wireless LAN could improve by having more granularity in terms of the data displayed. However, I understand that with Cisco Meraki Wireless LAN, you need to have a compromise point to what are the functions that you're going to provide to the users versus ease of use. More granularity in terms of the data and the things that you can do to the devices would be helpful. For example, when we wanted to make a change, restriction, or segregation within Palo Alto, we can go to the level of detail that we want. The amount of detail provided is amazing, it is very granular. However, it comes with much more difficulty, it requires a technical understanding of the environment compared to Cisco Meraki Wireless LAN. 

I used Cisco Meraki Wireless LAN within the past 12 months.

I have not used the technical support because the equipment was new.

We used other vendor devices previously, such as Dell PowerConnect. We were looking for a solution that was easier to configure and maintain while not compromising the visibility of our environment. That's why we chose the Cisco Meraki Wireless LAN solutions because they have user-friendly dashboards to use the equipment and at the same time, it does provide the visibility that we needed to control our traffic in all our branches. 

When you are deploying equipment in remote areas where you don't have many employees having a cloud dashboard where you can make changes to your equipment easily is a large benefit. Having a centralized, single pane of glass dashboard where you can manage all your equipment in one place has been helpful.

The initial setup was very easy considering it is a Cisco solution.

It took us approximately two to three weeks, to migrate small branches which were quite fast. We hadn't migrated the head office systems when I left the company but that implementation would have been more complicated because that's where the data center is involved.

We hired a network architect as a consultant and that team helped us do the whole migration and implementation. When we were doing the setup of switching and the access points, it require a lot less preparation because of its ease of use. Other solutions, such as Palo Alto, required a lot more planning.

We have 12 branches and our head office and we use one person for marinating and supporting the solution. However, we did outsource the support, we pay annually for support from a third-party company that helps us maintain our equipment. They are on call if we need them.

I rate Cisco Meraki Wireless LAN an eight out of ten.

Cisco Meraki Wireless LAN was easy to deploy and use, it gives us the functionality that we need to maintain our infrastructure functions, and at the same time, it does provide the security that everybody's looking for these days. We did replace the firewalls with Palo Alto, which gives us another layer of security because Palo Alto's very good in that regard.