You will want to install Elements once manually to dig these keys and their contents out of the registry, then add them in again once you've deployed the app.
The reason being is that the Serial Number is encrypted and included in these keys. For some reason, when installing from the MSI, these keys aren't created. What results is an error that your Serial Number is Invalid when you attempt to run the program.
Kong_Harry's method is best but not well explained. Here's my Full HOW-TO:
-Create a transform from the MST template (This is better than "Tailoring" one...)
-Enter the serial number by seting the SERIALNUMBER property like this: 1234-1234-1234-1234-1234-1234
-To have the serial number accepted by the program the Epn function must run. Copy the "Serialization" Custom Action from "All Custom Actions" listing in MSI Script.
Pasted it in MSI Script in the Execute Immediate sequence after CostFinalize and then add the condition.
Copying is probably the only way to avoid specifying where the "NewBinary19" is. It should look like this:
If Not REMOVE then
Call DLL From Installation Function Epn(Serialization1)
Not sure if Ghost AI packages are discussed here (first time poster), but since Winstall LE didn't work for me building an .msi package for Photoshop Elements 3.0 (Elements required serial number after msi install), I had to use Ghost's package builder. When building an AI package for Adobe Photoshop Elements 3.0, don't restart as requested by the installer. (If you restart, the AI package will seem to install fine, but tools and menus were grayed out for me.) Instead, cancel the request to restart your computer and run the 'after' snapshot right away. This worked great for me and I now have a deployable package for Photoshop Elements 3.0. The only thing I couldn't get rid of is the registration nag screen. But that's easily gotten rid of by just attempting to register one time. After that, it assumes you actually did register and the nag screen is gone for good.
Edit: This installation uses the CD from Adobe licensing. It might be different with a retail CD.
In order for a silent install to sucseed (with /qb switch og Active Directory Deployment), you need to trigger the epn-function. This function is only triggered by UI by default. By adding something like
If Not REMOVE then
Call DLL From Installation Function Epn(SerializationNonUI)
for example after CostFinalize in the Execute Immidiate sequence, it will work.
It's bad design. This function should always be called.
Even I have applied this registry tweak, I kept having registration popup. As I was logged on Administrator, this was not a permission issue. I had an other pc where I have registred the software. After observation I found out that there is a file called "log.txt" under
%userprofile%\Application Data\Adobe\Photoshop Elemets\3.0\Organizer
Content of the text file looks like this.
0 Photoshop Elements 220.127.116.11 Log (5) started 2005-01-21 10:59:05.330
15 RegisterConnect matched
If I rename this file, it asks for the registration.