Acrobat XI Not Remembering Serialization After Deployment

[Guest]

I am currently working on preparing several Mac OS X (10.8.3 or Mountain Lion) images for deployment at the school where I work. These contain both Acrobat XI and the CS6 Master Collection. For CS6, I use a serialized deployment package that I created with AAME. This enables the Creative Suite to hold on to it's serial number and registration information after the image is deployed to other Macs. However, I've not been successful at getting Acrobat XI to do the same.

At first, I installed Acrobat manually in my image, using the standard installer and entering the license information by hand. However, I observed that after applying that image to another Mac, Acrobat did not retain it's serial or registration. So, I then downloaded the Acrobat Customization Tool and created a serialized package with that. I then uninstalled Acrobat from my original image and added this package as a post-imaging installation in DeployStudio, which I use to deploy my images. That seemed to work great, but a few days later I launched Acrobat on an imaged Mac and found that it opened to a request for the serial number. This would have been irritating if it had happened upon the first launch, but it worked just fine for a week and a half, leading me to believe that there was nothing wrong.

I thought that perhaps this was a result of my original image having Acrobat installed, then uninstalled, then re-installed with the serialized deployment, so I tried applying the same serialized package to an installation of OS X that didn't have any previous Acrobat or CS6 installation and when I opened it up post-deployment it was asking for me to sign in with an Adobe ID despite the fact that the package was supposed to suppress all requests for registration.

I'm seriously confused as to how I can get a serialized copy of Acrobat deployed to my 250 + Macs without having to manually enter the serial number on each and every one. What can I do?

[Guest]

If you have another CS6 Product installed with the same CS6 serial number then look at solution #3 in this KB:  http://helpx.adobe.com/creative-suite/kb/acrobat-failed-launch-30-days.html

[Guest]

Thanks Sabian. That might work, however I have 250 + machines to deal with and a very short amount of time in which to do it. What I really need is a way for this to work in the actual image.

[Guest]

You should be posting AAMEE questions in the Creative Suite Forum as that installer uses the customized Creative Suite installer which is different than the Acrobat installer.  As I also stated in the previous thread (  http://forums.adobe.com/message/5368801#5368801 ) you should be looking at the licensing logs. Because that is probably where the issue has root cause.

[Guest]

This isn't a question about AAMEE, because I didn't use AAMEE to create this installation package. I used the Acrobat Customization Tool, as is detailed in my original post.

As far as the licensing logs go, there aren't any for Acrobat, as it does not get installed with the rest of the CS6 Suite. It gets installed by it's own standalone installer, made using the Acrobat Customization Tool, which is supposed serialize each system it's installed to. Which it does not seem to be doing, hence the issue.

[MichaelKazlow]

Moved to Creative Suite Enterprise Deployment