Forum Discussion
Acrobat DC Install via Intune
Hi Jeff,
how are you triggering the setup? Via a custom Wrapper script or direct msiexec call? If you use a PowerShell or cmd wrapper are you writing an additional log file?
My suggestion would be to use psexec to start a command prompt in system context (psexec -i -s cmd) and test your Adobe Professional installation with an PowerShell wrapper in system context and let the setup write additional log files. Normally you get enough indicators in the log file then to resolve the issue. As soon as you have success, use the wrapper and Adobe files and generate a new .intunewin and try again with Intune. Normally a log file and test install in the same execution context (system context) is necessary to troubleshoot these failures.
best,
Oliver
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)
- kubidag
Microsoft
Is your app install command line generating a log somewhere in the system? Did you take look at the IntuneManagementExtension.log located in "C:\ProgramData\Microsoft\IntuneManagementExtension\Logs"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.
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.
