Deploying Adobe CS3 and CS5

Double-check your snapshots. My suspicion is that you're overwriting the licensing database for one version when installing the other (careful anything with FLEXnet Publisher in it).
On Sep 24, 2010, at 1:17 PM, Nicometo, Tim S. wrote:

Suggestion is to use your snapshot for CS3, then use Adobe's AAMEE tool to build a pseudo-PKG installer for CS5. That way installing CS5 after CS3 will add to, not overwrite, the licensing database...

You can read between the lines, this was sent to me before because I had
the same issue, below is what was sent to me.You will need to package
just the license file for both packages together load one of youre
packages and then load the other manually and then capture the
/Library/Application Support/Adobe/Adobe PCD and package this.

It's because you're Flash Catalyst package is overwriting the license
file. This license file (actually its two files, contained in
/Library/Application Support/Adobe/Adobe PCD/) stores licensing
information for all versions of Creative Suite.

The solution to your problem is to either remove that file from you
Catalyst package, and license Catalyst manually on installs, or creative
a licensing file that holds keys for both your CS4 and FC-CS5 license
and deploy it separately.Alternatively, you can just install CS4 before
you do your initial Composer scan to create the Catalyst package, this
way the captured license file contains both licenses by this method as
well.

My preferred method is to create a separate "Master" License File
package that contains the license to everything I own. This way I can
install any apps in any combination, as long as they fit our licensing
model with Adobe, and not have to worry too much about licensing.

I hope this helps.

Regards,

-Sean Hansell

JWT

Patrick Bachuwa

Client Technical Services

Sears Holdings Corporation

Michigan Campus

3000 W. 14 Mile Road

Royal Oak, MI 48073-1717

Phone: 248 637-0350

Tim,

I'm not a fan of using Composer for something AAMEE is designed to do (and does well). :)

If you have no choice but to package using Composer, why not manually install CS3, then manually install CS5. Then test to make sure both suites work properly. Then create two packages. One with CS3 (and all the FlexNET stuff). One with CS5 (and all the FlexNET stuff). This way nothing in FlexNET breaks. We followed this process with two older versions of CS and it worked.

Have you tried using AAMEE to create the CS5 pkg, then installing on a computer that has CS3 installed?

Don