I have an app (oracle's jinitiator) that includes a setting file that needs to be placed in each user's profile. How do a make this file install to each user's profile?

I'm sure this is basic stuff none the less I don't know how to do this. Thanks in advance.
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


What I've done in the past is just script something that would find the subfolders of the profiles folder (variable), remove the ones we know are "garbage" (SMS Service Account, Altiris Account, etc), and then copy into the other folders.

However, I read this recently which will probably change my ways in the future:

Read it, and check out the link in Madswami's post.

Hope this helps!
Answered 03/07/2006 by: usachrisk
Purple Belt

Please log in to comment
If you can't get the application to self-heal when the user starts it, then Active Setup is a good option.
Answered 03/07/2006 by: sikkert
Orange Senior Belt

Please log in to comment
I'm going to try Active Setup. Sounds like a good piece of knowledge for the ol' toolkit.
Answered 03/08/2006 by: desktop
Senior Yellow Belt

Please log in to comment
To solve the issue, get the package repaired for every user who logs in for the first time.
for this you need to add active setup registry in your application package.
First you need to copy the file in current users porfile and then active setup will copy it for all users porfile.

Files getting installed to My Documents actually go to personal folder in the ISM\MSI.

here is the process to configure active setup:-

It basically compares these two registry entries:-
HKLM\Software\Microsoft\Active Setup\Installed Components\{ProductCode}
HKCU\Software\Microsoft\Active Setup\Installed Components\{ProductCode}

If HKCU registry is not present it the application will execute the command written in the value of "StubPath". In StubPath we can make the MSI to run in repair mode for that user.

for this you need to add two registries in your package as following:-

HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\{ProductCode}

At this key you need to add two values "Version" and "StubPath"
Value for the "Version" should be less than version of your product version and
Value for "StubPath" should be "msiexec /fomus {ProductCode} /qn

So whenever the new user logs in it will check for the registry in HKCU and if the value is not present or the version is less than what is mentioned in HKLM it will run the MSI in repair mode to make the settings which are user specific. MSI in repair mode is being executed by the command in "StubPath".

Hope this works in your case......
Answered 03/16/2006 by: sidverma
Senior Yellow Belt

Please log in to comment