EAs not getting set

Question

EAs not getting set

wcwelch opened this issue 5 years ago · comments

About a week ago, I used version 5.0.5 to set values for a number of EAs. I am starting to hear from end user that there devices are not grouped. When looking into it, it appears that the EA values were not set. I went back and looked at mut.log and it's not showing any errors for the SNs I look up.

In one "batch" in particular, out of 550 devices, 6 were not set. For this batch of iPads, I was only setting one EA to "2026".

I know this isn't much to go on, but it's all I have.

Mike Levenick · Answer 1 · Fri Sep 06 2019 21:36:17 GMT+0800 (China Standard Time)

Interesting. Can you please try trimming down the CSV file to just the devices that didn't work (or at least a couple of them) and try again, to see if the behavior persists?

wcwelch · Answer 2 · Sun Sep 15 2019 01:32:10 GMT+0800 (China Standard Time)

Looks like this is a bug within the JSS, not the MUT.

…

On Fri, Sep 6, 2019 at 9:36 AM Mike Levenick ***@***.***> wrote: Interesting. Can you please try trimming down the CSV file to just the devices that didn't work (or at least a couple of them) and try again, to see if the behavior persists? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAM4UWRCXIH4SVUQI746IWLQIJMFHANCNFSM4IUJBEIQ> .

wcwelch · Answer 3 · Tue Sep 17 2019 02:56:44 GMT+0800 (China Standard Time)

Bug is PI-007467. When a device checks into JAMF via Self-service, a "timing issue" can occur. When this happens all EAs for that device are erased causing the iPad to lose all apps and restrictions.

Mike Levenick · Answer 4 · Sat Feb 08 2020 03:32:47 GMT+0800 (China Standard Time)

@wcwelch Glad to hear it was not a MUT issue. Let us know if there's anything else we can do to help!