About DamonBCSA

DamonBCSA · ‎11-24-2020

For anyone that comes across this same problem, I lodged a ticket with Meraki, and whilst they looked at it, there was no fix coming, just saying it was an issue with Samsung. They also went with the possibility of the knox security bit being flagged (but like I said, brand new, straight from the factory devices, so I know they never had any other OS images on them) As luck would have it, these new A7's are bleeding edge, so over the last 3 weeks there have been 2 OTA updates, the first one didn't fix anything, but the second that arrived yesterday has resolved the issue and we can now register the devices. The only down side is you have to skip through the setup without using the MDM so you can run the software update on the tablet, then factory reset it so you can then put the device on the MDM, but at least it works.

DamonBCSA · ‎11-05-2020

I've just purchased fifty Samsung Tab A7's , and I've also go the problem straight out of the box complaining that the device can't create a work profile due the security policy claiming a custom OS on the device. These devices are new out of the box and I've made sure that the security police within Meraki does not have the "Device is not compromised" checked. I'll be logging a support ticket, but judging from other posts in this thread, I'm not holding much hope.

DamonBCSA · ‎05-14-2020

Hey PhillipDAth, thanks for the reply, I didn't mean I want to lock the phone down to stop accessing the boot loader menu options. i'm talking about the factory reset protection ie. when you go to register the device and put your email address in, it verifies your account against what was registered as the owner account on the phone before it was reset. ie. at the point where we put in afw#meraki From the link I provided, it looks like Meraki has disabled this option at the backend by default, which is good for those people who no longer have access to the email account that was used to register the device, but it's bad if the device is lost/stolen and you want to stop someone using the phone again. I never had to look for this option in either Airwatch or Mobileiron to see if it could be activated/deactivated from the MDM side as it was just always on by default, which Meraki apparently changed from On by default to Off by default back in 2018 according to my link in the original post.

DamonBCSA · ‎05-13-2020

Hey there, I'm relatively new to the Meraki MDM, having previously used Airwatch and MobileIron, so I'm not totally new to the world of MDM. Our current policies and settings are fine and prevent anyone resetting the device once Meraki is installed an enabled via the settings menu. However I've recently discovered that even though we are registering the devices in Device Owner mode and the AFW account is enabled, that if a phone is reset via hard reset using the Android Recovery option, that you can then just register the phone again as anyone. After some trawling through these forums I've found out that Meraki have disabled Factory Reset Protection for AFW by default sometime in 2018 as per this posting https://community.meraki.com/t5/Endpoint-Management-Systems/Disable-factory-reset-protection/m-p/11128#M1378 My question is how can I either setup AFW's factory reset protection to default on, or at the very least, re-enable it so if a device is stolen/lost (or in our case some mischievous clients) and they do a reset that the device can't be setup again and/or they need to contact our IT department to reconfigure the phone so we can get it back in the MDM. cheers

DamonBCSA

Community Record

Re: Meraki, custom rom and work profile

Re: Meraki, custom rom and work profile

Re: Enabling AFW's factory reset protection

Enabling AFW's factory reset protection