MSI installing to the USER PROFILE
hi
I am still having problems with this app called info pak
I have been able get the app to install to the allusers profile using the set directory custom action [%ALLUSERPROFILE]\APP DATA\
but the app is still installing to the user profile
is there a way to rectify this or is the app written to install to the user profile
I am still having problems with this app called info pak
I have been able get the app to install to the allusers profile using the set directory custom action [%ALLUSERPROFILE]\APP DATA\
but the app is still installing to the user profile
is there a way to rectify this or is the app written to install to the user profile
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
AngelD
17 years ago
Posted by:
cygan
17 years ago
Posted by:
AngelD
17 years ago
Posted by:
KalleBaah
17 years ago
Posted by:
nheim
17 years ago
Hi Kalle,
your post is definitely wrong. A new user profile is not built from the "All Users" profile, but from "Default User" profile. There is no such thing, as the "All Users" profile at all!
However, the "All Users" folder in the profile folder takes files and settings which belong to all users on a machine. If there are files and/or settings which belong to the "Users Profile" the author of a setup package has to take special considarations to get this stuff into each profile. There a two main ways to this: MSI self healing or Active Setup.
But if an app is installing stuff to the users profile without awareness of the rules, its mostlikely working in the profile (with admin rights), which the app was installed, but in every other profile, MSI self healing is kicking in but can't succeed because of the lack of the necessary rights to do it.
AngelD has qestioned cygan exactly about the behaviour the app does around this.
Regards, Nick
your post is definitely wrong. A new user profile is not built from the "All Users" profile, but from "Default User" profile. There is no such thing, as the "All Users" profile at all!
However, the "All Users" folder in the profile folder takes files and settings which belong to all users on a machine. If there are files and/or settings which belong to the "Users Profile" the author of a setup package has to take special considarations to get this stuff into each profile. There a two main ways to this: MSI self healing or Active Setup.
But if an app is installing stuff to the users profile without awareness of the rules, its mostlikely working in the profile (with admin rights), which the app was installed, but in every other profile, MSI self healing is kicking in but can't succeed because of the lack of the necessary rights to do it.
AngelD has qestioned cygan exactly about the behaviour the app does around this.
Regards, Nick
Posted by:
mvpackager
17 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.