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.
Best answer by pbowden
@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.
@Dschurrat if you scroll up you'll find ticket numbers that we submitted and that Jamf submitted, would send those to Apple to so they can gauge impact (the more tickets the more attention it gets).
I have one: Bash: https://github.com/hhorn76/JAMF/blob/master/API%20Scripts/clearAllFailedComputerMDMCommands.sh PowerShell: https://github.com/hhorn76/JAMF/blob/master/PowerShell/JamfAPIClearFailedVppMdmCommands.ps1
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.
@hhorn can you go into detail on how to use those scripts?
Edit: figured it out… for others open terminal and use this line changing apiuser:password for the appropriate information, leaving the ` marks. paste the info into the strAuth in line 9
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...
I would urge anyone who hasn't opened a case with Apple to open one, and reference ticket 100893229861, which JAMF has open with them... the more reports, maybe the more pressure... (we can hope, right?!?)
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.
Note: 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.
Note2: 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
