Adobe CS6 deployment with AAMEE 3.1 and Group Policy

[Graham_Payton_SCCH]

Hi

I work at an educational establishment in the UK and we have just received our Adobe ELA license for CS6 Master Collection.  I am trying to get this deployed to our campus before term starts in about 2 weeks time.

We previously had a limited amount of CS5.5 licenses which I packaged up using AAMEE 2.1 and deployed via Group Policy.  This worked really well and I am looking to do the same now with CS6.  I have a few questions though if anyone can help please:

When applying updates at the package creation point AAMEE 3.1 does not include updates for Acrobat X.  Is this correct?

If so then how can I apply updates to the Original 10.0.0 installation that comes with CS6?  I was hoping to just create an AIP from the 10.0.0 files in another folder, for example 10.1.4, and then patch that AIP with the 10.1.4 MSP update file.  After that apply the newly patched MSI from the 10.1.4 folder to the group policy as an upgrade to the original 10.0.0 MSI.

If I do this then will it mess up the serial keys for Acrobat X?  I know that on the original installation there is no specific key for the Acrobat X, it appears to be serialised by the CS6 MSI install that I do afterwards.

Finally, and sorry for so many questions.  If I create a deployment package for 32bit and another for 64bit.  In the Exceptions folder I have the same 4 folders for both architectures

AcrobatProfessional10.0-EFG

AdobeDreamweaverWidgetsBrowser1.0-mul

AdobeHelp

AdobePDFSettings11-mul

Is the software in these folders identical for both 32bit and 64bit deployment packages, or is there a 32bit version and a 64bit version?

The reason I ask is that I want to make Group Policy deployment as easy as possible and put all the MSI files into one Group Policy for install.  If they are all 32bit for example then I only need to add them once.

Thanks in advance for your help

Graham

[Jeffrey_A_Wright]

Moving this discussion to the Creative Suite Enterprise Deployment forum.

[MrAdobinator]

Hi,

I am pretty much in the same situation as yourself, we got the Master Collection 6 about 4 weeks ago so it was a tight schedule to get it ready (and tested) for deployment for the start of this term - oh what joy I have had trying to get the thing to work, from the buggy and not-complete AIMEE 3.0 (Which I have just seen they have 3.1 beta out) to the fact that although Acrobat X is PART of the MC6 suite it requires separate configuration and the volume serial key doesn't actually serialise Acrobat if you try to deploy it without the rest of the MC6 suite.

To answer your questions: I have only used AIMEE 3.0 and this did not even include the update feature for ANY of the products, so you are probably correct, I have tried integrating the 10.1.4.msp update into the original installation which I have done successfully but this then breaks the deployment and I cant seem to serialised the product when rolled out with the rest of the MC6 suite.

Does your License Key serialise Acrobat Acrobat if you just do a single test installation and input the key manually?

I don't think Acrobat Pro is a native 64bit app, we have the whole suite installed on 64 bit machines and you only get one shortcut which loads the 32bit app.

We also have another two issues with Adobe Acrobat:

On certain machines it keeps reverting to the trial version, and as yet I dont know how to get round this (inputting the MC6 key fails)

and also, even though I have suppressed the EULA everyone has to click agree on the first run of the application.

Just a few things to be aware of there!

Hope it helps, Id be interested to hear how you get on.