Is it just me or is this forced update feature not working for you too? Noth
Is it just my system or is this not working for you too? Updates do not get forced and we are all on Sonoma.
Solved
Forcing updates using the new Software Update feature
+5Best answer by sdagley
WARNING! - PI116287 "Scheduled Software Updates (DDM) using Specific Versions Does Not Work"
Apparently I was incredibly lucky that using a DDM Scheduled Update specifying version 14.2.1 actually worked because there is a bug in the current implementation that generates malformed DDM commands. Use the "Latest version based on device eligibility" or "Latest minor version" options to schedule an update instead.
This bug is present as of Jamf Pro 11.2.0, and reportedly will not be fixed until after Jamf Pro 11.3.0 is released.
+20@mvu Thanks for the details, much appreciated. Ill keep you posted on my DDM testing over the next few days (and my 'big test' Saturday night to ~25 IT production Macs).
I just noticed that some of my test Macs reported AvailableOSUpdates - Scheduled, ScheduleOSUpdateScan, AvailableOSUpdates, ScheduleOSUpdate and OSUpdateStatus - Scheduled, but did not report "DeclarativeManagement" in their Jamf Management History logs.
Does this mean that DDM protocol wasn't used for the OS updates? These particular Macs are M1 Macs running Sonoma 14.4.x. and should be capable of DDM. My JSS is 11.5.1 (Cloud). Im confused here.
The success rate of all these Macs (when NOT using a schedule) is 100% - even on Macs that are asleep, idle, etc. I have tested ~10 Sonoma Macs (Intel and ARM) and the only Macs that have failed have been the jobs with scheduled commands. Any commands I have sent that are "Update to Latest minor version" + "Download Install and Restart" (forced) are working great thus far.
I checked some of my Macs: I see similar results as you mentioned. Some have it, some don't. None of your Macs had "DeclarativeManagement" in it?
I'm guessing Jamf is using the old MDM command for the update and force restart then. Not DDM. Jamf would know.
Ok, nice. I might use this for some of mine. Keep us posted on your results.
+19I checked some of my Macs: I see similar results as you mentioned. Some have it, some don't. None of your Macs had "DeclarativeManagement" in it?
I'm guessing Jamf is using the old MDM command for the update and force restart then. Not DDM. Jamf would know.
Ok, nice. I might use this for some of mine. Keep us posted on your results.
Like you observed, some logs have DeclarativeManagement some do not.
+5I am not seeing the success I would expect. I sent the update request with 3 deferments 6 days ago and I am still seeing users with the pending command in the device record...
+5I am also getting no joy on this also to any of our iPhones on ios 17x trying to upgrade using the schedule to ios 18 i am not using a specific version and it never works on any devices.
Will keep doing some testing and see if anything works.
+20Are you running a newer version of Jamf? Also, have you tried turning off and ON the Software Update Feature? Your devices Supervised?
+5Are you running a newer version of Jamf? Also, have you tried turning off and ON the Software Update Feature? Your devices Supervised?
Yes on all counts
+20Yes on all counts
The other gotcha I had...
When I was having trouble with DDM, I reverted back to the old MDM update commands.
Once the fleet got the old commands, I couldn't cancel them or send a new DDM. I had to wait until another iOS release and then used DDM.
What do your logs look like for a device that won't update?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.