Software Deployment

I think your answer may lie here:

http://www.appdeploy.com/packages/detail.asp?id=266

I'm assuming you need an MSI for deployment reasons? If not, you might consider creating a WiseScript package (exe) to check the results. Once or twice when I just could not get a working MSI package out of an installation, I have resorted to making an EXE package witch doesn't need to follow the many rules of MSI, and have had success. Worst, worst, worst case- an EXE packaged application run as a custom action in an MSI.

thanks, that was what i was looking for, I missed it on that page just looked under A for adobe illustrator.. [&:]

Bob,

We want to repackage this (and Photoshop CS) into MSIs to follow our Corp Standards.
The problem is with the Serial Numbers.

During the installation the Product ID (on the back of the CD) is entered and some algorithm is run to generate a unique number that is stored in the registry (the SERIAL value).. If we repackage this all our installations will have the same serial number, which isn't ideal.

I don't suppose there is any way round this?

Rgds, Steve.

Steve,

Not an easy solution anyway. From what I have seen, most organizations go ahead and use the same serial number in there deployment, but are careful to track the number of installed applications so that it does not exceed the number they have purchased. Most vendors turn a blind eye to remote deployment and simply say they "do not support this" situation. I have also heard of organizations that script the update of such information at install time (using properties/custom actions/external lists) which can certainly be an involved exercise. Finally, if you have 10 licenses, you may consider deploying the 10 licenses identically, and then scripting the update of the registration number after the fact (testing to make sure it does not cause problems, of course).

Hope this helps,
Bob

custom action in an MSI.

I have problems in packaging Adobe Distiller 5/5.05. I am using Wise Packaging Studio 5.1
Once packaged into an MSI, installation completes normally. But when I launch Adobe Writer 5 it gives error messages like:

ADBC.API could not be loaded because Javascript is not supported

and the application does not function as its supposed to.

Has anyone come across this? Or if someone can give me some tips on packaging Adobe Writer/Distiller 5/5.05

Thanks

I dont see that file in the installation at all.....I suspect that you have a rogue registry entry that is trying to register a file or something.

Yes Correct
After Setup capture Import following Registries into the package, as these registries are excluded by Wise.
These uninstall keys contains Licensing information and need to run the application.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{91A4AD99-69CE-4745-97B7-0E0DFBECFDE5}]
"RegCompany"=
"RegOwner"=
"Serial"=

I need to add more information about Package customization :

For Disabling the First Run Welcome Screen Following File should be included into the package : The location is %appdata%\Adobe\Adobe Illustrator CS Settings\AIPref
To disable first Run welcome Screen we need to set showQuickStartDlg 0,
We can customize number of options from these file.

To disable the Internet Upgrade
Following registry to be set

[HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Illustrator\11\Registration]
"PRODREG"=dword:65686669

This package installs SVG viewer 3.0
As the .svg and .svgz file extensions are opened with IExplorer.
So these entries to be put from registry table.

[HKEY_CLASSES_ROOT\Adobe.SVGCtl\DefaultIcon]
@="%SystemRoot%\\system32\\url.dll,0"

[HKEY_CLASSES_ROOT\Adobe.SVGCtl\shell\open\command]
@="[IEXPLORE] -nohome"

Where IEXPLORE is property Set which searches the IExplorer on system and returns the path of IExplorer.exe.