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.
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.
Nope and just did a fresh install of my Catalina TESTER today with the Supplemental Update installed as well and still getting the the 72 message from hell!
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:
Go under the management tab on the device in question, cancel all the failed <MDMClientError:72> command and then send a blank push.
On the machine in question quickly run a :sudo jamf recon.
After doing this several times it eventually went through. But without question still an issue.
Just updated to JAMF Pro 10.16.0 and Java openJDK 11.0.5. I was hoping the combination would solve the misconfigured TLS1.3 settings from Apple, however we are still seeing VPP errors however this did solve some of our DEP issues.
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:
Updated my VPP token (again)
Cleared <MDMClientError:72> then a blank pushed.
Ran a: sudo jamf recon on the machine in question.
And the App I been testing with FINALLY installed through self service.
The strange thing about this, at least in our environment, any VPP app that is pushed during enrollment works with no issues. We have Keynote set to install on all computers as a push. I can enroll a computer in Jamf (DEP or using enrollment URL) and Keynote shows up on the device.
Has anyone seen that once the apps do install that they won't update? I get notifications to update via the Mac App store, but unable to do so. I have tried the force update button via Jamf.
@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.
Have also been having this issue for a while now, have tried many things to remedy but the issue is very intermittent where VPP installs fail more than they succeed.
It seems like the first Mac of the day that I set up receives its Scoped VPP apps without issue - any Mac after that gets the error 72. I have absolutely no issue pushing Scoped VPP apps to iOS devices.
After renewing the VPP token, it was working for about two weeks, but today it broke again with the same error 72. This is for Microsoft Excel, Powerpoint, Word.
