User Profile
Leo
Level 1.5: Cupcake
Joined 2 years ago
User Widgets
Contributions
Re: Factory reset notice after enrolling device
Well they're coming out of box like this Michel , as we don't have any control over exactly what the stock from our resellers has on them. The stock was likely from Samsung from a while back, then it sits somewhere for a while etc.. etc.. Our enrolment process is still done by IT teams, but is run pretty lean, so doesn't include applying updates before sending devices out. But of course if we'd known about this gotcha with these models then we could have taken some action to avoid it.2.8KViews0likes0CommentsRe: Factory reset notice after enrolling device
Lizzie I think I might have found our answer (although the description is not quite the same). https://docs.samsungknox.com/admin/knox-platform-for-enterprise/kbas/kba-1120-unable-to-enroll-device-with-zero-touch-enrollment/ Similarities are: Devices getting the reset prompt are A54's. These devices are on ONE UI 6.0. Differences are: Google Play Services are already above v23.34.14 (24.31.37 (190400-662270918)) The devices do enrol into our MDM via GZT ok. It's after being enrolled they are prompted to reset. Still, I think this has to be it, as when we enrol them a 2nd time, they appear to be fine, which is maybe because out of the box they are on v23.xxx, but then when completing enrolment this is likely getting updated before we are able to check the version. Then 2nd time enrolment, no issue because its above 23.xxx.3KViews0likes2CommentsRe: Factory reset notice after enrolling device
Lizzie ok thanks for confirming, that sounds inline with what I was thinking from previous testing we completed before adopting GZT. However, when you say screen recording and/or bug report, at which point would this be required? As all the important stuff happens during enrolment where we have no ability to do either (device not usable while being enrolled). After this, the device is enrolled, but nothing of interest is happening. Then seemingly randomly a device might hit this issue, but we have no way of knowing when/why in order to prepare for it. What I would like to suggest for a future improvement, is some form of logging from the GZT admin console. Currently there's no logging we can check to try and troubleshoot what GZT is actually doing behind the scenes. If there was, then maybe we could see what happened for a particular device etc... Regards, Leo3.1KViews0likes0CommentsRe: Factory reset notice after enrolling device
Thanks for the reply Lizzie, Yeah that could be the case (not enrolled over wi-fi etc), but I didn't realise this was in any way a pre-requisite. Can you not enrol a GZT registered device into your MDM/EMM over LTE/mobile network? If that's not a valid enrolment path when using GZT, then it could cause us lots of issues, as users don't always have access to a good wi-fi network when the device is enrolled. In Australia, we have lots of variation with network bandwidth/capacity/availability, whereby some places might have better LTE than fixed line, and vice versa. I'm sure this wasn't the case when we first setup GZT around 12-18 months ago, did something change? Thanks, Leo3.2KViews0likes0CommentsFactory reset notice after enrolling device
Lizzie, is there a known reason for this to still be occurring? EDIT: sorry just realised this was specific to the Play store not updating, BUT this article is getting referenced elsewhere as the reason for GZT having issues which then cause the device to reset. So what I'm actually asking is whether there are any other known reasons for GZT continuing to have this issue even though the Play store update issue has been fixed. Samsung A Series Devices Android v14 Work Managed GZT > WS1 MDM Play store version is up to date on 42.xx Enrolment completes, then shortly after we get the GZT warning it needs to reset. *[Post moved to create a new topic - title updated]3.5KViews0likes9CommentsRe: Random factory resets after devices complete GZT configuration.
Hi there, we're also seeing this issue on Android v14 devices just in the last couple of days. The article referenced, talks about v11 devices with Play Store version not updating higher than 35.2.19 but our devices are above this version on 42.xxx. Does anyone know if there are any other common denominators2.6KViews0likes0Comments