HKCU avail for all users.
I am creating a deployment package for MS Live Meeting Add-in. I need to have all preferences preconfigured for each user that logs onto the machine (Organization name, Intranet Portal address). The information used to retain this info resides in a HKCU key. What I though would work for this is to create a key in HKLM\Software\Microsoft\Active Setup\Installed Components\(Product ID of .msi file)\StubPath (msiexec /fauvs {ProductCode} /qb). This is supposed to allow the package to run a repair which then will put in all of the HKCU info. After running the installation I log in as a different user. The .msi runs a repair, the HKCU values are there all is well. I then log in again as a different user and the HKCU values are not there. So only one user (aside from the account that ran the installation) is receiving the HKCU keys. Is there anyone that is familiar with this process that can assist me? I'm not certain what else it will take to get this to work. Thank you.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
peska
17 years ago
Hi,
If you look at the Component containing the preferences preconfigured for each user,
make sure it has: Key Path Type = Registry Key Path
And that a value under HKCU\xxx\xxx\xx is "set as Key" for this component.
peska
If you look at the Component containing the preferences preconfigured for each user,
make sure it has: Key Path Type = Registry Key Path
And that a value under HKCU\xxx\xxx\xx is "set as Key" for this component.
peska
Posted by:
MSIPackager
17 years ago
If it's not repairing for users it's because HKCU\Software\Microsoft\Active Setup\Installed Components\(Product ID of .msi file) already exists in their profile.
If you want to ensure that it kicks off a self repair then also add a Version value to HKLM\Software\Microsoft\Active Setup\Installed Components\(Product ID of .msi file)
This will compare the 2 values and if the version number doesn't exist (or is less) under HKCU then the StubPath comand will be executed.
Note if you want to use versioning other than 1 / 2 / 3 then you need to seperate the subversions with commas and not full stops - e.g. 1,1 / 1,2 / 1,2,1 etc
Active setup in a nutshell here.
Hope it helps,
Rob.
If you want to ensure that it kicks off a self repair then also add a Version value to HKLM\Software\Microsoft\Active Setup\Installed Components\(Product ID of .msi file)
This will compare the 2 values and if the version number doesn't exist (or is less) under HKCU then the StubPath comand will be executed.
Note if you want to use versioning other than 1 / 2 / 3 then you need to seperate the subversions with commas and not full stops - e.g. 1,1 / 1,2 / 1,2,1 etc
Active setup in a nutshell here.
Hope it helps,
Rob.
Posted by:
danr29
17 years ago
Is there maybe an easier way to do this, like creating an advertised entry point that places the HKCU values in the registry when the user clicks on the executable to begin the application at first use? I did read the artilce you suggested before and I took the approach to just use the existing msi file and not create a separate Active Setup exe. The version value is only used when an active setup exe is created, right?
Posted by:
MSIPackager
17 years ago
Yes, this is what peska already suggested and is the best way to do it, however it depends on the user running and entry point (e.g. shortcut or file extension) to invoke a self repair and write the HKCU keys you want.
Active setup is a method you can use to run a program (weather is an msiexec command or whatever) automatically at logon, without the user needing to run the app.
The version value can be used to ensure that the program in the stubpath is run - not sure what you mean by "The version value is only used when an active setup exe is created, right?"
Regards,
Rob.
Active setup is a method you can use to run a program (weather is an msiexec command or whatever) automatically at logon, without the user needing to run the app.
The version value can be used to ensure that the program in the stubpath is run - not sure what you mean by "The version value is only used when an active setup exe is created, right?"
Regards,
Rob.
Posted by:
danr29
17 years ago
Sorry for the confusion. What I meant was that when reading the article pertaining to active setup, it looked like when using the existing .msi for active setup you don't use the version value. So I do need to include the version value when doing active setup from an .msi file?
Posted by:
turbokitty
17 years ago
danr29, I deployed that app last month. I created an MST with the HKCU info and let the advertised shortcut repair it. Worked for me... until I put it in Radia (but that's another story).
Posted by:
danr29
17 years ago
turbokitty, which shortcut did you advertise? Did you just enter in the registry info for the destination machine and that worked for you? Or did you have to go in and create a component with the HKCU values that point to the specific shortcut? Can you provide me with a little more info on how you got this to work? Thanks.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.