Software Deployment

We had a bit similar problem with PS 7 and the reason was that when users started the app it wanted to write several things to classes_root. We went under the fence and gave rights there on MSI.

How did you do that?

Guess you mean you took a snapshot of the installation to create your MSI?

If so - make sure you run the application once and close it again and as part of your snapshot. Apps often write additional registry keys / files upon first run.. If you don't include them in your snapshot and are in a locked down environment you'd get some strange results.

Regards,
Rob.

I would also suggest running your regular snapshot, then recording the changes, and take a new snapshot of the initial run of the program, that way you could export those registry settings and add them to the other MSI as advertised information.

Not sure this will be useful, but might be worth checking?

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

Thank you Guys i am trying to do what you have Guys provided me and i will let you know the results.

Thanks

Hey Rob i have tried your suggestion but that did not resolve the issue.

Thanks
mali

Sorry to hear that - it would have been a nice easy fix!

Have you validated your package for ICE errors?
Checked for references to usernames / machine accounts in files and registry keys?
Run regmon / filemon?
Checked your install against the vendor install for obvious differences?
..etc etc

These are just suggestions for trying to find out where the problem is - there is no easy answer unless someone else reading this thread has had the same error and fixed it [;)] Better get your detective hat on!

Good luck,
Rob.

I reallly had a hell packaging Adobe Creative Suite.. I used the information here, with a few modifications: http://itninja.com/question/adobe-creative-suite-install-automation

First i installed the Suite on a clean computer. After each component started i took the abcpy.ini-file and saved it.

I made a pre-install-package, containing the Adobe Creative InstallShiled Installation Product folder and the abcpy.ini-files i took from the installation.

Then i used the SuiteInstaller.log to see the parameters each component was started with. I maked the installation silent that way.

At last i made a post-install-packages. I used the SuiteInstaller.log to see where the installation put the suites.sif for each application. That file needs to be replaced. If it isn´t replaced a error message saying that the user information is wrong/corrupt.
In the case with Photoshop CS, I also had to add the registry-information from the uninstall-string.

Good luck!

/Jonas

To change premissions in the registy you can use a build-in Windows Tool called: Regini (located in the System32 directory). If you need more information go to the Microsoft support site: [link]http://support.microsoft.com/?kbid=245031[/link]

Regards,
Rob van het Bolscher.

 

Go into the settings folder for whichever program your trying to launch in your Users/Library/Prefs. and pull a copy out and onto your Desktop (in case you need to rescue items from it later).

Then trash the contents of the original folder; empty the Trash; reboot and then see if the application will start up!