in some Macs's Selfservice, the policy always executing, never finished.

chenhao2018
New Contributor

in some Macs's Selfservice, the policy always executing, never finished. There is no log output in jamf.log. what is the problem? Is there any one know that?

but when we use sudo jamf policy -id xx in the terminal. It works.

3 REPLIES 3

ferrispd
New Contributor III

Same issue here. Just opened a ticket. I'm not sure how many others are seeing this issue. It has just started happening to some of our devices after upgrading Jamf from 10.9 to 10.13.

Only solution so far has been to remove the framework and then enroll the device.

-Pat

hkabik
Valued Contributor

As above, remove framework and re-enroll has been our path forward when these pop up. Still on Jamf 10.12 though.

We've seen no rhyme or reason in what causes these. See maybe 1 or 2 a week. Very frustrating.

I do remember this occurring in a Jamf Pro Version a ways back and it was eventually resolved with an update. Hopefully that's the case here.

Musicmaker
Contributor

@ferrispd Any luck with that ticket you made then? I'm having the same problem here, but removing framework and re-enroll doesn't work.