Skip to main content
T
technologyd94833456
Participant
August 12, 2017
Question

Creative Cloud Packager Will Not Install .msi of Acrobat

  • August 12, 2017
  • 3 replies
  • 9128 views

Hi there,

I am a frustrated new customer and just got out of a bad chat experience with a technician so hoping the community can be a bit more helpful.

I have created several different creative cloud packages. One with ALL Adobe products and another one with just Adobe Acrobat. I have tried 32 bit and 64 bit and tested over 3 Windows 10 machines which includes a machine that was just reformatted and contained no history of Any Adobe products. Unfortunately, Adobe Acrobat is never installed on any of these packages; regardless of the configuration I select.

I should say it works perfectly fine for MAC packages. In addition, if I manually go to a computer and run the .exe package to install Adobe Acrobat it will work. However, who wants to do that on a several hundred computer network?

I could use some help on how to get a .msi package to correctly start to deploy Adobe Acrobat as part of my bundled package or a standalone.

This topic has been closed for replies.

3 replies

R
Adobe Employee
ravinderg62643219
Adobe Employee
December 7, 2017

Hi

Are you installing Creative Cloud package using the msi file of setup.exe?

Installing via msi file will not install Acrobat. Please run main  setup.exe inside "Build" folder in the package to install complete package.

Regards

D
davidb18368380
Participant
December 12, 2017

Unless that setup.exe supports a silent switch then that's not rather Enterprise friendly.  Why would Acrobat be allowed to be part of the Creative Cloud bundle yet the .msi installs everything BUT Acrobat?

R
Adobe Employee
ravinderg62643219
Adobe Employee
December 13, 2017

Setup.exe do support silent mode. "--silent" switch can be used to silently install the package.

D
davidt191088
Participating Frequently
September 20, 2017

I can tell you one issue is that most current SCCM admins do not want to use packages anymore. Applications are the way to do it since you can detect MSI GUIDs or exe versions. I am doing this with my setup now. I will work on trying out the MSI only but still was getting a blank screen when the process finishes. Users cannot deal with that. Why can't we get this deployment to work like all of the other CC apps? Every other CC app deploys flawlessly with little work. Acrobat Pro has been an animal for years.

D
davidt191088
Participating Frequently
September 20, 2017

Also that link to the SCCM deploy is for 2007. May wanna update that a bit.

rpandita
rpandita
Inspiring
August 14, 2017

Hi technologyd94833456

Please check this link and follow the instructions.

Learn how to deploy Acrobat Pro or Standard for team Single App

~Rohit

D
davidt191088
Participating Frequently
August 21, 2017

This is not relevant to the CC Acrobat Pro 17. The Customization wizard is not relevant for the new versions.

D
davidt191088
Participating Frequently
August 21, 2017

How about they make this work like all of the other CC apps. Everything else deploys perfectly. I end up with a black screen every time and every way I deploy Acrobat Pro in SCCM. Even tried making the gui pop up with no success. This is a major issue for many shops. How can I get this thing installed?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices