Cisco Meraki MX Firewalls is a combined UTM and Software-Defined WAN solution. Meraki is managed via the cloud, and provides core firewall services, including site-to-site VPN, plus network monitoring.
The Meraki MX lineup is well suited for organizations that need centralized management of multiple locations, as it allows for both quick deployment and simple/easy remote administration all from a single pane of glass. It also works very well for providing VPN access for remote workers and helps monitor end-device uptime. It does, however, fall a bit short in its firewall's customization, compared to traditional appliances (like our WatchGuard Firebox), so perhaps less suited for organizations that need more customization, as the Meraki MX lineup is primarily designed for simplicity and straightforward cloud-based management.
Windows Server and Active Directory is very robust and stable, it has been a staple in every IT environment I have worked in during my career. Junior to Intermediate admins can learn Windows Server easily, the user interfaces make administration tasks very easy as well as the documentation available through a vast amount of resources. There are other Operating Systems available with no GUI which has a smaller attack surface, faster update installation and reboot time. Windows Server does have the ability to remove the desktop experience, however it is not something I have had experience with and I believe most administrators choose not to remove it.
The Cisco Meraki MX series is phenomenal at allowing us to remotely manage networks. So the devices usually act as the brain behind our client's networks, which makes it really, really easy for our team to take a look at what's going on in those client network environments, resolve any issues, and make sure that our client's networks are staying secure.
Layer seven firewall rules. Just making them more granular. We've been in meetings with Cisco SES where I've said feature requests many times and that's one of the big ones where it's just a little cumbersome to implement layer seven rules right now.
Just making them more granular. We've been in meetings with Cisco SES where I've said feature requests many times and that's one of the big ones where it's just a little cumbersome to implement layer seven rules right now.
Microsoft needs to minimize the update frequency by making the product more secure. It can become very exhausting trying to keep updated if you don't have a dedicated support team. It can become challenging where the business is unable to allow downtime for reboots as part of the update process.
Prone to security and audit vulnerabilities.
The operating system needs more CPU and memory resources compared to other options such as Linux.
Understanding the licensing model can be abit confusing.
Comes with a standard firewall, but not the most secured one available. Would suggest using a more secured firewall as part of your antivirus software.
Due to the number of vulnerabilities and the operating system being a target for hackers, anti-virus software is a must.
The simplicity and ease of use for the Meraki Dashboard make it an easy choice for our organization to renew our Meraki Enterprise Agreement. We will likely continue using the Meraki MC67-C, MX450, and other MX models in their catalog until we shift away from Meraki completely
I've carefully reviewed the servers and services currently running on Windows Server 2012, and given the opportunity would renew them as is going forward. There are two systems I currently have in place, one is a very large Linux implementation for a large ecommerce site, and one is a very large backup solution front ended by FTP servers running Linux. Neither are well suited for Windows, but the overall network infrastructure is and will be Windows Server for the foreseeable future.
Some features simply aren't there, but the ones that are there are pretty easy to use. Sometimes it is easy to get lost when trying to find the specific device you want to work on, but that's mostly due to how rarely we have to go into the interface.
Anyone new to IT could easily use the familiar Desktop Experience (GUI) version because we all know how to use Windows, whether a client or server version. Once an IT user is more comfortable with the operating system, they can move on to the Core version, which is the way to go in almost all situations.
Meraki MX devices support high availability (HA) configurations, which ensures minimal downtime if one device goes offline. This feature has helped us maintain a stable and reliable network, even in cases of hardware failures. ince Meraki is cloud-managed, we've noticed that the cloud infrastructure is generally highly reliable, with minimal service interruptions or downtime. This makes it easier to manage the network remotely without significant availability concerns. Meraki automatically pushes firmware updates and patches, which helps maintain system stability without requiring manual intervention. These updates are rolled out in a manner that ensures minimal disruption to service.
The interface is pretty responsive. The lower end devices are easy to overwhelm if you have a lot of throughput. Be sure the model you get is rated for the amount of traffic you will have. Overbuild if possible, otherwise you won't be fully leveraging the connection from your ISP.
I haven't ever had a bad experience with Meraki support. On the few occasions where I wasn't understanding the UI or needed some clarification about what a setting actually would do, I contacted them and they were very quickly able to provide help. Returns are simple and fast, too. We had to return a defective device one time and they shipped the replacement before we had even un-racked the one that was faulty. Unlike many other vendors, they didn't ask use to a do long list of scripted diagnostics, they just took my word for it that the device was broken and sent out a replacement immediately
Microsoft's support is hugely wide-ranging from articles online to having to contact them directly for the more serious issues. In recent years when I have contacted them directly, I have found the support o be excellent as I have found myself connected to very knowledgeable people in the field in which I needed the support. The online support available is vast and I tend to find most of the time that there is always someone out there who has had the same issue as me in the past and knows something about how to resolve it! This is the advantage of using industry standard and long-established systems such as Windows Server.
great when they offered it, really tested your knowledge with hands on and see what your peers from other orgs know. glad to see that we were ahead of the curve of what our peers knew
Implementing Meraki MX devices in phases—starting with a pilot group or select branch offices—was invaluable. This allowed us to identify potential configuration issues, troubleshoot problems, and refine our setup before rolling it out company-wide. It also helped to get feedback from early users and adjust the deployment strategy accordingly. The SD-WAN capabilities in Meraki MX were essential for optimizing our WAN traffic and ensuring better application performance across various locations.
Make sure that you have detailed processes in place for every server instance you plan to install/upgrade, if possible get the base OS loaded and Windows Updates applied ahead of time, and if using a VM take a snapshot prior to installing each role, as well as along the way.
Cisco Meraki MX provides simplicity and scalability while cutting costs. With Meraki MX, you get a Security appliance, router, and Firewall in one appliance and managed with one GUI. These features enable the network engineers to maintain large-scale enterprises with a single dashboard from a remote site or anywhere with internet, all thanks to the Meraki cloud dashboard
They are different experiences, and while the other solutions offer enterprise-grade stability and, in some cases, address Windows server shortcomings (such as patching), they all do the trick, but the other solutions require a deeper technical background/configuration of items at the command line, which some people are not fully comfortable with.
When I first started with my company we had various infrastructure and a mix of tech. Since going to Cisco Meraki MX we have noticed better network performance and our new sites are much easier to bring online. Users have noticed an improvement in VPN connection and getting into all our systems.
From a positive impact? Basically it allows us to set up shop very quickly. It allowed us to add sites to our network very quickly. From a negative perspective, I think the only thing is that I can see from a negative perspective is I have a preference to working with ACLI in terms of how I engage with the youth tool At the moment, the only way to actually engage with a tool is on a gui and sometimes what I'd actually like is more detailed information in terms of actual configuration that you'll actually get out of ACLI.
