2 weeks ago
Hello all
I am blocking Macos Sonoma beta with two different restricted software setups, one is Install macOS Sonoma beta.app and the other is "Install macOS 14 beta.app" Im using both just to be safe and make sure I catch the installer .
With the production relase of MacOS Sonoma around the corner I was wondering if anyone has setup their environment to block macos sonoma already. Im looking for the process name
Thank you again
2 weeks ago
I'm sure it will follow the same naming convention but there is no way to tell until its released.
I've got mine set to block "Install macOS Sonoma.app"
2 weeks ago
You can search discussions for blocking Ventura, its the same.
2 weeks ago
Yea I have my deferral set for 90 days in Jamf already, this is just incase people try and download it in other ways
2 weeks ago
This also is the new way to block folks running the beta OS, as well. Under your Software Update payload is a check-box to enable/disable installing macOS beta releases. Create one for those who are allowed to pre-test the Software, leave unchecked for all others.
2 weeks ago
Do i leave the others checked and just uncheck the beta one?
2 weeks ago
a week ago
Hello All can i get confirmation if this restricted access i did to kill the mac os sonoma beta will work?
a week ago
As far as I am aware there is not an install macOS Sonoma Beta.app. Your restriction on install macOS Sonoma.app should work fine, however I strongly suggest testing this yourself. Keep in mind blocking install macOS Sonoma.app wont do anything on Macs running greater then 12.3.1 as they will never download the app to upgrade.
a week ago
sorry can you elaborate on that. What do you mean by they will never download the app to upgrade?
a week ago
I mentioned this in another comment on this thread. Apple changed how macOS Major upgrades are installed with macOS 12.3.1. The install macOS XYZ.app is no longer downloaded. Instead the update comes down as a delta, and there is no way to block it aside of a configuration profile.
I did mistype and put 11.3.1, it was 12.3.1.
You can search discussions for blocking Ventura, its the same.
- Macs running macOS 11.3.1 or newer will not download install macOS Sonoma.app. So, blocking that installer really does not do anything other stopping people who download the app manually, still a good idea to block but wont help much.
- MacOS 11.3.1 and newer will download Major Software updates as a delta, the ONLY way to block this is with a OS update deferral configuration profile. You cannot defer longer then 90 days.
Monday
so if all macs are on ventura they will not be able to download the sonoma beta?
Thursday
No, @AJPinto is just saying it doesn't download a complete installer, just an update containing the necessary files to upgrade to macOS 14.
You don't really need a software restriction to block OS betas anyway, it's a simple checkbox available in a configuration profile:
Thursday
hmmm okay thank you for the info let me ask you is it possible to block the sonoma 14 beta? in the restricted software sections or is it different this year where you are unable to at all?
I am only asking because i asked a lot of people and i am getting mixed answers people are telling me yes where others are telling me no and to create a config profile
Thursday
I'm honestly not sure, but my guess is yes since it is possible to download a full installer. This thread seems to support that: https://community.jamf.com/t5/jamf-pro/blocking-sonoma-developer-beta/m-p/292714
Friday
The old-school method to block software updates involved setting Restricted Software process blocks for the software that you wanted to deny. In Ventura's case, it was a combo of blocking the InstallAssistant, Ventura as a process, and I also blocked Install macOS Ventura.app. You can change both scoping and wording to affect different outcomes. For Sonoma, your process names/app names would just be updated to reflect that. I would feel like the Configuration Profile restriction would be more effective though.
Friday
even with restricting install assistant did not work for me, does it work on your end?