[font="times new roman"]Msi package self heals, if it is having hkcu or application data entries, and after healing it gets it. If we keep hklm and hkcu in the same component, 1st thing we will get ice error, then still if we continue with it, everytime at the selfheal, it will heal hklm entries unnecessarily. What are the other disadvantages?
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


Mixing per-user and per-machine data in the same component could result in only partial installation of the component for some users in a multi-user environment. For example, after the installation for everyone on the same machine, a new user may not be able to get per-user data due to the poor design of components. This can lead to application run-time problems.
Answered 08/04/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
Normally users do not have permissions to make changes in HKLM. If u keep both registries in same component, then at the time of repair, it will unnecessarily go to repair HKLM entries, and if it does not have access in HKLM, it will through an error.
Answered 08/04/2009 by: abking99
Second Degree Blue Belt

Please log in to comment