If a new user runs an installed per machine installed application that needs to repair JUST for some HKCU keys can it repair without needing the source (in my circumstnace on a network which may not be available)?

I know it CAN but have difficulty getting this to work on some packages. Are there any more tips and tricks or points you think I may be missing? - my general approach is below:

Typically, I put the HKCU settings in their own component in a sub feature of the root parent feature of the package. The sub feature typically contains one other component which has the advertised shortcut entry point, an exe and maybe a few HKLM keys relating to the exe. Assuming the rest of the package is good, when a 2nd user runs the app with it already installed, my theory is only the HKCU component keypath will be bad and only the subfeature will repair. If this sub-feature only has a file and HKLM keys which are already present, only the HKCU keys are missing - hence these can come from the cached MSI not require the source from the network.

Like I say I have some packages that I can repair to get the HKCU keys while disconnected from the network, yet others I cannot reproduce this on!
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



As far as I know do you need access to the package where you have installed it from.

Maybe one of these "hacks" will help you:

1. Copy the package to a local folder and install it there from instead.

2. Make some kind of login-script that "repairs" the package using a .reg-file or maybe a KIX-script.

Answered 10/21/2005 by: jonasm
Blue Belt

Please log in to comment
Just look there and your question should be answered:
Answered 10/21/2005 by: sini
Orange Senior Belt

Please log in to comment
Thanks Sini.

If I read and understand that post correctly, my above theory that it can be done is correct and I must have a broken keypath in a component in my parent feature to blame...........
Answered 10/23/2005 by: GB1
Orange Belt

Please log in to comment
Answered 10/24/2005 by: sini
Orange Senior Belt

Please log in to comment