Skip to main content
Solved

Prevent name change on iPads?

  • December 21, 2011
  • 6 replies
  • 64 views

Forum|alt.badge.img+19

Hi all,

I don't think we can lock it down but I though I'd double check just in case!
Can you prevent a user from changing the name of their iPad? I have one school in particular who are frustrated by students constantly changing the name the device.

There doesn't seem to be anything in restrictions. Can anybody confirm or enlighten me?

Best answer by davelb20

Zvordauk,

As far as I know that is not an available MDM Feature, yet.

Dave

6 replies

Forum|alt.badge.img+7
  • Contributor
  • Answer
  • December 21, 2011

Zvordauk,

As far as I know that is not an available MDM Feature, yet.

Dave


Forum|alt.badge.img+19
  • Author
  • Employee
  • December 22, 2011

Thanks for the confirmation Dave.

Regards,
Ger...


Forum|alt.badge.img+3
  • New Contributor
  • January 5, 2018

It must be avilable because we have both AirWatch and Jamf, and AW supports this feature.


Forum|alt.badge.img+21
  • Valued Contributor
  • January 10, 2018

You can enforce a mobile device name from General > Edit. The device name can be manually changed but it'll revert to what you have set the next time it checks in.

Hopefully OP learned of this in the two years it's been available...


Forum|alt.badge.img+26
  • Esteemed Contributor
  • January 10, 2018

You can also enforce this from the Prestage Enrollment Profile as well as with a Configuration Profile.
It does get a little dicey if you use more than one source for this :)


Forum|alt.badge.img+8
  • Valued Contributor
  • January 10, 2018

I have this covered with 2 things:
1- Configuration Profile that pushes the restriction - Allow modifying account settings (supervised only) unchecked.
2- In the General tab of the inventory record, Enforce Mobile Device Name is checked.

We had students changing the name on the iPad and then AirDropping inappropriate items. Using just #2, the could change the name then it would default back before we could catch them. With #1 in place, they can't change the name in the first place.
During mass deployment I push this out when we are done.