We are trying to figure out why most of our Macs updated to macOS 15.6.1 after I used Software Update in Jamf Pro to enforce getting Macs updated to macOS 15.6. When I set the update to go out, I specifically selected 15.6, not 15.6.1. I always check a few Macs in the group I selected to update to verify that they received the correct scheduled update. I confirmed that they had received the scheduled update for 15.6. Right after pushing out another update command, I saw that my own Mac already runnning 15.6 displayed an alert that it would update to 15.6.1 at the scheduled time. We have a profile installed that defers updates for 21 days. I confirmed that it is working using Macs not yet updated to 15.6. They all show 15.6 in Software Update. Macs running 15.6 do not show updates available. I wonder if the enforced update is responsible for this. I was very careful to specifially select 15.6 as the update we wanted to run. Has anyone else seen this behavior?
Using Jamf Pro software update to enforce 15.6 installed 15.6.1 instead
+23
+7What’s your profile look like to defer the updates?
+23I found out that DDM does not work with deferrals. The deferral profile is working as it should. I tested it on Macs not yet updated to 15.6. They all show 15.6 available in Software Update. Looking at my own Mac and reading over the logs from the enforced update, I see something really strange.
eventReceivedEpoch" : 1755900010478,
If you convert that epoch time using “/bin/date -r 1755900010478” in Terminal, the human readable date and time is April 3, 57612. Really? So the update event was received over 55,000 years in the future?
AppleCare Enterprise thinks this may have been caused by Software Update having the setting turned on to automatically install security updates. We have automatic updates turned off using a profile that sets the Apple Software Update settings. I have automatic update checks and downloads turned on but not automatic updates. 15.6.1 fixes a really bad vulnerability. I received a request from our cyber security department to run this update as soon as possible so this is not all bad. I’m just annoyed that this happened. I know that I definitely did not use the option to install the update based on device eligibility. That would definitely install 15.6.1. I had forgotten that DDM does not care about deferral profiles until someone in the Mac Admins slack reminded me.
+23Regarding my previous post… I found out this morning that the “eventReceivedEpoch” value is in milliseconds. 1755900010478 converted to seconds is 1755900010 which is 8/22 17:00 CDT. I have been working a lot with using epoch time in my scripts. I am confused why this process uses milliseconds but I’m happy to have found this out.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.