Closed robotech99 closed 3 years ago
MUT 5.2.0 and 5.1.1 have the same behaviour, "Enforce Mobile Device Name" box not checked after batch rename mobile devices. Something must have change with the Jamf Pro version. Do we need to send a separate command via MUT to Enforce Mobile Device Name?
Hello. Can you please post a copy of the MUT.log?
The way this works is that MUT changes the name, and then generates a mobile device command to update the name. This mobile device command is what actually enforces the name. I'd be curious if MUT is throwing an error when attempting to set that name.
I'd also be curious if you see the "DeviceName" command generated in Jamf Pro, and if so, if the jamfproserver.log has anything to say about that command and its outcome.
Disregard the above. This has been filed as Jamf Pro PI-009042. I recommend you reach out to Jamf Support to get a case created and tied to the PI to help gather information and seek resolution for the issue.
@robotech99
I think you'll be excited to know this issue was resolved in MUT v6! Check it out, and let me know how it works! https://github.com/mike-levenick/mut/releases/tag/v6.0.0
As always with MUT, I strongly recommend trying out a small, test run of just a few devices before doing a massive update to your entire fleet. MUT is a very powerful tool, and while I've done plenty of testing, it is good to be careful, especially with a change as massive as this.
We are on Jamf Pro 10.26 with MUT 5.3.2 and noticed the following. When changing mobile device names the "Enforce Mobile Device Name" box is no longer getting checked in the device record. So after a batch rename the end user can change the device name, after next inventory the name in Jamf Pro will also change. Is this due to changes in Jamf Pro 10.25+ or the latest version of MUT?