Skip to main content

Okay we’ve never had this issue in the past.  The prestage enrollment naming requirements ALWAYS take precedence...but for whatever reason, this is not the case.  

Workflow to replicate:

  1. Move device (currently named PS1-Serial) from one prestage to another 
  2. Perform “wipe” command from Jamf
  3. Enroll device under new prestage with new name PS2-Serial

Unfortunately on step 3, the device ends up with a PS1-Serial name for whatever reason.  Did I miss a PI (product issue) behind this?  Is this known behavior? Or am I just losing it from the week of crazy JAMF PIs that I’ve found?!

Going to answer my own question. 
 

PI141235: Settings - Device Name not working with JAMF Pro 11.20

Hi ​@Chubs ,

I’ve experienced the same issue before.
After investigating, I found the root cause was the “ Enforce Mobile Device Name “ setting.
When this option is enabled, if you remove Jamf and then re-enroll with another user, the device name will remain the same as before. You’ll need to disable this setting.

 

Hi ​@Chubs ,

I’ve experienced the same issue before.
After investigating, I found the root cause was the “ Enforce Mobile Device Name “ setting.
When this option is enabled, if you remove Jamf and then re-enroll with another user, the device name will remain the same as before. You’ll need to disable this setting.

 

We’ve had this enabled since we have had JAMF and never had an issue until JSS 11.20(.x). 

Hi ​@Chubs ,

I’ve experienced the same issue before.
After investigating, I found the root cause was the “ Enforce Mobile Device Name “ setting.
When this option is enabled, if you remove Jamf and then re-enroll with another user, the device name will remain the same as before. You’ll need to disable this setting.

 

We’ve had this enabled since we have had JAMF and never had an issue until JSS 11.20(.x). 

If there are any updates or new information from Jamf,
could you please share them in this post?

Back on Jamf 11.19 I had a different issue (the device activation code did not appear), which was resolved after updating to 11.20. However, it seems another issue has come up (though I haven’t experienced it myself yet). At the very least, this helps us determine whether the issue is coming from Jamf or not.

Terms & ConditionsCookie settingsAccessibility statement