We developped the CS3 package by using the documentation on the adobe site. When we are starting the batch file, it is working correctly.
However, if we are deploying it on our field computers, we are not getting reliable result.

1. Sometimes it might work.
2. Sometime it is just failing.
3. If we uninstal CS2 to install CS3 then we get a fail.
4. If we reinstall the computer then deploy CS3 then usually it is working.

We worked a lot on these problem and found nothing in the logs. We even opened a case to Adobe and when they saw we were using a batch file we got " it is unsupported" lol.

I would need reading CS3 story and understand your experiences, problems, solutions. What should I take care of?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Adobe CS3 is flunky. I re-packaged CS3 into a more "real world" MSI. The Adobe installer is poo.
A couple of things to look out for are the cache.db file and AUM. The cache.db holds the registration info, but it lives in %progfiles%\common\Adobe, so if you include it in your package, it could overwrite other Adobe product registration info.
A file called application.xml.override can be used to supress EULA and updates.
Answered 02/22/2009 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
Could possibly be that during the install the user has IE or office open, or their screen resolution.
Answered 02/23/2009 by: brianb0177
Senior Yellow Belt

Please log in to comment
0
Good point. It also requires at least 500mb of ram for the install to run, it checks.
Answered 02/23/2009 by: reds4eva
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity