Forum Discussion
Acrobat DC Install via Intune
Hey Oliver,
Right now, I downloaded the package from Adobe. Extracted the files; which creates a folder called Build. In that folder is both a setup.exe and AcrobatDC.MSI. I then ran the Intune WinAppUtil and have choosen both the setup and the MSI without luck. Right now, I have the setup selected and within Intune, I have setup /quiet as the command. I was able to find the uninstall command and that is msiexec /x {AC76BA86-1033-FFFF-7760-0C0F074E4100}
The detection string is the MSI with {AC76BA86-1033-FFFF-7760-0C0F074E4100} in the field.
The latest error is (0x87D300C9)
- Jeff HarlowMar 07, 2019Iron Contributor
Not entirely certain what logs Acrobat would produce. Still tracking that one down as I know there is a new feature for Win32 troubleshooting to gather those logs. The Intune logs are so encrypted, I cannot even follow them to figure why it is failing. I have an issue open with MS but they have been slow to respond on this one. This is bugging me as I deploy Dreamweaver and Photoshop nearly identical. But I do now that Acrobat typically requires a restart and also require Outlook to be closed, so there are additional variables that could be causing the problem.
- mirthrockApr 09, 2019Brass Contributor
Jeff Harlow Did you ever find a solution to this? I'm running into the same issue. I even tried to deploy the MSI as a LOB instead of WIN32 and I haven't had any luck either.
- Jeff HarlowApr 09, 2019Iron Contributor
mirthrock Yes. After a few weeks going back and forth with MS. The solution was to use the Single App deployment method instead of building a package for Acrobat. Not entirely sure why the package never worked (as that method works for other CC apps). Here is the link MS provided which solved the issue.
https://helpx.adobe.com/creative-cloud/kb/deploying-acrobat-singleapp.html
I did not need to do the customized wizard, but YMMY.