Technical wireless Team Lead at SEE "Systems Engineering of Egypt"
Real User
Top 5
Sep 29, 2026
Regarding improvements or enhancements in Cisco Meraki MR Wireless, I believe Cisco should take the step of offering multi-vendor support. I have worked with solutions where the same access point can function as a cloud-managed device, as an embedded wireless controller, or through CAPWAP management from a wireless controller. In new launches from Cisco, this capability has been introduced, and I think this was a weak point before. Regarding missing features in Cisco Meraki MR Wireless currently, I believe there should be more adaptation for third-party integrations. Some features do not work with third-party implementations, such as SMS gateways from certain vendors, or when customers need to connect through Active Directory.
Solution Engineer & Manager at a media company with 1,001-5,000 employees
Real User
Top 10
Sep 1, 2026
I cannot think of any at the moment because the only possible solution we are right now using is HP Aruba, the other competition, and in my opinion, both solutions offer a similar feature set; it is just about the feasibility, and in my view, Cisco is better since Meraki is better, in fact, because it has the zero-touch provisioning feature which is really good, while Aruba has a lot of dependency, so Meraki is already really good; I do not foresee any other improvements at the moment, apart from maybe introducing more security, granular security based, or access based controls. I think the accuracy of Cisco Meraki MR Wireless is almost accurate, but in my opinion, there is a lot of improvisation needed on that side.
Network Engineer at Edmonton Catholic School Board
Real User
Top 5
Nov 13, 2025
I have utilized Meraki's RF Optimization to some extent. To do that effectively, I really need accurate floor plans, which I don't yet have. Without having the full picture, I'm operating somewhat blind and have to be careful.
We do not use Layer 7 traffic shaping extensively in Cisco Meraki MR Wireless, except for blocking URLs. We block URLs and websites by category through Cisco Meraki MR Wireless. We do not use the analytics feature extensively in Cisco Meraki MR Wireless. We only use the log to trace issues. Regarding service support, Cisco Meraki does not provide direct support. When raising support tickets, the support is not always effective. Among our tickets, 50% receive proper support and guidance, while the remaining 50% do not receive adequate attention.
I don't think there's an advantage with Cisco Meraki MR Wireless; I think it's overpriced for what it does. The pricing is one reason, and there is also a limited feature set without spending more money. If you have a particular device at a site and want to add the advanced feature set, you may have to upgrade the hardware, which increases your costs. In contrast, products such as Palo Alto and Fortinet typically have all those features built in from day one, and they just need to be licensed, if that. There are limitations in terms of scalability. My main concern is that Cisco Meraki MR Wireless is overpriced, has limited functionality, and the hardware is not prepared for any further improvements in terms of features.
The challenge with Cisco Meraki MR Wireless is that for any Meraki device, you require internet connectivity to get it registered on the cloud. Most customers do not have internet connectivity due to security reasons as they deny internet access. This creates many challenges for us in configuring Cisco Meraki MR Wireless. In my opinion, what should be improved in Cisco Meraki MR Wireless is that the AP should initially get configured irrespective of the internet connectivity.
Cisco Meraki MR Wireless offers cloud-based management, reducing on-prem hardware reliance and easing deployment with zero-touch provisioning, making it ideal for high-density environments.Cisco Meraki MR Wireless provides central management through a cloud-managed dashboard, facilitating easy control across multiple locations. Features like Layer 7 traffic shaping, RF optimization, and security enhancements, including Air Marshal and WIPS, make it suitable for enterprises managing complex...
Regarding improvements or enhancements in Cisco Meraki MR Wireless, I believe Cisco should take the step of offering multi-vendor support. I have worked with solutions where the same access point can function as a cloud-managed device, as an embedded wireless controller, or through CAPWAP management from a wireless controller. In new launches from Cisco, this capability has been introduced, and I think this was a weak point before. Regarding missing features in Cisco Meraki MR Wireless currently, I believe there should be more adaptation for third-party integrations. Some features do not work with third-party implementations, such as SMS gateways from certain vendors, or when customers need to connect through Active Directory.
I cannot think of any at the moment because the only possible solution we are right now using is HP Aruba, the other competition, and in my opinion, both solutions offer a similar feature set; it is just about the feasibility, and in my view, Cisco is better since Meraki is better, in fact, because it has the zero-touch provisioning feature which is really good, while Aruba has a lot of dependency, so Meraki is already really good; I do not foresee any other improvements at the moment, apart from maybe introducing more security, granular security based, or access based controls. I think the accuracy of Cisco Meraki MR Wireless is almost accurate, but in my opinion, there is a lot of improvisation needed on that side.
I have utilized Meraki's RF Optimization to some extent. To do that effectively, I really need accurate floor plans, which I don't yet have. Without having the full picture, I'm operating somewhat blind and have to be careful.
We do not use Layer 7 traffic shaping extensively in Cisco Meraki MR Wireless, except for blocking URLs. We block URLs and websites by category through Cisco Meraki MR Wireless. We do not use the analytics feature extensively in Cisco Meraki MR Wireless. We only use the log to trace issues. Regarding service support, Cisco Meraki does not provide direct support. When raising support tickets, the support is not always effective. Among our tickets, 50% receive proper support and guidance, while the remaining 50% do not receive adequate attention.
I don't think there's an advantage with Cisco Meraki MR Wireless; I think it's overpriced for what it does. The pricing is one reason, and there is also a limited feature set without spending more money. If you have a particular device at a site and want to add the advanced feature set, you may have to upgrade the hardware, which increases your costs. In contrast, products such as Palo Alto and Fortinet typically have all those features built in from day one, and they just need to be licensed, if that. There are limitations in terms of scalability. My main concern is that Cisco Meraki MR Wireless is overpriced, has limited functionality, and the hardware is not prepared for any further improvements in terms of features.
The challenge with Cisco Meraki MR Wireless is that for any Meraki device, you require internet connectivity to get it registered on the cloud. Most customers do not have internet connectivity due to security reasons as they deny internet access. This creates many challenges for us in configuring Cisco Meraki MR Wireless. In my opinion, what should be improved in Cisco Meraki MR Wireless is that the AP should initially get configured irrespective of the internet connectivity.