App Installers automatic updates/installs not working but Self Service App Installers do

[jamiesmithJAX]

I am seeing an issue where suddenly my App Installers that I have setup for automatic updates are no longer functioning, but Self Service app installs work fine.  Seems to have started when 11.10 was released.  I have tried recreating policies from scratch but issues remain the same.

1. No App Installers set to automatic function, everything stuck in progress but no signs the update command is ever sent.
2. When I look at the deployment status, none of the scoped machines are visible, but if I look at a Self Service policy, they are there.

Is anyone seeing anything like this and any idea how to resolve it?  I do have a case open with JAMF but so far we haven't got it figured out.

[scottb]

I had a couple that were setup early on that did that.  I deleted them and started again and that fixed it.
May not be your solution, but worth a shot...

If you have a bunch and they're all failing, hopefully Jamf can help you.

[jamiesmithJAX]

Thanks, they were working great and suddenly just stopped working.  I've tried recreating but no luck.  Works totally fine in my dev instance.  Hopefully JAMF has the answer

[jamiesmithJAX]

Seems to have started with 11.10 but I have since updated to the latest and it still exists.  11.10 did introduce some change to App Installer workflows, but for me Self Service workflows are working fine, it's the auto deployments that fail.

[scottb]

Wow, that's a bummer..did it start after a recent update to Jamf?

[Shyamsundar]

Currently using JAMF 10.1, I have not encountered any issues. Some of the items you can check are the MDM Profile expiry date. Additionally, you can access the Management history tab to verify the presence of any installed or failed commands. Furthermore, ensure that you can deploy and distribute profiles. Lastly, run the Mac evaluation utility to confirm that the device is accessible to all Apple servers.

[jamiesmithJAX · Accepted solution]

This was resolved for me.  PI121695 addressed an issue relating to status value logging not being set correctly in the database.  They had to take my cloud down for about 30 min to apply a hot fix and after that I was good to go.  I assume it'll be patched in a future release.

[bfrench]

Looks like they have addressed PI121695 in the maintenance update released today 11.10.2.

[CLVX]

Thanks a lot! this article was very useful a coulple weeks ago, i faced same error, following suggestion, i submitted a ticket, and Jamf Team did the same workaround :)