Machine and User Keys

can you please tell me why we should not keep machine and user related keys in the same component?
As per microsoft component rule, if we keep it in the same component it throws ICE error. But can you tell me what is the exact reason of not keeping it?Even if we keep it, the app will install and do the fucntionality fine

0 Comments   [ + ] Show comments

Answers (1)

Posted by: pjgeutjens 13 years ago
Red Belt
the reason for this is that, when you do a per-machine install, user keys typically get set using SelfHealing functionality. They get set in every user's specific environment when they first start up the application. It's no use rewriting machine level setting every time at this point.
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