Deploying CS3

Authored by: Anonymous on Monday, March 12 2007 @ 02:47 am CDT

Is there a better proof that Adobe is cracy? And if you deploy it like that, what will you get on the clients side? 200 Fonts in /Library/Fonts an a complete install of Version Cue, including a unnessesary SQL Database engine? I think the best way to deploy CS3 is the same way as with CS2. Install it on a clean system, clean up the installation, look what has changed and make a PKG out of that stuff.

[ Reply to This | # ]

Authored by: Anonymous on Thursday, March 15 2007 @ 05:02 pm CDT

What about managing CS3 serial numbers? OK, so I can mass deploy the apps to my 200 Macs, but how do I register the serial numbers etc?

Agreed - an out-of-the-box .pkg file sure would be nice. Adobe - get a clud. I'm tired of building homemade packages for your apps.

[ Reply to This | # ]

Authored by: donmontalvo on Saturday, March 17 2007 @ 08:15 pm CDT

cs2 was a monster to package but it was well worth the effort. 2.1g pkg with some real p.i.t.a. file merges, symbolic links, aliases, etc. i took a look at this "silent install" from adobe and i'm willing to give it a try, but i'll most certainly update our logout hook to prevent the flood of fonts and unnecessary cr@p (read: version queue, a process that's installed turned ON by default), and adobe updater from kicking in when a non-admin user is logged in. don

---
don montalvo, nyc

[ Reply to This | # ]