SOLVED Adobe Acrobat Standard installation with Registration Key

[Dinesh Rakhyani]

Hi Prajwal,

I am new to SCCM. Can you help me as I am looking to create a package for Adobe Acrobat Standard XI along with registration key. Also could me guide me on how a registration key is pushed through GPO and and the location of registry key in regedit.

Thanks.
Dinesh Rakhyani

 

[Prajwal Desai]

Hi Dinesh,

You need to download the Adobe customization tool to deploy the Pro version. check this link - http://blogs.adobe.com/acrolaw/2013/02/acrobat-xi-deployment-guide-for-large-firms. If its doesn't work let me know, I can try out the same in my lab setup.

 

[Dinesh Rakhyani]

Hi Prajwal,

Actually we have done this few months back, however users are getting message to re-register adobe standard XI, wonder why!. Also there is no recent change made for the same.
1. Is there a possibility to push registry key via GPO.
2. Or is there any other alternative.
3. .mst file which was created for previous installation is not accessible now.

 

[Prajwal Desai]

I don't think there a possibility to push registry key via GPO. Could you check the number of licenses used by users ?.
.mst file which was created for previous installation is not accessible now - What exactly do you mean by this ?. If its missing you could try creating a new one.

 

[Chris Cools]

If I may share our experiences with automatic registratrion of Adobe products... It's nearly impossible to achieve this, Adobe products tend to 'bother each other' when you install or uninstall one of them. We've had issues with Adobe Photoshop after installing a new package for Adobe Professional. Although they are two different products and have other license / registration keys, we encountered the exact same problems as you did. Clients were asked to reregister their products... We've logged an incident for this issue directly with Adobe but they never managed to solve the problem for us, Nowadays we've created some scripts that 'fix' the issue after install / uninstall and workaround the problem like that.

Please let me know if you ever succeed to solve this one without some kind of workaround Our packaging team did everything you can imagine to get this working, with assitance from Adobe even, it still doesn't (always) work 'out-of-the-box' (and with mst file).

I suppose Adobe products share parts of the file system and registry for multiple Adobe products and there lies the problem... I think...

 

[Prajwal Desai]

Hi, I am marking this thread as Solved.

 

[Chris Cools]

You do not need to push the activation key via GPO, just use the Customization Tool from Adobe as mentioned by Prajwal. Include the .mst file in your package / application and as soon as an internet connection is available on the client, the software will get activated automatically.
Concerning the registration issue, you can also disable registration via the Customization Tool.