I am seeing a lot of our systems having the "vpp redownload call timed out <mdmclienterror:72>" error when cliets try to install VPP apps via Self Service on MacOS (most clients are 10.14.2).
I have tried clearing the failed commands, reconning, re-enrolling etc with no luck.
I am hesitant to revoke all apps as I have seen suggested because I am concerned about the number of people who will experience iTunes notifications about apps not being assigned (the staff at this school are fragile...).
Any advice would be appreciated.
Solved! Go to Solution.
@mjames @whitebeer The issue with storedownloadd crashing during MAS installs is fixed in 10.14.4 Beta 4 (18E205e). This is RADAR 47685116. Let me know if you still see problems after the update. For clarity, typical symptoms of this bug:
- Larger MAS apps like Xcode and Office fail to install and leave behind an .appdownload stub
- Needing to run multiple jamf recon commands to coerce apps to install
- MDMClientError:72 failed command seen in JSS
I've updated https://macadmins.software/mas with the latest info. The largest outstanding issue that I'm still tracking is the inability to update MAS apps through MDM when the user has the app perpetually open.
Has anyone build a script to do the following?
1. Cancel failed MDM commands.
2. Send blank push
3. Sudo jamf recon
Would be nice to have a script that could be built into a policy.
On top of Microsoft products, I'm getting the error for apps like Numbers and Pages, it takes multiple attempts to get it installed until it randomly works. Users are opening tickets for failed installs and we have to tell them to keep trying. Not ideal.
It's problem I encountered over the last few weeks here too. This happens for apps set to install silently or via Self Service. I've opened tickets with JAMF & Apple. It's an Apple issue: I asked an SE about it at a recent event & was told it's being worked on, but there's no timeline for a fix. What's the most maddening is that it's inconsistent-some of the above fixes are working for some folks, but not everyone.
Update #2 11/1/2019: Appears it has gotten worse for us since my last post. When in a time crunch we are copying the Apple Apps to flash drives (That were pulled down from Jamf to a machine not experiencing the VPP issue) and putting them in Applications on the machines that we can not "jiggle the handle" and get them to pull down via self service using all the tricks above. We have also put in an Applecare ticket and referenced previous Apple & Jamf AC tickets listed here. Our AC ticket # is 100941078865. Also referenced this URL in the ticket and cc'd our Apple SE.
Been following this thread almost since it's inception, so thought I'd chime in and say that in my environment we've seen this issue progress from "intermittent" to "consistent" to "damn near all of the time." Like many of you, we've observed this to be exclusive to macOS devices running 10.13.x - 10.15.x. Our iOS, iPad OS and tvOS devices are able to download VPP apps via Self Service without issue, as are the few devices we still have running macOS 10.12. We've worked through every suggested solution in this thread with no success. In fact, it seems that things are only getting worse.
It's really hard to sell folks on Self Service as a viable solution when VPP apps (which make up most of our offerings) are almost certainly going to fail...
If anyone is still having issues with this, I think I found a workaround.
Follow what @samherren posted, but in addition, make sure to keep the Mac App Store open at all times.
This seemed to ease the process with all machines I tested after discovering this trick.
Cannot find any comment of @Samherren in this thread, where to find it?
What we discovered in combination with JCV, that if we have not yet logged into JCV on the client if fails.
cancel all failed and login JCV and app starts downloading.
JCV has nothing to do with authentication on app store or whatever, but on of the guy of the support team at my company discovered this.
There are several thread about this issue with possible workarounds.
disconnect from network and cancel all failed seems to be a workaround for more then 50% of the issues
Update #3 11/04/2019 Apple has replied to my AC ticket: "Your issue matches a behavior we are currently investigating". He encouraged everyone having this issue to please put in a ticket and also give quantities of devices effected in your environment so they they can prioritize for enterprise customers. I also shared this threads URL in the ticket and the Jamf ticket #'s below (as mentioned earlier in this thread):
• Jamf AppleCare ticket (100893229861)
• Jamf Product Issue (PI-007435)
We have flash drives with GarageBand, Pages, Keynote & Numbers we can quickly deploy to students/teachers that need if initially it fails in Self Service (These were pulled from a MacBook that had the apps deployed properly via Self Service). Luckily a lot of students had already downloaded these before the issue hit us harder. Still a pain and a good number effected that did not initially download at the first of the school year (or students that just now are taking classes that require GarageBand) or with freshly erased/provisioned MacBooks. We had a method that seemed to work for us and got us by which was clearing the VPP error logs and running a recon multiple times. This work around doesn't appear to work as well currently as it did in mid October.
Seriously though, what's taking so long to find and fix this issue - an issue that's extremely high-impact to a multitude of organizations? I can't count on two hands how many tickets i've raised for this issue - tickets dating back to March 2019 - and I've been met with absolutely no response from Apple.