Is anyone else seeing macOS Sonoma not respecting the delay within the restrictions payload?
I have the delay for Major software updates set to 90 days. In addition I also have a software restriction setup for "Install macOS Sonoma.app". Not sure how my users / systems are being updated?
 
 
Best answer by JoeRonin
False alarm. A lesson to always review config profiles before posting ;)
Upon closer inspection. This is due to a config profile that have setup to get around 13.4.1 upgrade issue (https://community.jamf.com/t5/jamf-pro/13-4-1-upgrade-fails/m-p/294319). We have about 50 systems under this OS version and are scoped to a config profile with no delay. False alarm.
False alarm. A lesson to always review config profiles before posting ;)
Upon closer inspection. This is due to a config profile that have setup to get around 13.4.1 upgrade issue (https://community.jamf.com/t5/jamf-pro/13-4-1-upgrade-fails/m-p/294319). We have about 50 systems under this OS version and are scoped to a config profile with no delay. False alarm.
Hi @JoeRonin Facing the same even raised Jamf support case but not help at all, is it fixed at your end, it seems that some of the devices are getting slipped through the restricted profile and being updated.
is there a way to fix this in the config profiles payload in jamf? i have 16 users able to download the sonoma os even though we have a config profile and restrictions set in place hahaha
is this more my fault? or is this something on apples end?
This article provides steps to restrict macOS Sonoma from being installed via System Settings/System Preferences on computers managed by Jamf Pro using a Custom JSON Schema deployed with a Jamf Pro configuration profile.
6. Additional fields to be completed will populate:
a. Enforced Software Update Major OS Deferred Install Delay: Use the dropdown to select Configured, and in the additional box that appears set the value (1-90) for the number of days to restrict the update.
b. Force Delayed Major Software Updates: Use the dropdown to select Configured, and set the additional box to True.
7. Click Scope and add a test computer or test computer group to ensure the update is blocked.