Software Deployment

Did you check the Package KB on this site? If it's not listed, you'll need to use InstallWatch or INCTRL to investigate.

Yeah I checked the appdeploy KB , and have tried all suggestions on there

I forgot to mention, Im using Wise installer

-install photoshop on a clean machine
-take a snapshot with InstallWatch, INCTRL, or some such tool
-launch the app
-accept the EULA
-take another snapshot

Then you'll know what to add to your package. This is repackaging 101. [;)]

Thanks for the info, but I have already tried this. I think the problem is in that I have to create a transform because the EULA states that I cannot alter the original msi. If I were to just run a straight setup capture and compile I wouldnt be having this issue. I was hoping someone else had tried to create a transform for Elements and they knew of what to add into the registry settings or tables. Unfortunetly for me it seams there is no change in the registry settings and/or wise is not picking up on any changes. Installshield may be a better product but I do not have the application.

I didn't suggest you repackage the application. You should be running a tool that merely identifies the changes. Then you capture those changes in a transform.

I have just packaged this application using the following method:

[font="century gothic"]Run PSE_6.0_WIN_WEB_WWE_ESD1.exe
[font="century gothic"]Choose a location to extract the setup files to and click next (default will create adobe folder on the desktop)
[font="century gothic"]After copying files completes click deselect “Launch Adobe Photoshop Elements 6.0” and select “Open the specified folder” and click Finish
[font="century gothic"]Open the Adobe Photoshop Elements folder
[font="century gothic"]Create a new file in notepad and enter the following (amend the serial number string)
[font="century gothic"]
[font="century gothic"]<?xml version="1.0" encoding="utf-8"?>
[font="century gothic"]<Configuration>
[font="century gothic"]<Payload>
[font="century gothic"]<Data key="EULA">Suppress</Data>
[font="century gothic"]<Data key="Serial" protected="0">xxxxxxxxxxxxxxxx</Data>
[font="century gothic"]<Data key="Registration">Suppress</Data>
[font="century gothic"]<Data key="Updates">Suppress</Data>
[font="century gothic"]</Payload>
[font="century gothic"]</Configuration>
[font="century gothic"]
[font="century gothic"]Note that the adobe KB article detailing silent installs is incorrect for the option regarding suppressing the EULA message and must be used as above.
[font="century gothic"]
[font="century gothic"]Save this file in UTF-8 format in the same folder as the extracted MSI and data files and call it application.xml.override
[font="century gothic"]
[font="century gothic"]Create a transform to remove the desktop shortcut etc and any other company standards
[font="century gothic"]
[font="century gothic"]
There is a problem whereby the serial number is not written out during the installation if the installation is executed from a network location.

Adobe are aware of this problem, and it is documented here:

http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402610
[font="century gothic"]
[font="century gothic"]Either a) Write a script that will when executed copy the source media down to the local PC and then execute the installation from the local copy of the files.
[font="century gothic"]
[font="century gothic"]b) Have your deployment tool (Managesoft, SMS) copy down the source locally prior to starting the installation.
[font="century gothic"]
[font="century gothic"]Or c) Install from the network location but when the application is run for the first time the user will have to enter the Abobe Photoshop Elements 6.0 license key.

Jamie B, can you please write a Package KB for this package and include any links to Adobe's site as needed?

All the info is pretty much there already.

The OP needs to pay particular attention to the following line in the application.override.xml file
[font="century gothic"]
[font="century gothic"]<Data key="EULA">Suppress</Data>

Adobe incorrectly state that it should read [font="century gothic"]<Data key="EULA">0</Data>

After checking the KB, this snippet of info is contained in the last KB post for the package.

[font="century gothic"]Adobe are aware of this problem, and it is documented here:

http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402610Vendors like Adobe make my blood boil. In the time it took someone to create that KB article, get it proof-read, signed off and all the other cr@p that goes with posting docs on a major vendor's web site, a halway-competent packager could probably have worked out what the issue was, fixed it and released the revision. Of course, quite how a package with such a glaring flaw escaped a major vendor's QA process opens up a whole other set of questions....unbelieveable....

I know it is a too late reply.
However, I have recently found a solution to this problem.
The EULA and license information is stored in the cache.db file under Common Files\Adobe\Adobe PCD\Cache\.

Capture the db file with the license key and EULA, and copy the same with a custom action in your package.
Please note that, you cannot include this file in MST file table. It has to be copied via a custom action.

Thanks
Sooraj