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.
@totalyscrewedup This is not a Jamf issue, but a Apple issue. Jamf opened the case with Apple.
Agree it’s an Apple issue, Jamf has sent the APNS command to Apple
I'm seeing this with Pages and Numbers right now. Weirdly enough, Microsoft Word worked fine yesterday. Anyone get a response from Apple yet?
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!
VPP redownload call timed out <MDMClientError:72>
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.
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
- 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.
- Walk away - Wait
Now it works again with MacOS Mojave. Please try it again
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."
@Dylan_YYC Yep seems to be the Automated response everyone else is getting. The must be getting tired of hearing about it as we are at seeing it.
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.
Ive tried that too. Its just a matter of the stars lining up or something to get apps to install.
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.
@kerickson Same here, putting in a ticket to add me to that PI now as well.
Thanks Guys.
@benducklow Thanks yup I'll be putting in a ticket for this PI now as well @JarvisUno
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.
Here's what's happening in my environment...
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.
Hello @mjames ,
Can you please remove the "resolved" post as this is being experienced still by several people.
Nope, this is still an issue, I'm on 10.15.0.
We are experiencing the same exact issue with version 10.16.0
Seeing this issue too. I have tried all the things mentioned here.
