Hi, I am hitting my head against a wall and need any tips you guys have...

We captured Oracle's Application Desktop Integrator 7.1.26 into a MSI. That MSI works perfectly on Win2k. But now we are migrating to WinXP so have to retest/repackage this MSI.

After numerous recaptures, and reinstalls, I can't get ADI to launch as a regular user for the first time after install. If an administrator launches ADI, it opens fine, and then opens fine for any further users. It is just the initial launch that is a problem. Since we use Active Directory to deploy apps in our shop, this administrator problem is indeed a problem.

Here are some things I have done:
1) Captured the install of ADI and then also the initial launching of it as administrator. I figured if the initial launch registers dll's and such, Wise studio would detect it. But still have the same problem with this MSI as a regular user.
2) Ensured the regular user does have full write access to the folders and reg keys specified in ADI's install docs, but same problem I even tried to give full read/write access to every folder and sub folder on C:\ and every HKEY in the registery but same problem!!
3) If the user is added to a Power USers group, ADI does launch fine. But this is still not suitable in our shop.
4) From the local group policy editor, I gave the local Users group, access to every security role. Still the same problem!!!
5) I do have a bug report filed in with Oracle, but that may take a while for them to find a problem......
6) Ran a dependency checker, filemon, and regmon, to watch what happens when user and admin launch the app.. Nothing usefull found.

Since I gave the user full access to every folder and registry key, I don't beleive it is as simple as a file-system security issue (locked down too tight). But what else could it be? What else can I try?

Any ideas would be very appreciative.

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I'm sorry that I can't help you really.
I just wanted to let you know, that we've had the same problem with lots of applications during the test phase before migrating to WinXP. That's why we decided to "upgrade" the users to Power users. This solved lots of those problems...
Answered 02/06/2006 by: rpfenninger
Second Degree Green Belt

Please log in to comment
ditto. i've had the same probelm with the odd app.

you could always try changing things in group policy as it might be a permission at that level that's screwing with it.

our solution was to temporarily (for like a day for instance) elevate the user's rights when pushing it out.

what tool are you using? Using Wise instead of Installshield or vice versa for the repack might make a difference. Demo versions of both are available.
Answered 02/06/2006 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
I am using Wise studio 7.0 to package. I have created another MSI that will give Power Users access to all domain users, and then from the RunOnce key, remove the PowerUser access, and autolaunch ADI this one time. Then ADI should launch properly no matter when the computer receives the push.

I wish there were more tools available for this type of troubleshooting. FileMon and RegMon from sysinternals won't run as restricted user so not much good.

Thanks for your ideas though.
Answered 02/06/2006 by: radeon7500
Senior Yellow Belt

Please log in to comment