- Jamf Nation Community
- Products
- Jamf Pro
- Prestage Enforcing Latest macOS
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Prestage Enforcing Latest macOS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
I have a MacBook Pro (14-inch, M2 Pro, 2023) in our test environment on macOS 14.4. When i set the prestage to enforce the latest macOS based on device eligibility i get an error:
System Update could not be installed, even though the machine should force it up to 15.2. Has anyone else seen this?
10 REPLIES 10
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
@tkimpton Some versions of macOS 14 don't respond properly to the minimum OS requirement, and I _think_ it wasn't reliable until 14.5 and later.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
We are seeing this on pretty much every new deploy in Central America. North America seems to be ok. We had to turn it off
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi @tkimpton, have your tried to specify a version instead of latest macOS based on device eligibility.
Let's say 15.2 instead of let it choose a version for you.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
We have tried both. Our issue seems to be region specific.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Try with a newer OS. I did not see this actually performing well in my enviornment until enrolling devices with macOS 15, and now it works without issue.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
The problem is, we sometimes drop ship from our vendor (like CDW) and can't guaranty OS version. Having hiccups with this makes simplified deployments... difficult.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
we have seen this issue due to network issues during the Enrollment, Restarting the Machine and connecting with know good network resolves this issue mostly.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
I tested it many times, and 14.6.1 works. Jamf needs to change the minimum version on their end from 14.4 to 14.6.1. Anything lower than 14.6.1 should be skipped.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
from my jamf case "it appears that this issue is related to a recently opened Product Issue (PI125574). Based on our findings, this behavior seems to stem from a third-party Apple issue, as it occurs before the device enrolls into Jamf Pro." i have been advised to set it to latest minor. In my view if jamf change the minimum to 14.6.1 they can see it works.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Its a known issue. We had the same issue and ended up changing to Latest Minor version which works.
