Posted on 11-11-2021 09:18 AM
I am having a handful of systems with Configuration Profiles stuck in pending state. Does anyone know of a fix for this?
These systems are all Automatic Device Enrolled, they are checking regularly to jamf. I have tried having them reboot, sending blank push from management commands.
These commands have been pending for months.
Posted on 11-12-2021 02:31 AM
@dthompson1 you can troubleshoot MDM from client side with log command.
log stream --info --predicate 'processImagePath contains "mdmclient" OR processImagePath contains "storedownloadd"'
Immediately after clicking on "Send Blank Push" the client should return a log.
Posted on 11-12-2021 05:10 AM
Posted on 01-14-2022 09:55 AM
Did you find a solution for this? I am also running into the same issue with a few of my devices.
Posted on 02-03-2022 02:36 PM
We are experiencing the same issue with around 20 laptops in our environment across 4 different profiles. Anyone found any workarounds?
Posted on 02-03-2022 06:11 PM
Is it pending only on some devices or all of your devices?
Posted on 02-04-2022 05:16 AM
Posted on 02-04-2022 08:53 AM
yeah, I had that issue too. its possible one of your other config profiles is causing the issue? In my case, removing all profiles and running the profiles renew command did the trick.
Posted on 02-04-2022 08:56 AM
Is the profiles renew command sudo jamf policy?
Posted on 02-04-2022 09:17 AM
No. Once you remove all profiles, it will also remove the MDM profile. You will basically need to re-enroll the computer. This article goes into more details about it -- https://docs.jamf.com/jamf-now/documentation/Re-enrolling_a_Computer_Using_Automated_Device_Enrollme...
Please make sure you read the requirements carefully before removing the profiles.
Posted on 02-04-2022 09:32 AM
Posted on 02-04-2022 10:37 AM
My problem ended up being with the keychain. I deleted too many keychains troubleshooting another issue. I did sudo jamf removeFramework command and reenrolled. My Profiles are coming down now. Not ADE on this test system.
Posted on 08-11-2022 11:46 AM
I was able to resolve the issue on one of the effected computers by doing the sudo jamf removeFramework and then using a User-Initiated Enrollment to re-deploy the MDM framework. It is a less than Ideal solution for a larger group of users, but was helpful in getting the device in front of me resolution.
Posted on 02-04-2022 08:41 AM
I am having this problem too.
Posted on 07-26-2022 02:44 PM
Posted on 11-03-2022 12:43 PM
Having the same issue on about 40 systems. All are checking in fine and most have users logged in. I have tried Jamf recon, launchctl kickstart -k system/com.apple.softwareupdated, renew MDM profile. No of these worked. Rather not have to re-enroll these systems, also sudo profiles renew -type enrollment forces user interaction which is also not ideal. Anyone find why this happens? Seems to be ongoing and happening randomly.
Posted on 11-14-2022 11:27 AM
There is a different way to re-enroll using the API that requires 0 interaction.
I've used that to fix a few computers that were not checking-in. The only requirement is the devices still need to be capable of getting MDM commands, which do get send the same way config profiles do I believe, but still worth trying. Definitely fixed a few for me.
Posted on 11-14-2022 11:40 AM
Thanks. Yeah the binary on these systems is fine, they are checking in and doing inventory updates. They are not getting MDM commands that is the issue.
Posted on 11-11-2022 02:41 PM
Seeing the same thing here, over 75 devices. Checking in, user logged in, MDM Profile Healthy and approved. Varying OS's.
Seems to just be more recent profiles that are stuck in pending, but these same profiles have gone out to hundreds of other devices just fine.
Surely someone has a better solution than re-enroll?
Posted on 11-16-2022 06:50 AM
I'm working with Jamf on this, will post if we find a solution
Posted on 11-16-2022 07:10 AM
Posted on 02-21-2023 08:38 AM
We have this issue with about 200\1000 devices. Policy and checking are working but configuration profiles are showing as Pending.