Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About IT_Magician
IT_Magician
Building a reputation
Member since Jan 20, 2020
Jan 22 2024
Community Record
85
Posts
28
Kudos
2
Solutions
Badges
Nov 22 2023
9:28 AM
3 Kudos
Meraki support rolled the firmware back to 16.16.9 and the Z3C activated immediately. Support said there is an active investigation and until that is resolved we will have to keep the Z3C on this firmware. For those who have this same issue you will need to call Meraki Support to reach this firmware level as you cannot do this on your own. Also worth noting, we have other Z3C devices on the newer firmware versions and they work fine, but those have been activated for a long time so maybe ths issue is just during activation? Also under known issues I am seeing this regarding the Z3C: MX67C, MX68CW, and Z3C appliances may encounter an issue where they are unable to communicate with the integrated modem. This state can be cleared by rebooting the device. When MX67C, MX68CW, and Z3C appliances are repeatedly unable to communicate with the integrated modem, they will attempt to reset the modem to restore connectivity. In some cases, this reset procedure may fail, requiring the appliance to be physical power cycled to restore connectivity with the modem. Due to an MX 17 regression, the integrated cellular modem on MX67C, MX68CW, and Z3C appliances may fail to acquire an IP address via DHCP. This can be resolved with a physical power cycle of the appliance. MX67C, MX68CW, and Z3C appliances may erroneously detect a SIM card as missing. This state can be cleared by rebooting the device. Either way I want to give a shout out to Meraki support, we are now able to hit some deadlines before the holiday break so we consider this a big win. It may be worth updating the known issues to say "revert back to older firmware" as everything listed in known issues does not state this.
... View more
Nov 22 2023
8:39 AM
4 Kudos
After confirming IP addresses is correct, I would also get your ISP on the phone. Sometimes they need to clear the ARP table on their side to make sure their modem properly bridges with your device.
... View more
Nov 21 2023
6:28 PM
Title says it all. We have Z3C, new SIM card, set APN to BROADBAND. That didn’t work so got a static with AT&T with custom APN. In both scenarios AT&T says they see it hitting the tower but Meraki isn’t requesting IP. Meraki blames AT&T and vice versa. I’ve done basic troubleshooting, different firmwares, Meraki support. SIM works fine in a iPhone. Meraki just stays at connecting…. any ideas would help.
... View more
Labels:
- Labels:
-
Firewall
Apr 28 2023
6:55 AM
Thank you for the quick responses, we are looking into Umbrella SIG. This is 100% just my opinion, but Meraki is so far ahead of the competition when it comes to ease of use, ability to quickly pinpoint the issue, and preventing misconfigurations that could cause an issue, that moving to some of the DPI capable vendors for us, is a huge step backwards.
... View more
Apr 27 2023
6:54 PM
As the title says, I am looking for deep packet solution that works with Cisco Meraki. We love Meraki, but we need the ability to scan encrypted traffic, scan it for PII, and if the destination/source is not on the allow list, the packet is dropped. Since Meraki cannot do deep packet inspection, does anyone know of an affordable way to integrate a deep packet inspection engine with DLP capabilities on the edge? Maybe somehow filter through a proxy that can do this?
... View more
Labels:
- Labels:
-
Firewall
Mar 22 2023
9:11 AM
First ticket was submitted December 18th, and another one when I posted this. We are being very patient and have a lot of feedback we hope Meraki will consider which everyone will benefit from.
... View more
Mar 21 2023
3:14 PM
That is why we are posting here, it might not be, but as a Cisco partner I think its important to have these debates so the community can all benefit from improved products that make our lives easier. If anyone knows of a better way, we might just be doing this wrong.
... View more
Mar 21 2023
11:31 AM
Updating MacOS Devices: Why can't we set a target version, a schedule to apply updates, and then Meraki handles the rest? I have to go to devices, sort my Mac devices, click through hundreds that I want updated, click "Push available OS Updates". All Meraki does is confirm if they sent the update command to the device, and nothing else. The user can click deny, and that is the end of it. For a company required to maintain minimum OS patch levels for compliance, how are you supposed to do this with Meraki MDM?
... View more
Labels:
- Labels:
-
macOS
Mar 21 2023
11:23 AM
Can someone shed some light onto what is happening? This is extremely frustrating, and I cannot get a resolution from Meraki support. I can tell anytime I call in about systems manager this is their least favorite product to support. Root issue: One of our custom apps fails to install Custom app deploys is dependent on Meraki System Manager being installed, which fails on 30% of devices. This is my second ticket I have opened with Meraki, the first one went nowhere and turns into "start remoting into each device individually" to spot check them. If we have to do that, then this is a very expensive paper weight IMO.
... View more
Labels:
- Labels:
-
macOS
Dec 28 2022
11:27 AM
I never came back to update this post so doing this now. We did end up figuring out the best way for us to implement implicit deny which I wrote up a guide to hopefully save others the headaches we went through. Implicit deny is possible and the link below shares what we learned and how we do it. Cisco Meraki firewall with implicit deny? Yes, its possible.
... View more
Oct 17 2022
9:38 PM
Thank you, you were 100% right. Immediately fixed the issue. We had 2 other known cases and also downgraded them and it fixed, so we ended up downgrading all with built in WIFI back to 16.6. Meraki should do a better job making support aware. We spent hours doing packet captures to no resolution.
... View more
Oct 17 2022
1:13 PM
2 Kudos
After the MX17.10 upgrade to a mx64w everything works great except built-in wireless clients have horrible lag between loading sites. I say lag because if I go to www.cisco.com it spins and spins and spins and while trying to load I can open command prompt, NSLOOKUP immediately pulls correct IP, and I can ping no problem. This happens to ALL wireless users which is VLAN 1, but our hard wired VLAN 1 devices on same subnet do not have the issue. We replaced the Meraki with a MX67w running MX17.10 and have same issue. I then try a new browser (Edge) and go to www.meraki.com and it just spins and spins (eventually loads, 30+ seconds) but while that is loading I have zero packet loss to www.meraki.com via the command prompt, and all hard wired devices can access that without any issues. On the phone with Meraki support now, but anyone else with built in wireless having issues?
... View more
Oct 6 2022
7:01 PM
1 Kudo
Okay so riddle me this. I fixed the issue with the .MSI file so it pulls down entire file. I try to install via Meraki and it fails. I add /i and it still fails. But then I add what NBV suggested and add this and it works: /l*v "C:\Temp\msi.log" What is strange is, if on Powershell I do /i or /i /qn it works on the local machine, but that same command through Meraki fails. No idea what is going on but it works now.
... View more
Oct 5 2022
1:24 PM
Alright, so I think this issue is another systems manager bug. If I run the installer via Powershell like NBV suggested it works fine. When I run it through systems manager the problem is the MSI fails to install. Here is the break: 1. Meraki downloads the .MSI file. 2. Under C:\programdata\meraki\systems manager agent\temp\download it does not successfully download the full MSI, it pulls 16KB and then stops. It should be 41MB. 3. Meraki is either waiting for it to fully download which it never does so it hangs, or it thinks it is does and tries to execute but it fails because the MSI is corrupt. At this point I am going to have to use my own powershell script to run an installer by pulling it down from our FTP into a directory and then installing that file via powershell, but Meraki does not support scripting natively, so using this documentation: Deploying Scripts in Systems Manager using Software Installer - Cisco Meraki we will have to learn Nullsoft and somehow have that run our simple powershell command. Very frustrating these bugs are lingering in this product.
... View more
Oct 5 2022
7:54 AM
1 Kudo
Received this update from Meraki support. At least they know the issue but that leaves us dead in the water. "The Meraki Engineering team finished investigating the behaviors with Windows 10 & 11 devices and Sentry VPN. The Windows 10 & 11operating system introduced a change in what type of logins and credentials can be used in an MDM environment. Sentry Client VPN was original designed using a method that Windows no longer allows by default and leads to the user being prompted to enter their credentials. As this is directly related to a change in Windows 10 & 11 behavior and the Sentry Client VPN integration we are currently investigating and tracking improvement on this issue moving forward, however I do not have any further updates on the improvement at this time."
... View more
Oct 4 2022
12:26 PM
Confirmed same issue on Windows 10. I tried downgrading the agent but even after telling it to go to 3.0 and hitting save, which is says successfully saved, if you refresh the page it reverts back to the latest version. I do have an escalated ticket open with Meraki, hopefully they get back soon.
... View more
Oct 4 2022
11:12 AM
Alright, spun up a new Windows 10 box and confirmed issue is there as well. Meraki pushes out the VPN profile but when I connect it prompts for a username and password. I am going to try and downgrade the Meraki version. We are currently using latest of 3.5.2.
... View more
Oct 4 2022
11:08 AM
You are 100% correct. We are trying to do two basic things with Windows MDM: 1. Push out a MSI 2. Have MDM provision a Sentry VPN For the MSI, Meraki only downloads 16kb of the 41MB file so the MSI does not install. For Sentry VPN, it asks a handful of Windows users for a username and password. Blows my mind this doesn't work as advertised.
... View more
Oct 4 2022
10:29 AM
1 Kudo
We have a VPN profile pushed via Sentry to both Windows and MAC devices. All MAC devices work fine, and most Windows devices work fine, but we have a handful of Windows devices that cannot connect to the VPN. I spun up a fresh Windows 11 VM and can re-create the issue. The VPN shows up, but when connecting it is prompting for a username and password instead of Meraki systems manager automatically handling that. When looking in the event viewer I do see errors with the profile installing. I removed and re-pushed the profile but the errors in event viewer still are listed (even through the VPN does install) but I think that might have something to do. I am spinning up a Windows 10 device now to test that OS.
... View more
Labels:
- Labels:
-
Sentry
Oct 4 2022
10:26 AM
1 Kudo
On our Windows stack we have an issue where systems manager fails to install .MSI files. Here is what I have gotten to on our Windows 11 device: 1. We upload the .MSI 2. In Meraki you can download the MSI which I confirm it is 41MB 3. It pushes the install but eventually fails 4. When looking at the logs it downloads the file to C:\programdata\meraki\systems manager agent\temp\download 5. However looking at that file it is trying to execute it is only 16kb I tried re-uploading the file, and even pointing the file to a dedicated URL and confirmed it is a 41MB MSI, but when Meraki pulls it down it is getting stuck. From what I can tell that is the issue but I could be wrong. I am spinning up a Windows 10 device now to test that OS.
... View more
Labels:
- Labels:
-
Apps
Sep 6 2022
12:06 PM
Hey Meraki Community, We have a customer who we are migrating away from Rippling to Meraki MDM. All features seem to be found equally on both systems except one item. Rippling allowed the IT Team to click "reset password" for both Windows and Mac. When that happened it created a random password and required change on next sign in. It then showed the password in Rippling so the IT admin could tell the user how to login, and then once password changed they are good. Does anyone know if Meraki can do something like this?
... View more
Labels:
- Labels:
-
macOS
Mar 24 2022
1:57 PM
No we were not.. but you know how bug fixes go, sometimes they do not cover all things that were breaking....
... View more
Mar 24 2022
1:52 PM
2 Kudos
For those who had issues with 14.33, it looks like they have a 14.33.1 stable release and the bug fix might knock this issue out: Bug fixes Adaptive Policies rules can be incorrectly ordered resulting in traffic being blocked when it should not be
... View more
Mar 24 2022
1:51 PM
So just today without any firmware upgrade at all, we had a location where switch went offline. Checked the dashboard and MX is up, and shows a link light to the switch. We rebooted the MX and the switch came back online. I am doing firmware upgrades now, just letting others know we are seeing weird switches going offline bugs still.
... View more
Mar 4 2022
9:04 AM
Also worth noting, after switches updated to 14.33, our MX was still on v15. We since pushed firmware to V16 but still has issue. We then took another network with MX67w and MS120, upgraded firmware to 14.33 and had no issues. We then upgraded MX67w to v16 and still no issues. This seems like a bug between ms120 14.33 and MX100 on v15 and v16 firmware. If it happens again we are going to roll back the firmware.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 318 | Nov 22 2023 9:28 AM | |
| 2585 | Jan 20 2020 4:02 PM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 4 | 522 | |
| 3 | 318 | |
| 3 | 4290 | |
| 2 | 1325 | |
| 2 | 2518 |
© 2024 Cisco Systems, Inc.
