CS5 Adobe Packages Fail to Open after Install

[#1]

Hi,

I've created packages of my CS5 Adobe apps using Composer. After installing the packages they fail to launch giving an
Adobe error 6. Is this a known problem with a clear solution? The apps installed fine on the host from which the
packages were created. Updates were run and all was good. Interestingly, I don't have this problem with my Master Collection
pkg. Just with the individual applications that are licensed separately.

Also, I've just gotten started with Casper Imaging and must admit I'm off to a slow start. Does anyone have a workflow
document they'd be willing to share? I've looked at what I've been able to find on the Jamf website and haven't found
the step-by-step process I had hoped for. I'm sure that once I get rolling with this it's going to be great, but it's taking
me more time than I expected.

Thanks,
Lawrence

Lawrence Hass
Director, Multi-Media Labs
University of Colorado Denver
College of Arts & Media
College of Liberal Arts & Sciences
Office 303-352-3770
Mobile 303-810-0262
Fax 303-556-2335

[#2]

Hi,

Are you installing this over cs4? I can't install CS5 Master Collection over a CS4 and that is with Adobe media. I have a call into tech support. I am pretty sure I get an error 6 as well.

If you look in LibraryColorSncProfiles their is a folder called Profiles. In CS4 this is a folder in CS5 it is an alias. When I was testing AAMEE during its beta this folder was causing issue.

I will let you know what support tell me, but I am not in the office until Thursday.

Best wishes

Michael

[#3]

I am having the same issue with my CS5 Production Suite. Loads fine in Composer, then fails to run after imaging. Interestingly, I redid my image master without Adobe and tried to install it manually after an image and it would not let me install After Effects or Illustrator. Any clues out there as to what is causing this?

Roy A. Baril
Director of Technology
UC Berkeley
journalism.berkeley.edu

[#4]

Aha... I think you nailed it. Jamf said to Compose the CS4 stuff first,
then the CS5. And, they said to rank the packages so that the CS4 programs
would install first. Hmmmmm.... I think I will try and reverse that
order..... I will let you know how it works.....

Thanks,

Roy

[RobertHammen]

This is undoubtedly related to licensing. If multiple packages are writing into /Library/Application Support/Adobe/Adobe PCD, overwriting the DB there, that can be an issue... also watch /Library/Preferences/FLEXnet Publisher...

[donmontalvo]

We've been holding off on CS5 distribution to avoid these kinds of problems. Been burned too many times in the past (since CS3 introduced the dreaded FLEXnet licensing engine). We're hoping to let JSS do all this for us, using Self Service (the user or a tech can trigger; scoped to specific computers). That is, after JAMF certify JSS for CS5.

Thanks,
Don

[RobertHammen]

If you want to deploy it this way (user-initiated via Self Service), you can use AAMEE to build the pseudo-pkg files and deploy them via Casper. I had to override to force an AFP rather than http download of the installer, but it's worked fine here with zero issues.
On Jul 19, 2010, at 10:50 AM, Don Montalvo wrote:

--Robert

[donmontalvo]

Hi Robert,

That's encouraging news. :)Did the process require a logged in user?

Thanks,
Don