Current User keys and user profiles in MSI Installation
Hi All
During manual MSI Installation, WriteRegistryValues Action writes the registry values in the registry. As far as I know, deferred execution Standard actions run in System context. But I observed, HKCU registry keys are getting written in Currently Logged on User (HKCU) instead of HKU\.Default (System account). The same is for files (user profiles).
Please explain me the phenomenon while writing registry values/user profiles in current user.
During manual MSI Installation, WriteRegistryValues Action writes the registry values in the registry. As far as I know, deferred execution Standard actions run in System context. But I observed, HKCU registry keys are getting written in Currently Logged on User (HKCU) instead of HKU\.Default (System account). The same is for files (user profiles).
Please explain me the phenomenon while writing registry values/user profiles in current user.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
Kazakh
12 years ago
Hi raj-regul,
This is the default behaviour of Windows Installer.
All the profileinformation is written to the profile of the logged on user, this is why you normally get the installation progress bar when you first launch an application like Word with a user other than the one who installed it on the machine.
To counter this a lot of packagers trigger the self-healing part silently using the run/runonce key or the activesetup mechanism.
I advise you to read up on the subject and google for "Windows Installer self healing" to get all the technical information about it.
This is the default behaviour of Windows Installer.
All the profileinformation is written to the profile of the logged on user, this is why you normally get the installation progress bar when you first launch an application like Word with a user other than the one who installed it on the machine.
To counter this a lot of packagers trigger the self-healing part silently using the run/runonce key or the activesetup mechanism.
I advise you to read up on the subject and google for "Windows Installer self healing" to get all the technical information about it.
Posted by:
pjgeutjens
12 years ago
To counter this a lot of packagers trigger the self-healing part silently using the run/runonce key or the activesetup mechanism
I have to disagree with this statement. To me Self-Healing is still the best choice. Only if for some reason it is not available do I resort to ActiveSetup. The Run/RunOnce keys are a (distant) third option for propagating user settings imo.
Of course I am only one packager, not a lot of em, so feel free to disagree :)
PJ
Posted by:
Kazakh
12 years ago
pj,
That is why I said MOST packagers ;)
Everything depends on the requirements of the client.
Most of my clients don't like that repair window and want to get rid of it, so using activesetup is the standard choice with most of my customers.
Offcourse if you really want the native functionality, best is to use the advertised shortcuts.
btw, using activesetup does not mean you're not using the self-healing, basically you put the msiexec /fu... command inside it, which triggers the self-repair.
That is why I said MOST packagers ;)
Everything depends on the requirements of the client.
Most of my clients don't like that repair window and want to get rid of it, so using activesetup is the standard choice with most of my customers.
Offcourse if you really want the native functionality, best is to use the advertised shortcuts.
btw, using activesetup does not mean you're not using the self-healing, basically you put the msiexec /fu... command inside it, which triggers the self-repair.
Posted by:
anonymous_9363
12 years ago
Posted by:
Kazakh
12 years ago
Posted by:
anonymous_9363
12 years ago
Posted by:
Kazakh
12 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.