Today, Apple published https://support.apple.com/en-us/HT208312, which states:
As of April 21, 2022, Apple has discontinued macOS Server. Existing macOS Server customers can continue to download and use the app with macOS Monterey.https://support.apple.com/en-us/HT208312
As someone that cut my teeth with OSX Server on 10.3 (Panther), I’d like to say farewell old friend.
In addition, Apple have posted a document on choosing and MDM solution and as well have another document advising that:
Apple will discontinue Fleetsmith service on October 21, 2022https://support.apple.com/en-us/HT213238
As of April 21, 2022, Apple has discontinued new signups for Fleetsmith.
If you’re looking for a replacement for either Profile Manager or Fleetsmith, why not head over to the MacAdmins.org Slack, or reach out to folks like.. oh, I dunno.. dataJAR 🙂
Anyways, farewell macOS Server!
As forewarned by Apple a week ago, the Business Manager and School Manager Terms have been updated today.
I’ve covered this a few times, but essentially an AxM Administrator for your organisation will need to agree to the new terms.
Also the AxM Administrator(s) for your organisation should have the above email (or it’s School Manager equivalent).
In the meantime, until terms are accepted:
Devices assigned to a Mobile Device Management (MDM) server in Apple School Manager or Apple Business Manager won’t be affected. If you erase all content and settings on a device, the device will still be assigned to the same MDM server, and the same settings will be applied during setup.https://support.apple.com/en-gb/HT203063
Hot on the heels of macOS Monterey 12.2, Apple have publicly released the macOS Monterey 12.3 Beta Release Notes.
Despite this being a point release, there are a few breaking changes.
The kernels for both the Dropbox Desktop Application and Microsoft OneDrive are called out as deprecated in the release notes, and as such both have updates and/or changes coming to overcome this change.
However, the more impactful change is the removal of Python 2 (/usr/bin/python).
This has a number of ramifications, and is really a very large change to drop in a point release.
See below for more details on this, and how it will likely affect every Mac Admin.
Hopefully, all 229 posts from the past eleven years and two months have all been sorted.
All the code examples have been moved to gists from repos, and they will now show inline natively.
There was also still some http:// items from way back when this blog was just http://, which have been moved to https.
And, there was some images missing.. for $reasons.
I’ve also rejigged some backend stuff and removed some older plugins.
So, a fair bit or maintenance over the past 11 days. Let me know if any issues encountered.
Lastly, once more, thanks to @SudarMuthu for the WP Github Gist plugin which served this blog so well.
A few folks have noticed that the code examples have disappeared from my posts, well.. I was using a plugin called WP Github Gist to display the code as this blog has been around since before WordPress added native support for Gists.
However, this plugin no longer works.
But, don’t panic!! Things will come back, I just need to manually update the 229 posts here (over 11 years worth), to use Gists.
One of this things I most liked about WP Github Gist and will miss, was the fact that I could link to lines within a file within a GitHub repo and has them displayed. Instead of creating a gist per post (as an example, this file was used across a number of posts).
So, there is some work for me to do.
If you’re looking at a post, and are missing the content, please message me on Slack or Twitter.
No SLA mind, but I’ll look to update the posts requested over the older ones.
And lastly, thanks to @SudarMuthu for the WP Github Gist plugin which served this blog so well.
During your testing of macOS Monterey (betas or today after it’s release), you might receive a prompt like that shown above.
Well, does this mean that the “JamfManagementService” needs an update? Nope! and, to be clear, this is something you’ll likely see even if you don’t use Jamf.
Below is some information on this message, what triggers it, and how to start to uncover what on your macOS devices are triggering it.
As forewarned by Apple, Richard Purves and recently one of my dataJAR colleagues Richard Mallion, Apple is making a change to APNs on March 31, 2021.
As detailed within the dataJAR blog post, this change is between MDM servers and Apple and not managed devices.
Since Jamf Pro 10.23.0, there has been a toggle to enable this change to HTTP/2 for APNs communication.
However with Jamf Pro 10.28.0 release earlier this week, Jamf Pro will default to HTTP/2 and if you’re self hosting Jamf Pro this release will flip over the APNs communication to use HTTP/2.
If you’re Jamf Cloud, then this change has already been made for you.
So, this short post is just to bring attention to this change for those that need it.
And if you’d like to know more, for more info see the aforementioned blog post on the dataJAR blog.
With the recent release of iMovie 10.2.3, an additional surprise item is installed, a provisioning profile.
See below for more information on this provisioning profile, and impact.
With Apple recently releasing macOS 11.0.1, many Mac Admins over at the MacAdmins.org Slack started to see password prompts like the above.
Some digging has revealed that this password prompt is shown when the softwareupdate binary is called, and only on Apple Silicon devices.
Calling the softwareupdate binary is something which we Mac Admins have done for years, and it’s likely folks have workflows in place calling the softwareupdate binary which is then triggering this prompt.
So, what’s the fix? Short term, don’t call the softwareupdate binary on Apple Silicon devices and raise this issue with Apple.
Longer term? Unsure. There is still documentation around Apple Silicon devices to be posted by Apple, and until we have documentation we can but guess.
In starting to write a blog post on how to block and delay the latest macOS release, I realised that the subject of delaying updates via Managed Software Updates was probably worthy of its own post.
This its that post, see below the break for details.