Skip to main content

So currently we have all iPads under a group policy that locks the name, and prevents any changes.
At the end of the year students have been resetting their ipads from the settings menu (against our instructions). We have found that if you erase all content and settings, the name will be pushed down and locked again once its on the network (as expected). However, if you just "reset all settings" the ipad name not only reverts to ipad on the actual device but in the jss inventory as well. This has caused a huge unexpected problem, since there are now hundreds of ipads to rename. The only way to prevent this is to individually "enforce mobile device name". Why does the group policy not work for this one particular reset? is anyone else experiencing this problem?

If you use an API command to set the device name, base on my observation that also checks the box.


Why don't you supervise the iPads and use a config profile to restrict the ability to access certain menu items like a full reset? That way they can't erase the device, which ticks the box in terms of you not wanting them to be able to.


we have also noticed our ipads once reset do not retain their static group memberships - everything is wiped when the device rejoins using DEP


The ipads are supervised. The problem is that you can only restrict access to "reset all settings" there is no restriction to disable "reset all settings" which is the problematic reset that reverts the name to ipad and removes it from all static groups.

And the names are locked via the configuration profile, but the only way to prevent the name wipe during "reset all settings" is to individually "enforce mobile device name" and that is very difficult to do with thousands


Have you looked at The MUT?

Make a spreadsheet of the device serial numbers and what you want the name to be, and it will rename, send a command and check the enforcement box.