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.
I have received a message from Jamf Support today with the following statement: The issue that you were originally experiencing, so the PI-007435 is partially resolved by Apple from what we know. By partially I mean that new installations of applications should work without any issues only updates of Applications may fail. The updates, unfortunately, may still fail with those errors. Sometimes it might be caused by the network connection also. Can anyone confirm this?
Yes, I can confirm that. We are still struggling with Self Service installed VPP apps and having them update automatically.
We have had a case open with Jamf for several months now. Their last workaround was to run a particular script which would attempt to prompt the app to update. This, however, would not work due to a separate issue when trying to call the install policy from Self Service. Instead of running the policy as it should, it simply opens Self Service to the description of the policy.
They are apparently still working on a solution. That was a few weeks ago.
Would you mind confirming exactly what issues it resolved? eg: - Self Service app installs - Updates to Self Service installed apps (for device assigned content that does not require the user's Apple ID to have that in their purchase history) - Auto installed apps - Updates to auto installed apps
Never had this problem until Friday when Big Sur was released. I have a policy to upgrade to Catalina through the App Store app, rather than build an OS package. Since Friday, its giving a timeout error. However, if I copy the link from the policy and paste in a web browser, it opens the App Store and directs to the Catalina installer.
Around the time Big Sur launched we started having this issue again. Big Sur did happen at the same time our Cisco Amp updated to 1.14.0. This added new Approving Mac Connector macOS Extensions and Approving Full Disk Access profiles using Jamf.
The most interesting piece has been the Cisco AMP WebContentFilter that requires approval - We have isolated that without the Profile or Extension installed/ allowed we are able to install Mac App Store Apps on 10.14 and 10.15 without issue. With it installed instant Error 72.
All the same Cisco AMP profiles installed and Big Sur has zero issues on our managed Macs.
I was successfully able to update to Big Sur via VPP earlier this month - now this week we are getting the lovely VPP redownload call timed out <MDMClientError:72> I honestly think this is a throttling issue on Apple's side.
Does anybody else here use Cortex XDR? This has been an ongoing problem for us and today I disabled the software using the cytool
command and found the updates were completing successfully when I forced them from the Jamf Server. It worked every single time the software was disabled, and failed every single time the software was enabled.
I'm yet to come up with a solution with the software enabled.
Hey all, Jamf & Apple say this bug is resolved in Big Sur 11.0.1, We can still see this error on a lot of 10.15.7 Catalina devices. Unfortunately I cannot confirm this bug is resolved in Big Sur, since we have not upgraded all of our devices yet.
Hey all, Jamf & Apple say this bug is resolved in Big Sur 11.0.1, We can still see this error on a lot of 10.15.7 Catalina devices. Unfortunately I cannot confirm this bug is resolved in Big Sur, since we have not upgraded all of our devices yet.
@hhorn Can confirm that this is still an issue on 11.0.0 and 11.0.1. Jamf Support has told me that updating to 11.0 is supposed to fix the issue, but this is not the case. I am still seeing the same VPP error codes as 10.14 and 10.15.
This is really annoying. I have seen issues like this since I started using VPP. I had a user with this same problem today. When I got a free moment, I checked the pending installs in the Management tab. I saw this error: VPP redownload call timed out <MDMClientError:72> So I fired up a test Mac, and I was able to successfully download the app the user was trying to install. Typically, I see VPP apps install without issues, but this only seems to happen when I assure a user that yes, they can download that app easily through Self Service. There's no need to use their own Apple ID to get an app. After I wipe the egg off my face, the app finally installs later without me doing anything at all to correct it 😳
