a week ago
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?
a week ago
@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.
a week ago
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
a week ago
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.
a week ago
We have tried both. Our issue seems to be region specific.
a week ago
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.
a week ago
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.
a week ago
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.
a week ago
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.
a week ago
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.
a week ago
Its a known issue. We had the same issue and ended up changing to Latest Minor version which works.
3 hours ago - last edited 3 hours ago
Agreeing with everyone's bad experiences.
Look into doing this with compliance instead, giving people a 24 hour grace period before enforcing compliance for system version, or even prevent access until the device has been updated. Updating doesn't require the device to be in compliance yet.
Compliance means you don't have to control every little detail - you just require the details to be correct before granting access. :)