Disadvantages of keeping HKLM and HKCU entries in the same component

[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   [ + ] Show comments

Answers (2)

Posted by: cygan 13 years ago
Fifth Degree Brown Belt
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.
Posted by: abking99 13 years ago
Second Degree Blue Belt
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ