We fixed this issue on ours with the same solution andhy.cauble used... we just installed the app through the regular app store (it just needed to show up on the ipad). Then we deleted it and it installed normally from the JSS.

+1 for @andy.cauble His process worked for us as well. Thanks.

andy.cauble's suggestion worked for me just now! +1

I fixed the same issue with solution andhy.cauble. Thanks a lot. CCA rules)

This thread is an older one with newer posts so I'm going to appropriately update it with what I've learned today.

I was facing the same issue with "app already scheduled for management" on a student device.

Background: all student devices enrolled with DEP using device-assignable VPP for app distribution. The App Store is permanently closed to our students. I have this issue occur, but it occurs very infrequently (about once a month on one or two devices randomly...we have a large fleet of 6000). I have previously found that very little seems to fix this issue. Occasionally a reset settings and an update of the iOS fixes things but nothing that I can turn to in a pinch.

Decided after it happened today and I had time to file a case with jamf on it. Here is a snippet of what they sent me:

1. Jamf sends an InstallApp command, device acknowledges the command. After this, there is no interaction with Jamf for the actual download/install. 2. The device reaches out to wherever it gets the app from (either vpp app store, public app store or caching server) and then installs what it is told 3. In these types of scenarios, there is usually something wrong with the app file that it downloaded (again, outside of Jamf) 4. This causes the install to fail. After the install failure, the iOS holds on to certain remnants of the app which are left in an "unmanaged" but "scheduled for management" state. This leaves little room for Jamf to do any corrective action since we can only do things for managed apps. 5. The cause is between the device itself and where is gets the app from. One thing you can try would be to download from the app store on the iPad itself. This could install the app correctly and then we can use Jamf after the fact to "make unmanaged app managed" in the app record.

I will be honest, they also sent further suggestions which I don't want to get into because I feel your Jamf rep should be involved if you try to perform them. That being said, I took this knowledge and performed the following...I temporarily lifted our App Store restriction and used a hidden Apple ID I maintain with all of our purchased apps on it, installed the app by hand on the device, deleted the app, made sure the App Store and iCloud were logged out and re-applied the purchase restriction.

I then reinstalled the app from Self Service and it completed on each of my afflicted devices.

In short, definitely not an end-user-facing fix, but I can easily train technicians to complete this fix. Hope this technique helps someone...if not contact your rep as they do have techniques that higher level engineers at Jamf can consider performing.