Forum Discussion
Acrobat DC Install via Intune
Has anyone been success on deploying Acrobat DC Professional via Intune? I downloaded the package from Adobe and used the IntuneApp to create a package but so far it refuses to install failing with a
(0x80070005) error. I can deploy the reader without issue. Deployed Dreamweaver and Photoshop CC without error but this one is puzzling. This like all of CC is subscription based now, so not sure what I am missing...
30 Replies
I have recently tested the deployment of Adobe Acrobat Reader App on Intune managed Windows 10 and Windows 11 devices. Please refer to the post: https://cloudinfra.net/deploy-adobe-acrobat-reader-using-intune/ to check the steps and get more details on this.
- I had issues with deploying Adobe products a while back. I noticed that the application required some MSI switches that I had never seen before. I think it was sys language and source folder (not seen these before) Also this isnt an issue if you run the installer as administrator or system since it will use some default values then.. 🤔
- The last time I needed to install Adobe Reader, I used Winget. Worked like a charm
- Below is how i managed to get it to work:
Install command: AcroRdrDC1900820071.exe /sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES
Uninstall command: msiexec /x {AC76BA86-7AD7-1033-7B44-AC0F074E4100} /q
Detection rule: File C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\
I got the installation file from Adobes own site - note that there is a specific file for distribution that differs from the standard installation file that you normally would download and install on a single PC.Hjorthen Yes, that works great.
When you download the enterprise version of Adobe (The latest version is AcroRdrDC2100520048_en_US.exe). Extract that to a temp folder (.\AcroRdrDC2100520048_en_US.exe -sfx_o”<path to extraction folder>” -sfx_ne).
Within that new folder are the setup.exe file and a setup.ini which contains the patch line (the msp file). You then use the IntuneWinAppUtil.exe to create an intunewin file. Set setup.exe as the setup file and when creating the win32app in MEM, use the install command in Intune as below: setup.exe /sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES
- Hi,
Maybe working around the problem and publishing it on a different way?
Deploying it with serviceui. With serviceui.exe you could create an interactive install. When the end user needs to install the app, he could open the company portal and install the app by clicking forward/forward on the install wizard (which installs the app In the system context)
https://call4cloud.nl/2020/11/company-app-unchained/ I'm successfully deploying AcroDCPro as a win32 app. I created a .mst via the Adobe configurator and then install using a .cmd which looks like this:
start /w msiexec /i "%~dp0AcroPro.msi" TRANSFORMS="%~dp0Transform.mst" PATCH="%~dp0AcrobatDCUpd1901020091.msp" /qn /L*v c:\Management\InstallReader.log
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"
