macOS Device-based VPP App Installations Failing and Opening App page on AppStore

[tomgideon2003]

Since updating from 9.98 to 10.1.1, we have been noticing on some newly enrolled computers this issue: In Self Service, the available VPP assigned AppStore apps all fail. After you click Install, it spins at Installing for 15 seconds or so and then pops up a failed to install error. It then opens that app page in the AppStore.

I have tried renewing the VPP service token and I checked the license counts. Everything looks good. I have tried paid apps versus free apps and both fail. I tried using a hotspot instead of our work network and it still failed. This seems to happen on 30% or so of newly enrolled computers since the upgrade of the JSS. The other 70% work just fine.

Any help is appreciated! Thanks!

[tomgideon2003 · Accepted solution]

We ended up having some records that were created with APN token problems. So we had to remove these records and re-enroll those computers. So far everything is back to working. A couple computers never would work after re-enrolling so those got erased and set back up. Here are the MySQL commands from JAMF Support:

1. We will have to log into MySQL
2. Once logged in we will have to run this command: Use jamfsoftware;
3. When we are in the database we will run the select statement below:

select distinct computer_id from computer_user_pushtokens where (user_short_name="" or apn_token="" or push_magic="")G

This will list out the computers that we need to hand touch and re-enroll. We will have to use the ID numbers to find them in the JSS. When we have those written down somewhere we will do the steps below.

a. STOP TOMCAT b. BACKUP DATABASE c. Commands MUST be done in this order. delete from computer_user_pushtokens where (user_short_name="" or apn_token="" or push_magic="");

delete from mobile_device_management_commands where apns_result_status="" and device_object_id=12 and device_id NOT IN (select computer_user_pushtoken_id from computer_user_pushtokens);

d. START TOMCAT

This will delete those records out of the database and when this is ran then we will have to re-enroll those computers.

Hope this helps others if you run into this type of issue!