-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
super[35251]: Error: Failed to send MDM install update/upgrade macOS request. Verify that this account has appropriate privileges #172
Comments
That means the Jamf API failed to accept the update/upgrade command. More specifically, You'll have to acquire a super.log in |
Thanks for your swift response, super is trying to upgrade to 13.6.2 (latest Ventura release as of 7th Nov 23) as per my flag to target v13, but doesnt seem to find the update to download. Please see below excerpts from logs Super.log: -- [...] === OS Update Item === [...] ASUListCache = ( As you can see 13.6.2 is not being downloaded hence the install is failing, the only available updates are to safari17.1, MacOS12.7.1 and MacOS14.1.1 |
You've cut out a lot of the super.log... so while your conclusions may be correct about the output from In fact, one of the fixes in |
Also looking back further in this thread... your original issue was related to the API call failing... which is not directly related to what |
So I noticed and this log confirms that 13.6.2 is being seen as a major update. If you have a defer major updates for X days it may not process. I think super itself should not have an issue but it would definately get blocked by that deferral.Sent from my iPhoneOn Nov 15, 2023, at 1:28 PM, Kevin M. White ***@***.***> wrote:
Also looking back further in this thread... your original issue was related to the API call failing... which is not directly related to what super does if it's going to pre-download an update or upgrade.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Please try the latest release of |
Two thirds of our machines have successfully been upgraded using v4 script with jamf mdm profiles/policy. Seemingly out of nowhere every remaining machine is now failing with the above error (regardless of current os, hardware version, etc.)
I'm not suggesting it's an error with the script as it clearly worked fine, just wondering if anyone else has seen this issue..?
The text was updated successfully, but these errors were encountered: