Skip to main content
Question

Prestage "Enforce Mobile Device Names" Not Working

  • October 9, 2025
  • 8 replies
  • 157 views

Forum|alt.badge.img+8

Updated to Jamf Pro 11.21 yesterday afternoon and have found that when enrolling iPads with a name set in Prestage and the “Enforce Mobile Device Names” option checked, the device record will have the checkbox unchecked when I click Edit on the general tab.  I see 11.21.1 is out this morning, perhaps need to update again and see if this was silently resolved?

8 replies

Chubs
Forum|alt.badge.img+21
  • Jamf Heroes
  • October 10, 2025

PI141235 - "Settings - Device Name" Not Working with Jamf Pro 11.20. When a previously enrolled mobile device is moved to a new PreStage with the "Enforce Mobile Device Names" option enabled and is re-enrolled (without deleting the device record in Jamf Pro), the device name is not updated to the new PreStage naming convention (even though the "Settings - Device Name" command is completed).
 

I believe you’re hitting some attribute of this PI. 


Forum|alt.badge.img+8
  • Author
  • Contributor
  • October 10, 2025

PI141235 - "Settings - Device Name" Not Working with Jamf Pro 11.20. When a previously enrolled mobile device is moved to a new PreStage with the "Enforce Mobile Device Names" option enabled and is re-enrolled (without deleting the device record in Jamf Pro), the device name is not updated to the new PreStage naming convention (even though the "Settings - Device Name" command is completed).
 

I believe you’re hitting some attribute of this PI. 

Hmmm that sounds like it might be the issue.  These are devices that have the record deleted already so not exactly the case of the PI but probably related then.  Guess we’ll be manually checking now and watching for an update on that PI.


Forum|alt.badge.img+1
  • New Contributor
  • October 22, 2025

Any idea why this PI is not published in the known issues.


Chubs
Forum|alt.badge.img+21
  • Jamf Heroes
  • October 22, 2025

Probably because it’s an internal PI and will be fixed quickly.  Published PIs are ones that are seemingly chronic...


Forum|alt.badge.img+8
  • Author
  • Contributor
  • October 28, 2025

I’ve wondered that as well.  We did upgrade to 11.21.1 to see if that would fix it silently but no change.  I’m not saying it’s chronic or not chronic but at this point we’ve waited to enroll some larger quantities of iPads for a project for this to be fixed but it’s been nearly a month so now we go touch each device record and edit>checkmark the box.  Perhaps a ticket is in order...


Chubs
Forum|alt.badge.img+21
  • Jamf Heroes
  • October 28, 2025

I’ve wondered that as well.  We did upgrade to 11.21.1 to see if that would fix it silently but no change.  I’m not saying it’s chronic or not chronic but at this point we’ve waited to enroll some larger quantities of iPads for a project for this to be fixed but it’s been nearly a month so now we go touch each device record and edit>checkmark the box.  Perhaps a ticket is in order...

I’d recommend throwing in a ticket with your CSM so that you’ll be added to the list of notifications when it’s resolved.


Forum|alt.badge.img+1
  • New Contributor
  • October 28, 2025

Jamf has indicated that a tentative fix for this issue is expected to be implemented in a future release, with an approximate target of mid-November. Until then keep editing each device record or deleting the record before re-enrollment for moved prestaged devices.


Forum|alt.badge.img+8
  • Author
  • Contributor
  • October 28, 2025

I’ve wondered that as well.  We did upgrade to 11.21.1 to see if that would fix it silently but no change.  I’m not saying it’s chronic or not chronic but at this point we’ve waited to enroll some larger quantities of iPads for a project for this to be fixed but it’s been nearly a month so now we go touch each device record and edit>checkmark the box.  Perhaps a ticket is in order...

I’d recommend throwing in a ticket with your CSM so that you’ll be added to the list of notifications when it’s resolved.

Just sent in, the chatbot was supposedly connecting me with someone then switched to they’ll get back to me in a few hours, which is fine, just wanted to get ‘on the list’.

 

Jamf has indicated that a tentative fix for this issue is expected to be implemented in a future release, with an approximate target of mid-November. Until then keep editing each device record or deleting the record before re-enrollment for moved prestaged devices.

Unfortunately the device’s we’re enrolling have already been deleted, so we’re seeing it with any iPad that enrolls.