Can't update computer-prestages

[ckay-unsw]

Even when I try a basic update to a computer pre-stage like in your --help examples I get the following error:

echo '{"name":"Test 2"}' | jamf-cli pro computer-prestages update 100
{
  "error": "general",
  "exitCode": 1,
  "message": "request failed (HTTP 500): {\n  \"httpStatus\" : 500,\n  \"errors\" : [ ]\n}"
}

More complex updates get the same error:

jamf-cli pro computer-prestages get --name "${PreStageName}" -o json | jq --arg packageId "$PackageID" '.customPackageIds = [$packageId]' | jamf-cli pro computer-prestages update --name "${PreStageName}"
{
  "error": "general",
  "exitCode": 1,
  "message": "request failed (HTTP 500): {\n  \"httpStatus\" : 500,\n  \"errors\" : [ ]\n}"
}

[neilmartin83]

I am seeing the same since Jamf Pro 11.28 across direct Pro and Platform APIs. 500 on PUT, but a GET shows the fields actually updated where they are supported (I probed a ton of them).

Have raised this internally. Please raise a support request as well (to add customer-backing) and quote JPRO-20316 for correlation (this is the case I created with detailed logs/info).

Right now - the workaround is when you see a 500 response, do a GET and check that the field you changed persisted successfully.

[ckay-unsw]

So this issue isn’t limited to computer-prestages but the entire API? That workaround doesn’t seem to help in my case. Its not updating the prestige when I look. On 3 Jun 2026, at 8:49 pm, Neil Martin ***@***.***> wrote: [https://avatars.githubusercontent.com/u/10920581?s=20&v=4]neilmartin83 left a comment (Jamf-Concepts/jamf-cli#231)<#231 (comment)> I am seeing the same since Jamf Pro 11.28 across direct Pro and Platform APIs. 500 on PUT, but a GET shows the fields actually updated where they are supported (I probed a ton of them). Have raised this internally. Please raise a support request as well (to add customer-backing) and quote JPRO-20316 for correlation (this is the case I created with detailed logs/info). Right now - the workaround is when you see a 500 response, do a GET and check that the field you changed persisted successfully. - Cameron Cameron Kay Senior Specialist Desktop and Infrastructure Level 11 Library Building, UNSW, Sydney, NSW 2052 UNSW IT p: 61 401 712 925 f: 61 2 9385 1170 ***@***.*** www.unsw.edu.au CRICOS Provider Code 00098G This email and any files transmitted with it may contain confidential information. If you believe you have received this email or any of its contents in error, please notify me immediately by return email and destroy this email. Do not use, disseminate, forward, print or copy any contents of an email received in error.

[neilmartin83]

This specific issue is only happening for Computer PreStages.

It will return 500 whether the request is valid or not. The endpoint is strict and has some required fields - you need to ensure you're including all the required fields in the request body. https://developer.jamf.com/jamf-pro/reference/put_v3-computer-prestages-id

I'm marking this issue as "wontfix" here because it's not a jamf-cli problem. Will keep this open in the meantime and close when JPRO-20316 is resolved.

Cheers!

[ckay-unsw]

Here’s my example script that’s failing PreStageName="Test" PackageName="Microsoft_Intune_Company_Portal_5.2604.1.pkg" PackageID=$( jamf-cli pro packages get --name "${PackageName}" --field id ) jamf-cli pro computer-prestages get --name "${PreStageName}" -o json | jq --arg packageId "$PackageID" '.customPackageIds = [$packageId]' | jamf-cli pro computer-prestages update --name "${PreStageName}" So I’m basically updating just the customPackageIds property and still failing with 500 On 5 Jun 2026, at 12:58 am, Neil Martin ***@***.***> wrote: [https://avatars.githubusercontent.com/u/10920581?s=20&v=4]neilmartin83 left a comment (Jamf-Concepts/jamf-cli#231)<#231 (comment)> This specific issue is only happening for Computer PreStages. It will return 500 whether the request is valid or not. The endpoint is strict and has some required fields - you need to ensure you're including all the required fields in the request body. https://developer.jamf.com/jamf-pro/reference/put_v3-computer-prestages-id I'm marking this issue as "wontfix" here because it's not a jamf-cli problem. Will keep this open in the meantime and close when JPRO-20316 is resolved. Cheers! — Reply to this email directly, view it on GitHub<#231?email_source=notifications&email_token=CCXOSQITXAPGTYVMNBC7HST46GFADA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGMZTGNZWGI2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4623337624>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CCXOSQJZVGFF4MSA5OGQGKD46GFADAVCNFSM6AAAAACZWMU3P6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMRTGMZTONRSGQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CCXOSQLBTUIEASS2IRELWRL46GFADA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGMZTGNZWGI2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/CCXOSQIBWDOGXWMH5FQVBOL46GFADA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGMZTGNZWGI2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***> - Cameron Cameron Kay Senior Specialist Desktop and Infrastructure Level 11 Library Building, UNSW, Sydney, NSW 2052 UNSW IT p: 61 401 712 925 f: 61 2 9385 1170 ***@***.*** www.unsw.edu.au CRICOS Provider Code 00098G This email and any files transmitted with it may contain confidential information. If you believe you have received this email or any of its contents in error, please notify me immediately by return email and destroy this email. Do not use, disseminate, forward, print or copy any contents of an email received in error.

[ckay-unsw]

Any ideas as its still not updating the package in the Enrollment Packages section of the prestige. On 5 Jun 2026, at 12:58 am, Neil Martin ***@***.***> wrote: [https://avatars.githubusercontent.com/u/10920581?s=20&v=4]neilmartin83 left a comment (Jamf-Concepts/jamf-cli#231)<#231 (comment)> This specific issue is only happening for Computer PreStages. It will return 500 whether the request is valid or not. The endpoint is strict and has some required fields - you need to ensure you're including all the required fields in the request body. https://developer.jamf.com/jamf-pro/reference/put_v3-computer-prestages-id I'm marking this issue as "wontfix" here because it's not a jamf-cli problem. Will keep this open in the meantime and close when JPRO-20316 is resolved. Cheers! — Reply to this email directly, view it on GitHub<#231?email_source=notifications&email_token=CCXOSQITXAPGTYVMNBC7HST46GFADA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGMZTGNZWGI2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4623337624>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CCXOSQJZVGFF4MSA5OGQGKD46GFADAVCNFSM6AAAAACZWMU3P6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMRTGMZTONRSGQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CCXOSQLBTUIEASS2IRELWRL46GFADA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGMZTGNZWGI2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/CCXOSQIBWDOGXWMH5FQVBOL46GFADA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGMZTGNZWGI2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***> - Cameron Cameron Kay Senior Specialist Desktop and Infrastructure Level 11 Library Building, UNSW, Sydney, NSW 2052 UNSW IT p: 61 401 712 925 f: 61 2 9385 1170 ***@***.*** www.unsw.edu.au CRICOS Provider Code 00098G This email and any files transmitted with it may contain confidential information. If you believe you have received this email or any of its contents in error, please notify me immediately by return email and destroy this email. Do not use, disseminate, forward, print or copy any contents of an email received in error.

[ckay-unsw]

Actually my script is working, accept its deleting the password from the Accounts Settings section of the prestage. Any idea how to avoid that happening? PreStageName="Test" PackageName="Microsoft_Intune_Company_Portal_5.2604.1.pkg" PackageID=$( jamf-cli pro packages get --name "${PackageName}" --field id ) echo PackageID = $PackageID jamf-cli pro computer-prestages get --name "${PreStageName}" -o json | jq --arg packageId "$PackageID" '.customPackageIds = [$packageId]' | jamf-cli pro computer-prestages update --name "${PreStageName}" - Cameron Cameron Kay Senior Specialist Desktop and Infrastructure Level 11 Library Building, UNSW, Sydney, NSW 2052 UNSW IT p: 61 401 712 925 f: 61 2 9385 1170 ***@***.*** www.unsw.edu.au CRICOS Provider Code 00098G This email and any files transmitted with it may contain confidential information. If you believe you have received this email or any of its contents in error, please notify me immediately by return email and destroy this email. Do not use, disseminate, forward, print or copy any contents of an email received in error.

[neilmartin83]

Apologies for the delayed reply.

The prestages endpoints are really tricky/strict for a few reasons as you've found...

• It's PUT for update so you need to include every field from the existing PreStage, not just some. Strictly speaking, PUT means replace in terms of HTTP. So you essentially need to supply a complete request body that has everything in the existing PreStage with your changes. Or get the existing object, merge your changes into it, then update.
• The admin password field is write only - API does not return it on GET so you need to re-inject it yourself on an update. This is actually good security and normal/common practice for sensitive values like passwords/private keys etc. You'll see the same for other endpoints like user accounts, policies (the accounts payload) etc.
• The endpoint has quite a lot of required fields - omitting any of them will fail (more useful for POST when creating)
• The endpoint doesn't support a PATCH method, which would be better and allow for just sending only the fields you want to update/change whilst leaving others.

[neilmartin83]

This example will update the name and password. But basically you need to always have .accountSettings.adminPassword = "NewSecret123!" in your jq mutation.

jamf-cli pro computer-prestages get -o json PRESTAGE_ID \
  | jq '.displayName = "New Name" | .accountSettings.adminPassword = "NewSecret123!"' \
  | jamf-cli pro computer-prestages update -p PROFILE PRESTAGE_ID

[ckay-unsw]

Jamf support got me to include the .accountSettings.adminPassword field in the JSON each time I update the PreStage. Only problem is there’s an existing PI112813 that setting the password via the API scrambles the password and you have to go reset it via the GUI. So that basically makes using the API unusable for PreStages. - Cameron Cameron Kay Senior Specialist Desktop and Infrastructure Level 11 Library Building, UNSW, Sydney, NSW 2052 UNSW IT p: 61 401 712 925 f: 61 2 9385 1170 ***@***.******@***.***> www.unsw.edu.au CRICOS Provider Code 00098G On 10 Jun 2026, at 7:33 pm, Neil Martin ***@***.***> wrote:  [https://avatars.githubusercontent.com/u/10920581?s=20&v=4]neilmartin83 left a comment (Jamf-Concepts/jamf-cli#231)<#231 (comment)> This example will update the name and password. But basically you need to always have .accountSettings.adminPassword = "NewSecret123!" in your jq mutation. jamf-cli pro computer-prestages get -o json PRESTAGE_ID \ | jq '.displayName = "New Name" | .accountSettings.adminPassword = "NewSecret123!"' \ | jamf-cli pro computer-prestages update -p PROFILE PRESTAGE_ID — Reply to this email directly, view it on GitHub<#231?email_source=notifications&email_token=CCXOSQO4B2VX4PWSAWJPBD347ETNHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRWHA3DKMBXGA32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4668650707>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CCXOSQPMBUQTEEDNCOLDKGL47ETNHAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNJSGQ4TCMJUHE5US43TOVSTWNBVGY3TMMBWGAZTDILWAI>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CCXOSQLMLOOFABIGNCLCQWD47ETNHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRWHA3DKMBXGA32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/CCXOSQLF2BZZ6TKGGMSDWXD47ETNHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRWHA3DKMBXGA32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***> This email and any files transmitted with it may contain confidential information. If you believe you have received this email or any of its contents in error, please notify me immediately by return email and destroy this email. Do not use, disseminate, forward, print or copy any contents of an email received in error.

[neilmartin83]

I only just became aware of PI112813 a few moments ago (talking to the same colleague who has your support case!). That's frustrating - but also good that it's known about and being addressed.

For the 500 response on every PUT: PI184901