I have a script that I run on machines to get them to do macOS updates and upgrades. Since the "Update plans" came out of beta I have modified my script to use plans when it is enabled.
I have noticed that on macOS 15, if the script runs while a user is logged in and I set a plan via the following:
curl --request POST \
--silent \
--url $JAMFServer/api/v1/managed-software-updates/plans \
--header "Authorization: Bearer ${authToken}" \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '
{
"devices":[
{
"deviceId": "'${ClientID}'",
"objectType":"COMPUTER"
}
],
"config":{
"updateAction": "DOWNLOAD_INSTALL_RESTART",
"versionType":"SPECIFIC_VERSION",
"specificVersion": "'${UpdateVersion}'"
}
That the macOS 15 machines will pop-up a dialog informing the user of a need to restart and it gives them the option to 'do later". Under the previous setup, when the command was sent:
curl --request POST \
--silent \
--url $JAMFServer/api/v1/macos-managed-software-updates/send-updates \
--header "Authorization: Bearer ${authToken}" \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '
{
"deviceIds": [
"'${ClientID}'"
],
"applyMajorUpdate": false,
"forceRestart": true,
"version": "'${UpdateVersion}'",
"updateAction": "DOWNLOAD_AND_INSTALL",
"priority": "HIGH"
}
The user only got the 1 min countdown.
I do not see a "priority" setting for plans and I don't think the OS is respecting the fact that no deferrals are set. Is this a change in macOS 15 or are the commands being sent by Jamf allowing deferrals?
Thanks