search

jamf / mut

MIT License
134 stars 10 forks source link

Error 400! #15

Closed blurunnner closed 6 years ago

blurunnner commented 6 years ago

Hi, what does it mean when I get "Failed! - 400!" as an error code?

mike-levenick commented 6 years ago

Hello. It depends on the situation. My recommendation is to turn on "advanced debugging" from the settings menu at the top, and see what the specific error that it reports is.

If you would like, you can turn on advanced debugging, and then save the whole log file and post it here and I'd be happy to take a look.

screen shot 2018-08-09 at 12 00 15 pm screen shot 2018-08-09 at 12 00 24 pm

blurunnner commented 6 years ago

Hi Mike, thanks. Attached is the file. MUT-Output-2018-08-09_16.03.log

My thought: Most of these devices are added to JAMF in pre-enrollment, but they haven't actually been turned on to have the profile installed. Do you think that is it?

mike-levenick commented 6 years ago

Ahh, yes. You got it.

MUT updates Mobile Device Names a bit differently than it updates any other field. In order to enforce the name change so that it sticks, MUT will actually generate an MDM command on the device to update the name.

This MDM command requires that device name changes are not blocked (restriction payload on a configuration profile), and they also will not actually take effect until the device processes the MDM command.

If another name change is submitted via MUT before the first name change command actually processes, you will receive a 400 error, and it will state that the command is already pending under Advanced Debugging. You can see this pending command on the management section of the device record.

To get the name changes to actually take effect, the device has to be turned on, on network, MDM capable, talking to Jamf Pro, and all that jazz—as soon as it processes the MDM command that's pending, the name will update.

blurunnner commented 6 years ago

Thanks, I'll try it again once they're all up and running!