Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About stevenwhiting
stevenwhiting
Getting noticed
Member since Apr 24, 2018
Nov 3 2020
Community Record
47
Posts
12
Kudos
0
Solutions
Badges
Nov 3 2020
7:27 AM
We now have BRAND NEW tablets and Meraki is refusing to register them claiming they have custom ROMS. Again, the policy to check for Jailbroken or Rooted devices is OFF! Meraki has become useless.
... View more
Sep 29 2020
11:57 PM
Been over a year and still no fix and Meraki support have been next to useless. Told me to get a original ROM for the Samsung tablets. I shouldn't have too, the tablet DOESN'T have a custom ROM in the first place, Meraki is incorrectly claiming they have. And despite all this we have the policy set to ignore custom ROMs and allow Meraki anyway, its ignoring that policy and still flagging this up. Posting again as had yet another Samsung Galaxy Tab A - SM-T580 get reset and then Meraki refuse to allow it to register due to a "Custom ROM" and custom ROM that doesn't exist!
... View more
Nov 25 2019
2:28 AM
No. However, we did discover in System Manager/Policies/DefaultPolicy/ "Device is not compromised" was ticked. This appears to state that if a device is rooted or jailbroken it won't create the profile. I unticked this 2 weeks ago, still not able to enrol the devices. Its as if the enrolment process is ignoring this policy change. I now have 3 tablets with the issue and is making Meraki useless at the moment.
... View more
Nov 25 2019
2:25 AM
Hi Noah Sorry for slow reply. No. Still claims it can't create the profile because of a Custom OS and it's been two weeks since I set that setting. It's as if it's now ignoring that we've told it "We don't care if it's a custom/rooted OS, create the profile anyway". I now have a 3rd tablet doing this. This is making Meraki pretty useless at the moment. I've logged the issue with support about the security policy seemingly being ignored. Steve
... View more
Nov 8 2019
8:34 AM
Other engineer here pointed out the policies area of Meraki dashboard and I've discovered in there DEVICE IS NOT COMPROMISED was ticked. I've unticked it, 99% sure this is what is causing the enroll issue, but how long before the device will see it? It states 1-2 mins but it's been 10 mins now, rebooted the tablet and it's still saying the same suggesting this policy still isn't seeing the change.
... View more
Nov 8 2019
7:16 AM
So we have success it getting it back to Samsung Official ROM. It states in Odin Mode it is Samsung Official ROM. Yet, Meraki still WON'T allow it to enroll because it thinks it has a custom ROM on it. It NEVER did and still doesn't! ):o( So Meraki itself is essentially saying the tablet is a brick as can't be used with Meraki anymore so can't be used as a corporate device anymore! Are there no options to tell Meraki "Yes, you might think it's a custom ROM, it's not, but just enroll it anyway! We understand the risks" but nope, I can't find said option.
... View more
Nov 8 2019
3:25 AM
Getting more and more annoyed as the days go by. FRP (Factory Reset Protection) might be all well and good but when you have a device where a user had left in anger, their Google account is long gone, trying to recover that device to be reused is seemingly impossible. Then you get a Samsung device where it has NO custom stock ROM but get the following when trying to enroll. "The security policy prevents the creation of a work profile because a custom OS has been installed on this device." So Meraki support checked the logs of the device and thought they might be able to see the issue. They think some files missing from the OS is causing it, but weren't sure. They said try factory resetting which will go back to an old ROM (it doesn't) and that also hasn't helped. Their next option was to download a stock ROM to the Samsung tablet so it should now be back to stock and no longer flagged as custom. Nope, that doesn't work either as the only option to get a stock ROM is to backup a known good tablet using TWRP. But the act of putting TWRP onto the tablet causes the ODIN Mode to flag it now as a custom ROM. Then Meraki won't allow you to create a work profile anymore, because of the CUSTOM ROM!!!! ):o(
... View more
Labels:
- Labels:
-
Android
-
Enrollment
Oct 17 2019
3:25 AM
So we noticed an issue today where Outlook contacts won't sync. We get "contact permissions are not fully granted" There are no specific settings for Outlook when deployed by Meraki. In "Systems Manager/Settings/Managed Settings/Android Restricitions" We had Auto Grant All Permissions. I've now switched this back to Prompt User for Permissions. Removed the work profile, re-enrolled and installed Outlook again. Now I get a prompt to allow contacts to sync. Does this mean "Auto Grant All Permissions" is bugged?
... View more
Labels:
- Labels:
-
Apps
-
Enrollment
Oct 17 2019
3:19 AM
Well at least we know it's broken then I guess and not our setup.
... View more
Oct 2 2019
1:46 AM
Appears to be working again but broken again the other day. Although fixed now most of our phones, Meraki still appears to insist on tracking them via the IP address which is MASSIVELY inaccurate. Can't seem to force it to only scan them via GPS.
... View more
Oct 2 2019
1:44 AM
Nope. It's a company device and hasn't been rooted and no other OS has been installed. I believe it's crappy Knox causing the issue possibly even though Samsung no longer support Knox.
... View more
Sep 9 2019
6:19 AM
We have a Samsung tablet that was working just fine. The user claims it wiped itself and we're now attempting to set it backup. But when trying to register the tablet with Meraki we get the following error. There is no customer OS on it, so not sure what it is banging on about. Anyone else seen this before? "The security policy prevents the creation of a work profile because a custom OS has been installed on this device."
... View more
Labels:
- Labels:
-
Enrollment
May 28 2019
3:13 AM
Nice. Customer Support was next to useless. Once I told them we'd found a fix via the Community all they said was that they were glad the issue was resolved. Never acknowledge the problem or give any fix for it.
... View more
May 21 2019
9:06 AM
1 Kudo
You can have 5.8.1 and if it was already broken it will still be broken until you un-enroll the device and then set it up again. Very annoying as we've had to have users bring their devices in for the fix. Still no word from Meraki themselves. Their support is shockingly poor.
... View more
May 21 2019
7:28 AM
1 Kudo
From what I can tell Meraki SM 5.7.1 is the version that broke it. 5.8.1 fixes it. From my testing on another phone I've just had, I tried pushing out 5.8.1 to a borked phone. It still had the issue even after a reboot. The only way to fix an affected phone it appears, is to remove the Work Profile and start again with 5.8.1 Annoying.
... View more
May 21 2019
5:47 AM
2 Kudos
Tried on two different model Android phones and an Android tablet and all now OK. Remove Work Profile and/or un-enrol device. Reinstall Meraki. Re-enrol and then all is OK.
... View more
May 21 2019
4:55 AM
2 Kudos
Only tried one at the moment. And yes, removing the Work Profile and then updating to the new Meraki appears to have fixed it for one phone so far. Shame Meraki themselves couldn't tell us that! Still no response to my support ticket from Meraki!
... View more
May 21 2019
2:20 AM
Nothing? The support from Meraki is shocking. Considering this is essentially a DDOS attack on the Meraki system. Logged a ticket and last update was from Meraki yesterday and 1:40pm, not heard anything from them despite, my replies, since.
... View more
May 20 2019
8:11 AM
This is now hitting our tablets as well. This is acting like a DDOS and Meraki seems to be really slow at acknowledging the problem.
... View more
May 20 2019
5:29 AM
I've raised a high level ticket with support a few hours ago. Still not had a reply on it. If it's anything like my last ticket about another issue, they'll probably just point me to the help file again ):-(
... View more
May 20 2019
3:33 AM
Just done a firmware update on my HRY-LX1 work phone and it's now doing it on that. Doesn't do it once Meraki is uninstalled so clearly an issue with Meraki. They pushed out a buggy update I wonder.
... View more
May 20 2019
3:13 AM
I don't think there is for iPhones due to the privacy settings recently pushed to them. Which allows a user to block people from tracking them. It's mentioned in the Meraki help "Forcing GPS Location Due to Apple end-user privacy restrictions, it is not possible for EMM vendors to force GPS location on iOS devices without user notification, nor is it possible to permanently lock location services to be enabled. The one exception to this is using 'Lost Mode', which can be found in the MDM commands on the Client Details page. Lost Mode forces location services on, while disabling all other functionality on the device. This can be used as a tool to remediate non-compliant users who are blocking location service requests from Systems Manager."
... View more
May 20 2019
3:02 AM
We're having the same issues. Someone has just reported this and happening on 2 devices so far. Other engineer here has uninstalled Meraki, reinstalled and the setting gets set back to 0 seconds again with no option to override. Looking like a bug in Meraki? SM-A300FU are the two phones at the moment, I suspect we are going to get more.
... View more
May 7 2019
12:44 AM
Hi Kevin Thanks for the reply. The maps are now working, the GPS location still isn't even though the SM app has the correct permissions on the phones and runs in the background. We'll raise a ticket.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 5 | 28698 | |
| 2 | 15083 | |
| 2 | 15089 | |
| 1 | 15013 | |
| 1 | 15049 |
© 2024 Cisco Systems, Inc.
