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.
Yeah, I was testing out MAS apps and the Office Suite installer. Installer worked flawlessly where the MAS apps was hit and miss on whether they installed or not. I decided to just remove MAS apps as a source for deploying/installing Office.
@pbowden I wasn't able to find a great uninstaller. Have you ran across one? I was looking to get one setup in case we need to uninstall O365/Teams and reinstall for any reason.
@bcbackes yeah, I was thinking at the weekend of putting an uninstaller together. There are two scenarios I can think of:
You want to put Office into a factory defaults state. Basically, remove all Config files, keychain items, group containers, Outlook profile, etc but leave the app bundles intact in /Applications
Do all of #1, and delete the app bundles in /Applications
I like the idea of #1 because I find that when Office isn’t working, people tend to delete the apps and get frustrated because the problem is usually one of the Config files. They also waste time by re-downloading the installer pkg from the CDN when this is very rarely the problem.
@pbowden Both options sound great. Like you said, option 1 brings it back to default. I'm thinking it would be similar to taking a snapshot of a VM right after you install Office, then, when things are messed up you restore it back to the part right after the install. That would certainly save time of having to redownload/install the app bundles.
However, I do see a benefit with option 2 as well. If there happens to be an issue during installation where something didn't install right, however, it wasn't bad enough to prevent the app from opening. In that situation I would like to nuc everything including the app bundles.
Nowadays there can be multiple variables on why things don't work correctly. For most tickets, I spend "x" amount on it before I decide it's time to uninstall/reinstall. I really hate to spend 3 hours trying to resolve an issue especially if uninstalling/reinstalling will resolve it. It's a fine line and each situation will dictate how much time I spend on it.
I too am still seeing this issue after implementing a workaround from Jamf for a separate issue where Self Service installed MAS apps cannot update and you have to delete the app and reinstall it through Self Service. PI-005189 - Self Service fails to display updates for Mac App Store apps if an older version of the app is already installed on the computer. Workaround: Use the Mac App Store to download the app update. ---- Which will only work if you are signed in with an Apple ID that has that app in its purchase history. Defeating the purpose of Volume Purchasing.
Jamf suggested setting the app to install Automatically and scope it to a Smart Computer group looking at a custom EA. That's when I saw the <MDMClientError:72> error. I have been trying to get Apple to give me an update on this issue for the last couple of months but all they are saying is "we only respond when there is a fix, which there isn't at this stage".
Personally, I think Jamf should be pressuring Apple on this issue.
Just want to post this as a quick workaround with Managed Apple IDs and pushing apps.
If you're getting this error, go ahead and get the user to open the App Store. They can click on their name in the bottom left, and a list of "purchased" apps will appear. Whatever app you licensed to them will appear there, and they can just go ahead and download/install it from the App Store itself.
I was experiencing this issue, and was diagnosing with a user. Was about to get them to sign out of the managed Apple ID and use a personal one, when I noticed this. Seems like the license gets properly assigned through the MDM, but the installation at the OS level fails.
This circumvents it, without the need of asking the user to hit "Install" until it just magically works the 100th time.
I've been keeping half an eye on this thread for six months or more after running into this issue with a few apps. I haven't really touched Mac App Store apps since then and I'm wondering if in a macOS 10.15.5/Jamf Pro 10.21 world, whether things are still messed up enough that it's not worth my time even exploring these apps or whether it's time to dip my toe back in the water and give it a shot? I find it hard to believe that the feature is so irreparably broken that it's useless but it's also pretty hard to believe how long this has been an issue with no apparent fix.
It seems to be working occasionally, we are definitely seeing an improvement, usually the apps would not install at all, but currently we are getting VPP errors but the app will eventually install. We are using macOS 10.15.5 and Jamf Pro 10.22.1
I had a user today that was trying to install a couple apps but were on VPN. I had them disconnect VPN and try again. The reported back that all apps installed as expected.
@jwojda : which VPN provider are you using? And is it split-tunnel or full-tunnel? Are you seeing this on all versions of macOS or just just the latest?
We're having it here with iMovie and XCode. Nothing like trying to get software on machines for the start of the semester and having it inexplicably and silently fail...
