Skip to main content
Question

Update Mobile Device Name via API

B
Forum|alt.badge.img+11

Which field needs to be updated in order to change the name of a mobile device via the API?

I tried changing <mobile_devices><general><display_name>

It does indeed change the name in Jamf, but doesn't on the iPad. When I then do a Update Inventory command, Jamf changes back to the name on the iPad (instead of updating the iPad with the name from Jamf).

I can experiment, but there are 2 other fields <device_name> and <name> (why 3?). If anyone knows which is the correct, of if all 3 need to be changed, that would be useful information.

tia

3 replies

J
Forum|alt.badge.img+8
  • jrwilcox
  • Contributor
  • 82 replies
  • November 7, 2017

Please check this thread:

rename

B
Forum|alt.badge.img+11
  • bvondeylen
  • Author
  • Contributor
  • 76 replies
  • November 7, 2017

I see there is a special command to change a device name

POST /mobiledevicecommands/command/DeviceName/$name/id/$id

I will pursue this…

B
Forum|alt.badge.img+11
  • bvondeylen
  • Author
  • Contributor
  • 76 replies
  • November 7, 2017

Hmm… what permission(s) are needed by the account to perform this function?

I have an account created with Read and Update permissions, and that account cannot change the Mobile Device Name.

I am successful using an Administrative account with total rights, but I don't want that account to be used in my FIleMaker solution.

I tried going into Privileges for the Account and setting the Jamf Pro Server Actions and turning ON the following (which didn't work either).
Send Mobile Device Set Device Name Command
Send Inventory Requests to Mobile Devices
Send Blank Pushes to Mobile Devices
Change Password
Send Mobile Device Set Device Name Command

Wondering why the account gives an error message (Authentication Failed) when using the /mobiledevicecommands/command/DeviceName/{device_name}/id/{id_list} command???

What privilege am I missing?

Reply


Most helpful members this week

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings