Software Deployment

Use the FileMon & RegMon freeware utilities (google 'em) and run the app as a standard user until you know you hit the security issue. Then sift through the pile of data you've accumulated to find the ACCESS DENIED. Note that sometimes ACCESS DENIEDs and FILE NOT FOUNDs are normal & acceptable, look at what happens before & after to insure that this is what is blocking the app from running. Give the User group access to the file or registry key where access was denied and write down what access you've provided. Then repeat until you've gotten past all the roadblocks. It can be tedious, but it works.

Use SetAcl utility (again, google it) in a custom action to set security according to the list you've made. Put that right before InstallFinalize in Execute Deferred MSI Script.

I found in Event Viewer something like this: "Detection of product '{7F4C8163-F259-49A0-A018-2857A90578BC}', feature 'ReleaseContainer', component '{9271C24E-8F22-4D2A-94C4-F71462F07F72}' failed. The resource 'HKEY_CURRENT_USER\Software\test\test' does not exist." I tried find solution with FileMon & RegMon but without results:(

Have you repackaged indesign or transformed their msi?

if' you've transformed the msi, that means a custom action looking for admin priv's is running and causing you grief during healing. generate a log file and you should be able to identify the action that's causing you grief.

Adobe's CS2 MSI's are not set up to cope very well with current user stuff, so I have reverted to Active Setup for all HKCU stuff.

if you have repackaged indesign cs2, then also go the log file option, and double check that the component identified in event viewer only contains current user stuff.