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.
This has been such a saga that I’m tossing in the towel and going back to Packaging... In my 20 year career I can’t say over ever seen anything like this.
Can someone from Jamf give us a status update? Has Apple responded to your tickets for this issue? This is crippling our deployment process - we've fallen back to packaging apps in the interim.
Unfortunately, things are getting worse. We're now seeing an issue in 10.15.3 where it is no longer possible for VPP to update apps (Office or otherwise). Jamf Pro will send the InstallApplication MDM command, which will complete, but fail silently on the device side.
You'll see the following statements in the console on the client-side:
Process: storeassetd SoftwareMap: Found app at <CKSoftwareProduct: 0x7fcdc2706f30>: (com.microsoft.Word, 16.33, 462054704:834308480 VPP:YES md:0x7fcdc2494a30 /Applications/Microsoft Word.app) using SoftwareMap to upgrade to 16.34
VPPController: VPP Redownload purchase for <SSPurchase: 0x7fcdc251d1b0 - itemIdentifier=462054704, buyParams=productType=C&price=0&salableAdamId=462054704&pricingParameters=STDQ&pg=default&appExtVrsId=834663827, isUpdate=NO, isRedownload=YES, isVPP=YES, isDSIDLess=NO, managedUUID=(null),accountIdentifier=(null), purchaseType=0> completed with success=1 error=Error Domain=CKVPPErrorDomain Code=3 "The product is already installed" UserInfo={NSLocalizedDescription=The product is already installed} response=<SSPurchaseResponse: 0x7fcdc254a8b0>
Process: storedownloadd Download: Download <Download: 0x7fef2ac3e9b0>: com.microsoft.Word 16.34 (462054704) paused:0 failed:0 isInServerQueue:0 is known to be an update when metadata is set
DownloadManifest: removePurgeablePath: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/C/com.apple.appstore/462054704 sending status (Microsoft Word): 0.000000% (0.000000)
LegacyDownloadQueue: Could not add download
LegacyDownloadQueue: Will start any ready downloads anyways.
@Cayde-6 no probs - this is all super frustrating. I've traced through the MDM commands, and Jamf Pro is sending the correct signal - the bug is in the OS.
What apps are affected? What is working(app install, app update, nothing? What OS version(10.14.6 or 10.15.3?
Thanks
from Apple: This is still a high priority for Apple and we're doing everything possible to resolve this. This issue is more complex than it might appear.
You mentioned previously you can install apps but "all" apps are not updating all the time. Specifically, which applications? Please list all you can that are affected.
I'd also like to mention we are tracking a separate issue related to updating MS Office apps in macOS Catalina. I assume this is consistent across different sites and locations, correct?
So like many of you this has been going on for...[checks watch]...ever. Did anyone else Try @ikhlasberrazi's fix of
After adjusting our firewall to allow all incoming traffic from the Apple IP range 17.0.0.0/8 issues were resolved. The previous role *.apple.com was not sufficient anymore.
and anyone have luck if you did? Is your fix still working? After yet another unproductive call with our SE and Sales Rep yesterday asking "what would it take to get more Macs in your .org?" and the answer being to "fix yo shiz" I thought I'd reinvestigate people's workarounds.
Also - FWIW my ticket with Apple support is considered "This is your case priority: Low - Other Questions or Issue" in their eyes.