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.
I'm also seeing this issue with 10.14.6 and 10.15. I have an open ticket with Jamf as well and they have acknowledged this this is an issue. They recommended clearing the failed command and trying it again, but this hasn't worked for me. I also tried running a recon and reuploaded the VPP token with no luck.
Jamf support pointed me to this, https://support.apple.com/en-us/HT201999 and to review my firewall settings. If the issue were firewall settings I would expect 100% failure. However that is not the case for us. Our work around currently when it fails to download VPP apps, which is about 75% failure for new installs, is to clear the failed commands and immediately do sudo Jamf recon on the machine in question. That works about half the time the first time, try and try again till it does work. Sometimes I just leave it sitting and the apps in question will just show up after a hour or so.
So I have randomly had this "vpp redownload call timed out <mdmclienterror:72>" happening to several people. It fails under the user account Self Service. If I login as my admin account, Self Service still fails. So it's not a user / user preference issue.
I deleted the folder /Users/Shared/adi/ which was empty and that magically fixed it. After the first app was installed there is now a new empty folder named /Users/Shared/SC Info/
Hope this helps someone.
New day, new issue.
Deleting the folder /Users/Shared/adi/ did not work this time. No app store installs were working for the standard account end user.
The error in the JSS was "vpp redownload call timed out" and not "vpp redownload call timed out <mdmclienterror:72>"
I logged in as an admin user on the Mac and no user in Self Service and the first Mac App Store app worked.
Then I was able to login as the standard account end user and continue installing the rest of their Mac App Store apps.
I restored their ~/Library/ folder from Crashplan so I suspect it is something in there this time.
Same issue (VPP redownload call timed out <MDMClientError:72>), running 'sudo jamf recon' isn't doing much, submitted the case to Jamf.
They should really concentrate on resolving all open cases before worrying about features and other gimmicks. Get it to be a solid platform, working reliably and have the features that are already there working first before adding more. The 'Download and Install updates' command hasn't worked in years, for just one example from trillion of open cases. Or how about getting Jamf remote to work as designed.
This thing is wonkey, after trying everything on here several times doing @jbosma method worked after x5 times of trying I think it comes down to timing:
sudo jamf recon.
After doing this several times it eventually went through. But without question still an issue.
same issues here with most clients on the latest version of 10.14 and open ticket with JAMF and Apple.
I have tried a bunch of the solutions above but the semi consistent fix is what JarvisUno stated
Still seeing this on 10.14.6 and 10.15. Currently running JSS 10.15.1
I talked with a JAMF support specialist yesterday and he said: "If we've verified this is not a network related issue, or the Volume Purchasing token is not assigned to another MDM Server, I would encourage you to open a ticket with AppleCare Enterprise Support (ACES) and reference the Apple Radar #100893229861."
So here is another suggestion you can try, after doing my previous studies for like x20 times and noticing I was not going any where I did the following:
sudo jamf reconon the machine in question.
And the App I been testing with FINALLY installed through self service.
@kerickson Someone correct me if I am wrong, but I believe there is a PI for this 'update' ability...
PI-006120 - Jamf Pro fails to update Mac App Store apps that are made available in Self Service and configured to automatically update.
The notes I have on this - The button simply says 'Open" instead of "Update" within Self Service Mac App Store App assignement policy. We are forced to create an 'uninstall' Policy and have Users' run this before re-running the install to get the updated version.