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 dfurasek
dfurasek
Here to help
Member since Oct 26, 2017
May 2 2023
Community Record
20
Posts
13
Kudos
0
Solutions
Badges
In general, we were purchasing the MR42 from 2016 through 2018. I realize that some of these will be ten years old in 2026, but what bothers me is that the amount of time between the end-of-sales announcement and the end-of-support date is significantly less for the MR42 when compared to what it was for the MR34. For what it's worth, I was told on the phone by a Meraki rep as recently as late 2020 that nothing had been said (internally or externally) about the retiring of the MR42, but that conversation unfortunately ended up being not long before the MR42 end-of-sales announcement. One way or another, we'll deal with it, but I'm just a bit surprised by the timeline. The other piece of the puzzle for us is that these AP replacements are typically something that we like to do while our schools are out for summer, but the end-of-support date in July (versus October for the MR34) might make things a little tight...
... View more
I have to say that this is not cool on Meraki's part. With the MR34, the period between end-of-sale (10/2016) and end-of-support (10/2023) was seven years. With the MR42 (the designated replacement model for the MR34), that period has indeed been reduced to four years, as outlined here: https://documentation.meraki.com/@api/deki/files/18680/MR42_EOS_Notice_updated_June_2022.pdf Interestingly, that very same document contradicts itself by stating the following: "End-of-Support Date (EOST): The last date a product will be affirmatively supported by Cisco Meraki, typically five (5) years following the EOS Date." We're replacing our last remaining MR34 devices this year, and we could really use an extra year to get all of our MR42 devices replaced. I'm typically not one to complain, but I think I would really like to try pushing to get end-of-support for the MR42 pushed out one more year until 2027. Are there any recommendations on how to best and most effectively go about making such a request?
... View more
Apr 8 2021
8:04 AM
Update: We were notified by Meraki support late last week that this issue has been fixed, and we are currently keeping our fingers crossed, while we wait to see what happens when Apple releases their upcoming 14.5 update.
... View more
Feb 25 2021
12:24 PM
1 Kudo
I opened a support ticket about this issue on 2/3/21, and it was acknowledged as a known issue affecting multiple customers. When I asked on 2/18/21 if there were any updates, I was told that they were still working on it, and there was not yet any ETA for a fix or workaround. Still patiently waiting...
... View more
Feb 4 2021
8:09 AM
We are attempting to use the Meraki MDM to push a VPN profile to iPads, using the IKEv2 connection type with certificate authentication, and the ultimate goal is to have an always-on remote access VPN connection between the iPad and a Cisco ASA. Detailed documentation for this scenario (both inside and outside of official Meraki resources) is hard to find, and so far, we have been unsuccessful in making this work as intended, after several attempts and even trying to enlist the help of Cisco TAC. I guess my first question is... Has anyone here been able to successfully implement the scenario that I outlined (especially the ASA part), and/or has anyone here even tried? Thanks!
... View more
Labels:
- Labels:
-
iOS
It seems like Meraki is really anxious to get this update out the door. Unless I missed it (entirely possible), I think they skipped public beta and went straight to RC for this one. Also, they've already auto-scheduled it twice for us, even before moving it into the stable release bucket, and since I don't recall that ever happening before, I've cancelled it both times. Of course, RC is better than beta, but stable is better than RC, as we were bitten once in the past by a premature RC update. In any case, I'm running it on just one of our networks, with no problems seen so far, but I'm a little leery about pushing it out to the others before it's finally declared stable, especially if they did indeed skip the beta stage. The release notes do mention two jQuery related CVEs that are classified as "medium" severity, but that doesn't seem to be enough to warrant this level of urgency. Anyone have any commentary on what I might be missing in all of this?
... View more
Oct 19 2020
12:57 PM
Hi @Noah_Salzman Regarding your post from 09-03-2020: "Hi dfurasek, I'll look into this and get back to you." ...is there any news on the activation lock removal piece for non-enrolled DEP devices in the legacy MDM? Thanks again.
... View more
Aug 28 2020
7:54 AM
@Kevin_C and @Noah_Salzman Update: I was just told by tech support that legacy MDM users will not be able to clear activation locks from the DEP page, and here is what I sent back in reply: "So, that was intentional?? If so, I fail to see the logic… The new features on the DEP page were added to mitigate the recent removal of the device detail pages for DEP devices that were not actively enrolled in the MDM. In other words, features were taken away (for both legacy and enterprise users), and this was done to put back equivalent means to the same ends. As a legacy user, the modification of owners and device names works great, but I can no longer clear an activation lock on such devices. When the free/paid pricing model was adopted a few years ago, it was understood that legacy users would not get most new features but would continue to be able to use existing features. As of now, this one important feature has been taken away from us, and I am respectfully asking to get it back. Again, we are indeed using the MDM for free, but we are also a Meraki wireless customer with hundreds of APs, so I would hope that counts for something. If it is to remain as is, I would very much appreciate some sort of official statement to that effect, and if possible, having that backed up with sound reasoning would also be most appreciated. Thanks again." Would one of you gentlemen be able to please comment on this?? Again, I very much appreciate all of your efforts to make this whole situation right, but it seems there is still one small missing piece of the puzzle, which could (and I think should) be easily resolved. Thanks! PS - I used the other two features (device names and owners) just this morning, and I was very pleased with the new workflow. 🙂
... View more
Aug 26 2020
11:12 AM
@Kevin_C and @Noah_Salzman I see that all three of these new features have now been implemented on the DEP page, and it looks great. 😊 Thanks!! However, while changing owners and device names works perfectly, clearing the activation lock from there appears to require the licensed version of the MDM. As a legacy MDM user, I can still clear an activation lock on the device detail page for an enrolled device just as has always been the case, so I'm guessing/hoping that the inability to do the same from the DEP page was maybe just an oversight at this point, right? Please advise, and thanks again.
... View more
Aug 12 2020
1:34 PM
@Kevin_C Nice. 🙂 Thanks!
... View more
Aug 7 2020
1:26 PM
@Kevin_C that sounds great! Will this also be available to users of the "legacy" MDM? Please say yes... 🙂
... View more
Aug 7 2020
7:20 AM
I haven't heard anything since @Noah_Salzman indicated that a "rough sketch" of their planned changes would be forthcoming in this forum, but I have seen some signs that something is in the works, such as the addition of an "owner" column on the DEP page in the MDM.
... View more
Jul 28 2020
5:10 PM
@Noah_Salzman Thank you for the sincere reply. I look forward to your forthcoming update on the changes that you are planning.
... View more
Jul 28 2020
6:10 AM
1 Kudo
@Noah_Salzman @Kevin_C Thank you for taking the time to post in this forum, it is much appreciated. Please, please, please reconsider your decision. In addition to renaming devices and assigning owners, there is also the even more important need mentioned a few times in this thread to disable the activation lock. (If you have ever needed to contact Apple to have that done on their end, you know that it is not at all a quick and simple process.) Those are at least three concrete features that have been removed by this recent change. With respect, what I'm hearing are vague things like "the intent was to avoid confusion" and "more consistent cross-platform device deletion experience" as far as improvements due to the same change. In other words, try as I might, I'm really failing to see how the benefits outweigh the costs. If there truly are better ways to perform (all three of) these tasks coming down the pipe, that's good to hear, but what you had before worked just fine, so it would certainly seem to be simpler to just go back and not reinvent that wheel. If the decision stands, I guess that's ultimately your call, but would it be possible to at least temporarily revert until those enhancements are ready for prime time? Better yet, could you go back to the old way and eventually add the new way as a second alternative for those that choose to use it? Again, I may be missing something, but I don't see how that would be a bad idea, especially since I think we're just talking about restoring access to the exact same page that is still available for actively enrolled devices. Finally, we are a paying Meraki customer with hundreds of wireless access points, but in the interest of full disclosure, we are currently using the "legacy" MDM for free. We have accepted that the free MDM does not have nearly the feature set of the paid MDM, but it does what we need it to do, so we have found ways to deal with the lack of the newer features. In this case, certain fundamental features that existed long before Meraki switched to the free/paid model have been actually removed, so I would very much hope the new enhancements that were mentioned will be made available to both free and paid MDM users. Thanks again.
... View more
Jul 20 2020
8:58 AM
3 Kudos
Yes, excellent point! This change has also taken away the ability to clear the activation lock on a DEP device that has already been removed from the MDM for any reason, which is definitely a problem. ☹️
... View more
Jul 17 2020
8:29 AM
6 Kudos
Hi All, Sorry for the length of this post, but I'm attempting to drum up some community support for reverting a recent change that was made to the Meraki MDM. Please understand that all of my discussions with them have been very cordial, so I'm intending no malice towards anybody with Meraki. Just maybe I'm the only one not pleased with the change, but that would be a surprise to me. If I'm not alone, I think it would be beneficial for them to hear similar sentiments from others besides myself, so I'm encouraging others to also politely open another case to echo my concerns. So, without further ado... A few days ago, I submitted the following case to Meraki support: "Previously, under Systems Manager -> Devices, I could switch from the 'General' view to the 'DEP' view (in the upper-right corner) to see DEP devices that were assigned to that network but not yet actually enrolled by the setup process on the device itself. Now, I can still see those devices in the list, but if I click into any one of them, I get an error that looks something like this: Additionally, if I switch to the Systems Manger -> DEP page, such devices appear in that list with a 'Name' that is no longer a clickable link, which is also a change from previous behavior. All of this is a big problem, because I can no longer rename a device and/or assign an owner prior to the device being activated." ...and after their initial response indicated a need for further clarification, I followed up with this: "For the last several years until very recently (i.e. earlier this week), I have been able to access the detail page for any DEP device where the settings had not yet been pushed (a 'placeholder' page of sorts), where I could rename the device and/or assign an owner, and I could take two paths to get to that point: 1. On the DEP page, as long as I was already working in the particular network to which the device had been assigned, I could click on the device name to get to the detail page. This same device name is now non-clickable text. This is definitely a recent change in behavior. 2. On the device list page, I could change the selector near the top-right from the default 'General' option to the 'DEP' option, and from there, I could click on the device name to get to the detail page. This same action now leads to the error described in my initial case submission, and this is also definitely a recent change in behavior. Based on what I know right now, this is a significant negative impact to my workflow efficiency, because I can no longer perform those tasks until after the device is activated." I was eventually told the change was intentional, with the following statement from the Meraki product team: "The intent was to avoid confusion since if the device is not enrolled there is no need for the device link to be a hyperlink to a non-existent page." ...and my last response to them (so far) was as follows: "Until this change, the page (client details for a DEP device that was not yet enrolled) did indeed exist, and it was that way for several years. As to the 'no need' bit, I have a frequent need to change the name and/or (more importantly) assign an owner for such devices. Without that ability, I can no longer pre-configure an email profile (based on the owner) for a given device, so the experience is worse for the end-user, and my workflow is much less efficient, as I have to circle back after enrollment to take care of these tasks." If you agree, please take action, and whether or not you agree, please feel free to discuss here. 🙂 Thanks!
... View more
Labels:
- Labels:
-
DEP
-
Enrollment
-
iOS
Dec 11 2019
5:59 AM
Here are the "wishes" that I've submitted from within the dashboard in the past. So far, none of them have been implemented, but here's hoping... 🙂 1. I wish the "Firewall & traffic shaping" page for wireless networks provided the ability import/export a set of layer 7 firewall rules, which would eliminate the need to manually rebuild our entire list of rules when creating a new SSID. 2. I wish the "Access control" page for wireless networks would offer a "strict priority order" versus "round robin" option for RADIUS server load balancing when using WPA2-Enterprise with our own RADIUS servers, similar to the feature that you already offer when using your splash page RADIUS features. 3. On the client detail page for a MR wireless client, there is a link to the MDM client detail page. I wish this page would do the same thing in the other direction, by linking directly to the wireless client detail page for any MDM client is also a wireless network client. 4. My dashboard account allows me to access multiple organizations, but I spend the greatest portion of my time working with just one of them. I wish that I was able to choose a "default" organization in my account profile, such that I would not be presented with the "choose organization" page every time that I log in. From there, I could easily switch to one of the other organizations from the navigation pane if/when needed. 5. I wish the block page that is triggered by a layer 7 firewall rule could be customized, such that more information about our policies could be communicated to the end-user via that same page.
... View more
Oct 26 2017
12:09 PM
I was made aware of it via a banner announcement that appeared at the top of all pages in the dashboard. I do know that those banners can be flaky, as there have been times in the past that one or more users in our office (using their own credentials) have seen announcements that others have not, so maybe you fell victim to something like that. Also, if you are planning on just doing a standard ICMP ping, I don't know that it will suffice, as you need to allow traffic through your firewall on specific TCP and UDP ports. As the FAQ mentions, you can refer to the Help -> Firewall Info page in the dashboard for all of the details. I generally like to use the "Download unfiltered rules as CSV" option on that page to see the greatest level of detail on what sort of changes I might (or might not) need to make in order to allow our Meraki hardware to work properly.
... View more
Oct 26 2017
8:59 AM
1 Kudo
Just curious, did you see this recent announcement: https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Cloud_Maintenance_FAQ ...and adjust your firewall accordingly?
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 6 | 24171 | |
| 3 | 24053 | |
| 1 | 2705 | |
| 1 | 23834 | |
| 1 | 7340 |
© 2024 Cisco Systems, Inc.
