Skip to main content
A
Anonymous
April 16, 2013
Question

Package created in Adobe Application Manager Ent - CS6 Standard install - Acrobat does not install

  • April 16, 2013
  • 2 replies
  • 2797 views

Hi All.

I hope you can help and assist me. 

It's the first time I have used Adobe Application Manager Enterprise , as  I need to do a create a few installation packages,  for Standard and Premium for both the PC and Mac which I will use to deploy via Group Policy and ARD.

When creating the package. I selected the CS 6.0 apps I wanted to install.  The package was created,but for somee unknown reason when the package has run , Adobe Standard is not installed.  

Looking the folder contents there is a folder called Exceptions where a AcrobatProfessional10.0-EFG exists.  I thought it was something I did at first , so I have re-created the package again and the same thing happened. 

Are you able to offer any advice or suggest what I need to do next please.

Thanks

Luke

This topic has been closed for replies.

2 replies

S
Adobe Employee
SachinPorwal
Adobe Employee
April 17, 2013

Hi,

Adobe Application Manager Enterprise Edition / Creative Cloud Packager generates MSI/PKG packages along with few Exceptions. Acrobat professional is part of the Exceptions folder, which needs to be deployed separately from main MSI/PKG. eXception Deployer Application(XDA) is a command line tool to ease deploy all Exceptions, it is copied in the Exceptions folder itself. Please refer to the deployment guide "http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeApplicationManagerEnterpriseEditionDeploymentGuide_v_3_1.pdf" for more details.

Thanks,

Sachin | AAMEE-CCP | Adobe Systems

Don Montalvo
Don Montalvo
Inspiring
April 24, 2013

Hi Sachin,

When we use AAMEE 3 to create CS6 packages for OS X, Adobe Acrobat Pro X is gets installed as part of the main package. The only items that end up in the Exceptions folder are Adobe Air and any Adobe Air apps (like Adobe Help, etc.).

Not sure about the PC side.

Luke, you mentioned Standard and Premium; did you mean Design Standard and Design & Web Premium? If you meant Acrobat Standard, that doesn't exist for OS X, only Acrobat Pro exists.

Don

Don Montalvo
Don Montalvo
Inspiring
April 24, 2013

Resolved. For some reason this folder exists:

~/Library/ColorSync

It shouldn't be there, but since it exists, Acrobat Pro X tries to use it.

Since it has incorrect ownership/permissions, Acrobat Pro X can't use it, so it tosses up that error.

At some point we'll determine how that folder got there, my guess is someone used the JAMF Casper Suite "easy button" (Composer) to create a package using a snapshot (which is an incredibly bad idea; logic exists in installers for a reason <wink>).

Don

Jeffrey_A_Wright
Jeffrey_A_Wright
Legend
April 16, 2013

Moving this discussion to the Creative Suite Enterprise Deployment forum.

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