I am working with a Corporate version of Photoshop CS2. In looking at the source files, I find one "main" msi, but also four sub-folders which each have their own msi. Those are Adobe Bridge, Common Files, Help Center and Stock Photography. In looking at the "main" msi, there is a custom action "CA_InstallFinishDisplay" that has a function name of "PerformSubInstalls" which points to a DLL which I can only assume launches the four sub-msi's. I have yet to get the "main" MSI to install all of the pieces - the main msi as well as its four sub-msi's. Has anyone run across this before and if so, what did you do to resolve?
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
created a transform, works like a charm ;-)
Answered 02/27/2006 by: Bartesque
Orange Senior Belt

Please log in to comment
0
We use SMS2003 for Deplyment and all MSI's are installed using the SYSTEM account (windows 2000 OS). We have an inhouse developed tool which will mimic a SYSTEM install in the Admin context when used. When I first started out, I was getting 4 of the 5 msi's installed, with the "commonfilesinstaller" being the only one that didn't work with /qb. When I created a Transform installing with /qb and when installing with or without the tool, I then only had success with the main msi, the other four were not even kicked off. I found a post here by nheim @ http://itninja.com/question/service112&mpage=1㬈 which suggested using /qn. With the transform, /qn and the tool, I am now back where I started, with only the "CommonFilesInstaller" piece not kicking in.

Any more help/insight/feedback is appreciated!
Answered 02/27/2006 by: DesktopEngineer
Yellow Belt

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