Configuration profile in "Pending" status?

I have. What I did to get the commands out of "Pending" was to send a push notification to check in. Inventory-><Computer Details>->Management History and click on the little circle arrow in the upper right side of the management commands window.

I am not really sure what caused it, but when I did that things started to happen again.

I'm gonna bring this one back.....our issues don't seem to have really gone away. Wether or not our configuration profile gets assigned is hit or miss. We can run our image once and 1 out of the two machines will get the profile. Both have all policies, but one has a profile stuck in pending status. If i delete all records from OD/AD and the JSS server, odds are that they will apply fine the first time. If we make a change and then try to reimage them sure enough the config profile for our wireless might apply, but it might not. Were banging out heads up against a wall here. got a deadline of next week to get a basic image ready, and its just not happening.

I've had the same experience with profiles pushed from the JSS, so I'm only using them for testing at this point. The only profiles I am using in production are installed locally using packages and postflight scripts. That works every time!

at least were not alone.....its very frustrating to see hit and miss application of profiles when we are still trying to get the basic image process hammered out.

Are these troublesome macs on different networks?

If you run ```
sudo jamf manage -verbose
``` (i think that's right), does all profiles show as downloading?

These macs are all on the same network. The JSS is on another subnet, but there haven't been any jss connection issues I've witnessed. I'll try your command in a second, thanks

sorry double post

Just another update. I took the two machines that we have been working with, that already have history in the JSS, as well as a "new to the jss" machine. Ran the same workflow on all 3. The two that were already in the JSS are pending for the 802.1x profile. The third machine received the 802.1x profile perfectly. Obviously we can't keep clearing out the JSS computer history/records, is there some trigger or command we are missing that would cause this sort of issue when reimaging machines?

Sam, did you run the above command I gave on the two failing macs?

What happens if you remove the policy remotely on the 3rd mac, do you receive the same issue?

Yes I did Ben, There was no reference to any configuration profile listed at all. For some reason they don't seem to be stuck in pending any longer, now we are dealing with the profile actually removing itself upon user login. We are trying to make a new profile now in lion server and setting security so it CANNOT be removed by the end user.

Yes I did Ben, There was no reference to any configuration profile listed at all. For some reason they don't seem to be stuck in pending any longer, now we are dealing with the profile actually removing itself upon user login. We are trying to make a new profile now in lion server and setting security so it CANNOT be removed by the end user.

Seeing this same issue on a newly imaged 10.8.2 + Casper 8.6 setup here. Forcing management via "sudo jamf manage -verbose" has no effect, still pending in status.

Forcing re-enrollment via jamf enroll nixes existing MDM profile config. "jamf manage" re-adds enrollment profile, but no additional policies.

Anyone found any other workarounds for this?

Following up on this, any way to just wipe/remove push notifications that linger in "pending" status? Casper is trying to remove a profile we had preinstalled on our image and it keep generating errors by trying remove a push profile with the same name:

Nov 2 17:07:33 us-mac-0276 mdmclient[1437]: [Daemon:0] Processing server request: RemoveProfile for: <Device>
Nov 2 17:07:35 us-mac-0276 mdmclient[1437]: [Daemon:0] Removing profile: Network BCWIFI (F78E827B-D159-40D7-8015-8B32C96637DB) for: <Device>
Nov 2 17:07:35 us-mac-0276 mdmclient[1437]: ** ERROR ** [Daemon:0] ### Errors while processing: RemoveProfile ###

We are seeing the same issue here.

Deleted the machine from the jss inventory, re-enrolled, removed binary re-enrolled, restart.
We have JSS 8.62 and 10.8.2.

Im rather frustrated and hairless.

Anyone still having this issue: reach out to your local JAMF Support team. We had one stubborn Mac whose pending push command persisted even after wiping out its inventory record and unenrolling/reenrolling it into our JSS. We reached out our local JAMF account team and they were able to walk us through a direct edit to the MySQL DB that removed the offending "pending command" once and for all. Individual configurations may vary so be sure to go over your specifics with your account team for best results.