Adobe Installation and Licensing

I am one of those Mac admins who has figured out how to deploy the Creative Suite in parts. And my comment is that the registration database is a silly idea. A folder full of individual files (one per application) would work just as well, and would be more deployable. Stuffing everything into a database does not bring any adavantages that I can see, and brings this huge complication.

Please make my job (and probably yours) easier for the next version and seperate this data into individual files. In fact I would really like to see a push to get all of the dependancies cleared out of the installers. Take care of loading dependancies at run-time, not install time. And I am NOT talking about self-heal... that whole idea was an abomination from the start.

Whenever I try to install with the AdobeUberInstaller (created from the CS4 deployment toolkit), I get the message:

"This application requires a version of Adobe Air which is no longer supported. Please contact the application author for an updated version."

I wish that Remote Desktop was a more eloquent solution for these Adobe deploys than it is. It's a bummer that the package can't live on NFS when pushed out via ARD. That is a bit disappointing, and made using ARD much more difficult for me.

We use Composer, after trying and failing to get Adobe's network deployment tools to work.

Your post highlights the main problem with such tools: the probability that a subsequent install will overwrite the licensing database. We just have to observe a strict sequence in remote deploys to overcome this. And, as the previous poster notes, this could really be considered a design flaw in your licensing scheme.

The benefits of the third-party route are significant: much faster installs (an order of magnitude faster) using standard tools; perfect reliability in our experience and no need to trouble-shoot the install process.

I'm a bit late coming to this party, however one tool/workflow that would be good to link to above is the InstaDMG and InstaUp2Date workflow scripts, developed by the guys at AFP548.

If anyone can find any way whatsoever to get any deployment tool to deploy Adobe Acrobat Pro for Mac, in a manner where the user doesn't have to:
a) have admin access
b) know the serial number
since that *is* the point of a deployment tool, then I will hand you my first born child and a large wad of cash. It is my understanding that it is impossible, since there is no "installer" per se, and it always comes back to needing either a) or b) or both.

That is not good enough.

These deployment tools are all excellent products, however they are hamstrung by the poor installer tech used by Adobe. Licensing failures, region (en_US vs en_GB), error code 7, workflow errors... I have a situation where After Effects always comes up with a licensing failure on its first launch, then works correctly from the second launch onwards. That's really poor.

Seriously guys, what do you people do in Adobe to deploy Adobe products? Do you eat your own dog food? Go ask your IT guys what they think.

Acrobat family installers are done in a separate team here; but, I'll forward your comments and queries to them.

I also don't think its possible to deploy without admin access. That's certainly true for the Adobe Creative Suite 4. It is possible to generally deploy the Adobe Creative Suite in trial mode by not supplying a serial number; but, Adobe Acrobat Pro 9 for Mac does not support a trial mode and so a serial number is required.

The problem with acrobat pro is not related to the installation process (which can be done easily as an admin using ARD...). The problem with Acrobat occurs at first launch after the install, when it's time for the user to work with it !! Acrobat Pro (And distiller) both asks :
1 : that another CS app must have been launched before using acrobat ?!?
2 : to install new pieces of software (this damned internet plugin that tries to resinstall itself every time, but it's another issue) and the PDF printer driver.
3 : At this time Acrobat asks for an admin password (even if the user is the admin. And that's the real problem !!

So here are some solutions I've tried :
* making a "monkey process" using Applescript but the password dialog does not accept that (for obvious security reasons).
* tried to launch the app as an admin: no way as it still asks for the password.
* tried to create an "snapshot" package, but it seems the licensing stuffs are time or machine related.
* tried to launch the perl files in the selfHealing subfolder. I havent succeed as it seems acrobat needs other licensing stuffs at first launch.

If you have another solution, please tell us !

Also, these licensing stuffs are really a mess. It only prevent good, honest user from working fast, it spends a lot of our time getting around the mess that that protection gives us and never prevents pirates from stealing your software anyway !! So by trying to protect you, you are spending time in protection (I'd prefer that you correct your bugs instead), your going to loose honest customers and urge them to use cracked versions available around the web!!

There is also a dramatic lack of support for us IT guys. This tends to fed us up : A new release every year(which we have to pay every time) instead of giving correct patches. No support for IT. Though the new deployment tools are there, these are neither standard, nor easy to use, nor working as wanted! All we want is to install the files by a simple copy from a server.