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.
Have been having a nightmare with this over the past month – new Jamf Pro user here – I've just discovered this thread, so at least I know I'm not alone :(
If you are using Cortex 7.2.1 or later and you are not on Big Sur yet - you will need to have your security team disable the Cortex networking filter. This is what fixed it for us,
Posted: 1/12/2021 at 9:21 AM CST by Knoxx
If you are using Cortex 7.2.1 or later and you are not on Big Sur yet - you will need to have your security team disable the Cortex networking filter. This is what fixed it for us,
@Knoxx We got a support exception to disable the filter which kind of worked for me when I tested on Catalina.
When I forced updates for some VPP apps there were no time out errors after running, I could hear my device spinning into gear like it was installing software, I loaded the apps and could see the newer version numbers. However, my app store was still telling me I needed to update and still is to this day a few weeks later!
@ajassi We see that as well with apps such as BBEdit and Microsoft ToDo. We are deploying those through VPP, somehow they are being updated to the current version but that doesn't seem to make it to what the AppStore thinks, and it will continue to claim a update is needed even though the most current version is installed. The only real way I have found to make this "update" go away is to remove the app and let VPP re-deploy it. The App Store will be happy until the next update.
We're seeing a new type of error, when Jamf is trying to 'Force App Updates' for installed VPP apps (Jamf Pro 10.26):
Install App - <app name> "Bag Load Failed"
Apps will just not update on macOS Big Sur (Intel) machines. When we don't see that error, Jamf will show the mdm command as completed and successful when in fact the app was never updated. It even shows as completed with the new version number in Self Service.
After dozens of forced app update attempts, we might see 1 in 10 app updates work.
I have no problems installing the VPP app via Self Service. So the workaround at the moment, is to delete the app that isn't updating and reinstall it from Self Service.
@Knoxx We've just recently started using Cortex XDR and I can't seem to find that setting to disable network filtering. Do you happen to know where that's located? Thanks so much!
@mlee001_hcs - This was done by policy our IT Security team on their side.. and it looks like its fixed with Big Sur and Cortex Ver 7.2.2 You can try with this line: sudo /Library/Application Support/PaloAltoNetworks/Traps/bin/cytool runtime stop networkextension
@Knoxx Thanks so much for the quick reply. Stopping the network extension did seem to work. Unfortunately the mac it's running on can't go to Big Sur. I'll need to dig around in Cortex to see what I can find about maybe disabling that on anything below Big Sur. Again, thanks!
Customer of mine just got hit with this. Macbook Pro running 10.15.7. VPP was working fine last week with no apparent changes made to anything that could interfere (network filters etc). Incredibly annoying as I have nothing I can tell the customer to do to try and fix the problem.
Retracting this post. After an update to 10.27 last night, the issue is not fixed at all.
~Hey folks, I just called Jamf support about this (15mar21) - the support person I spoke with said that their internal ticketing system shows "fixed in Jamf 10.27". She also confirmed that there's no direct mention of this in the 10.27 release notes.
We'll update and test as soon as we can. The Jamf support engineer mentioned (twice) "Make sure to update to MySQL 5.7.8 before udpating to 10.27"~
Yes, "<MDMClientError: 72>" was a symptom of PI-007435 which has been marked as resolved in Jamf Pro 10.27.0. However, this is has only been resolved with initial installations of applications. We unfortunately may still encounter "<MDMClientError: 72>" when updating macOS applications through Volume Purchasing.
This issue (Product Issue-007435 ) is supposed to be resolved in Jamf Pro 10.27. However, we are still seeing the problem with various Apple MAS/VPP apps such as macOS Big Sur installer, Keynote, etc.
Sigh. Big Sur 11.2.3, JAMF 10.28.0-t1615386406. Result whether automatic install or Self Service "Bag Load Failed". Pages, Numbers, iMovie etc. So now I will copy those apps off of a machine which has them and put them on the problematic device(s). This is great.
My Apple rep told me that he confirmed that <mdmclienterror:72> is resolved in macOS Big Sur 11.3 beta 4.
Unfortunately, I need it to work now, in Catalina because I want to leverage Self Service & VPP to upgrade Catalina Macs to Big Sur. Too little too late, Apple (assuming it's actually fixed).
