Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Acrobat deployment from SCCM won't install

Community Beginner ,
Dec 08, 2017 Dec 08, 2017

Hello all,

Via the Adobe Creative Cloud Packager version 1.13.0 build 59 I don't manage to build a working MSI file for Adobe Acrobat. For all the other packages like Photoshop I've no problems at all.

I've made a package with my admin account and so with my user account. Added the MSI in SCCM like always. Mostly it shows up in the Software Center as Installed but it isn't on my client.

Could someone helps me out?

5.8K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

New Here , Dec 21, 2017 Dec 21, 2017

I had the same problem as you, I found the solution to be to run the exe in the build folder with a --silent switch.

Translate
Adobe Employee ,
Dec 08, 2017 Dec 08, 2017

Check the CC installer logs for a failure

Log Collector Tool

If it's a failure in the CC installer that prevents the Acrobat installer from running, then you will see what the error is and be able to go from there and troubleshoot the CC installer.

If the log shows a failure in the Acrobat installer then try to collect the MSI verbose installer logs. You will need to enable a registry entry that is documented in this Microsoft KB to have the log file created.

https://support.microsoft.com/en-us/help/223300/how-to-enable-windows-installer-logging

Once the verbose installation log is created then you can look through the log to find possible errors in the installation.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 21, 2017 Dec 21, 2017
LATEST

I had the same problem as you, I found the solution to be to run the exe in the build folder with a --silent switch.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines