Mac Enrollment Timeout

Existing devices in JAMF (e.g.: reenroll)?  Or are these brand new devices without a JAMF record?

If the former, purge the old record and try it again. 

The devices were enrolled previously. However I already tried deleting the old records before reenrolling. Without success.

What macOS version are these computers running? Jamf Pro may not allow you to enroll computers with unsupported operating systems?

See the release notes for supported versions.

https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/System_Requirements.html

I tried it with macOS 15 and 26. Both had the same error.

​@Andixon have you deleted the partitions or volume and created a new one? I can’t explain why this would have an affect but starting from scratch with a fresh OS may work. 

Since only a few specific MacBooks are affected while others enroll fine, this is likely a device-specific state issue.

Recommended fix: Boot into Recovery Mode → Erase the drive → Reinstall macOS.

Already tried both. I always erase the drive as completely as possible.

Tried different internet connections?  What’s the system clock showing on the system?  Were these turned off/shelved for a long period of time?

Different internet connections make no difference.

The time that is showing it not correct. But that should not be the issue. The time is never correct at this point. It sets itself to the correct time after the enrollment. 
No, the one I am testing with was enrolled just before.

The clock’s time may actually be very important. Most modern systems require clocks be within a range of about plus/minus five minutes from the current local time. This is a security feature to thwart using old certificates that may have been revoked or expired.

If a Unix-based computer sits for so long that its battery depletes, the internal clock will reset to January 1, 1970 (Unix epoch time). A manual time sync is often the only way to restart time sync when it’s that far off.

You might want to review Apple’s document Check the condition of your Mac laptop’s battery.

Thanks Bill.  See, I know what I’m talking about sometimes.  And yea, the enrollment cert has to be within a valid window for it to actually enroll and not timeout.

Okay, but can I change the clock before enrollment? Because usually that is done via the sync with our NTP server, but that step follows after the enrollment and as I said usually the clock being wrong is no issue.

Are you on company network for Ethernet or Wifi when enrolling?

When you see this, did you happen try connecting to a personal hotspot? 

Usually I do it via Ethernet. Only the test via hotspot was Wifi.

The reason I ask is because we ran into something similar. We had to look at our 802.1x setup, and WSA configurations as well.

Some gremlins were blocking some URLs that needed to be whitelisted across our security applicances. 

https://support.apple.com/en-us/101555

For the sake of clarity, keep in mind that if it’s 3:01PM EST where you are, and the laptop says 12:01, the time isn’t wrong. The time is correct, just in a different time zone. It will still succeed in connecting to HTTPS sites, enrollment, etc. If the minutes are completely off then that is a time issue.