Skip to main content

we have a few older Intel iMacs that are applying policies as normal, but configuration profiles changes and deletions seem to be stuck in pending.


They're all checking in, and policies work without issue. This lab is all Intel iMacs running MacOS 14.7.1, but 75% works without any issues. They all report as being successfully enrolled in Jamf, and they where all automatically enrolled via ASM.


I'm not sure what to do to troubleshoot, as these profiles work fine with most of the Intel iMacs, and our newer fleet of Apple Silicon computers.

Sounds like the Jamf binary is working fine, but the MDM framework is not which is strange, the issues are normally the other way around.


 



  • What does the uptime look like on these devices?

  • Are the devices on the same network segment, and are any devices on that network segment working?

Try sudo jamf manage in terminal?

Sounds like the Jamf binary is working fine, but the MDM framework is not which is strange, the issues are normally the other way around.


 



  • What does the uptime look like on these devices?

  • Are the devices on the same network segment, and are any devices on that network segment working?


uptime ranges from a couple of hours to a couple of days. they're all on the same network segment.

Try sudo jamf manage in terminal?


sudo jamf manage results in:


Getting management framework from the JSS...
Enforcing management framework...
Checking availability of https://XXX.jamfcloud.com/...
The JSS is available.
Enforcing scheduled tasks...
Updating daemon settings
Checking availability of https://XXX.jamfcloud.com/...
The JSS is available.

 


 sudo profiles renew -type enrollment results in Error: Renewing DEP enrollment failed: (null) (NSCocoaErrorDomain:4099)


 


sudo /usr/local/jamf/bin/jamf enroll -prompt results in


The device certificate was created successfully.
This computer was successfully enrolled to the JSS with the following device certificate: "D8957EFC-DD28-5822-9596-D3DBD59A0C87"

and what follows that looks like the typical response from a recon command.

This could occur if the APNS certificate is changed and the APNS topic differs. You may simply access the MDM profile on two different Macs, one on which everything works properly and the other on which MDM commands do not work. If the APNS certificate is different, there is a problem.

Terms & ConditionsCookie settings