per-user/per-machine MSI installation
Hello.
I have created a MSI package (Adobe Framemaker 7 to be exact).
ALLUSERS property is set to 1
When I'm installing it while logged on as user with local admin privilages to the system, it installs per-machine and all works well (which is how I want it).
However, when I'm installing it while logged on as normal user (I set elevated rights in registry), it installs in per-user mode.
Note: I do set alwaysinstallelevated to 1 in two places in registry.
Now, as I understand ALLUSERS=1 it should either install in per-machine or not install at all and exit with error (compaining at lack of rights).
I have to have that package installed per-machine. What are other ways to FORCE MSI to install in per-machine ? Per-user installation is no good for me.
I cant find any information that would confirm of deny my theory, which is that normal user with elevated rights can install app only in per-user mode, not per-machine. If anyone had any comments about that I would appreciate aswell.
Thanks in advance.
Mops.
I have created a MSI package (Adobe Framemaker 7 to be exact).
ALLUSERS property is set to 1
When I'm installing it while logged on as user with local admin privilages to the system, it installs per-machine and all works well (which is how I want it).
However, when I'm installing it while logged on as normal user (I set elevated rights in registry), it installs in per-user mode.
Note: I do set alwaysinstallelevated to 1 in two places in registry.
Now, as I understand ALLUSERS=1 it should either install in per-machine or not install at all and exit with error (compaining at lack of rights).
I have to have that package installed per-machine. What are other ways to FORCE MSI to install in per-machine ? Per-user installation is no good for me.
I cant find any information that would confirm of deny my theory, which is that normal user with elevated rights can install app only in per-user mode, not per-machine. If anyone had any comments about that I would appreciate aswell.
Thanks in advance.
Mops.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
wiseapp
18 years ago
Hi Mops:
ALLUSERS=1 will perform the per-user installation only if the user has local admin that's y the installation is installing the product however if you change this value to 2 that is ALLUSERS=2 then it would do a per-machine installation despite of the user rights it will install the software. Try this and let me know.
ALLUSERS=1 will perform the per-user installation only if the user has local admin that's y the installation is installing the product however if you change this value to 2 that is ALLUSERS=2 then it would do a per-machine installation despite of the user rights it will install the software. Try this and let me know.
Posted by:
VikingLoki
18 years ago
You have it mixed up, Wiseapp. (I always confuse this one myself so I have it bookmarked.)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/allusers.asp
ALLUSERS = "" : Per user install, always.
ALLUSERS = 1 : Per machine for Admins, not installable by users (never per user)
ALLUSERS = 2 : Per machine for Admins, Per User for users.
Looks like mops has it right. That SHOULD work the way he wants it, but it's not.
Hmmm... Is this a captured MSI or are you transforming a vendor MSI? If you're transforming, you need to watch out for custom actions that will override the initial value of ALLUSERS. Especially Adobe, they make really funny installs. Search your tables for ALLUSERS and see if it shows up un any unexpected places that could be resetting the initial value.
Another approach is to create a log file (add /L*V "[filename]" to the MSIEXEC command line) and search through it for any ALLUSERS, Per machine / user entries. That will also give you a clue as to what's happening.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/allusers.asp
ALLUSERS = "" : Per user install, always.
ALLUSERS = 1 : Per machine for Admins, not installable by users (never per user)
ALLUSERS = 2 : Per machine for Admins, Per User for users.
Looks like mops has it right. That SHOULD work the way he wants it, but it's not.
Hmmm... Is this a captured MSI or are you transforming a vendor MSI? If you're transforming, you need to watch out for custom actions that will override the initial value of ALLUSERS. Especially Adobe, they make really funny installs. Search your tables for ALLUSERS and see if it shows up un any unexpected places that could be resetting the initial value.
Another approach is to create a log file (add /L*V "[filename]" to the MSIEXEC command line) and search through it for any ALLUSERS, Per machine / user entries. That will also give you a clue as to what's happening.
Posted by:
mops81
18 years ago
Hello.
I have worked out the problem.
BTW, it was an install capature created MSI by wise installer studio.
Using orca, I reviewed Property table, and noticed the following properties:
MACHINEELEVATED
USERELEVATED
They were both set to 0, i could not find any documentation on what they do, but once I changed them to 1 it all installed and worked as expected.
Thanks for input guys.
I have worked out the problem.
BTW, it was an install capature created MSI by wise installer studio.
Using orca, I reviewed Property table, and noticed the following properties:
MACHINEELEVATED
USERELEVATED
They were both set to 0, i could not find any documentation on what they do, but once I changed them to 1 it all installed and worked as expected.
Thanks for input guys.
Posted by:
VikingLoki
18 years ago
What version of Wise mops? I've never seen those properties before. Strange.
Posted by:
VikingLoki
18 years ago
I'm puzzled mops.
There is no mention of those properties in the Wise KB, doesn't even Google. I'm using 5.6 and they're not in my captures. (I was worried that I might be publishing user installable packages!) I have no idea how those properties could have ended up in your capture. Very strange.
There is no mention of those properties in the Wise KB, doesn't even Google. I'm using 5.6 and they're not in my captures. (I was worried that I might be publishing user installable packages!) I have no idea how those properties could have ended up in your capture. Very strange.
Posted by:
wiseapp
18 years ago
Hi Viking,
I'm sorry I keep on forgetting this ALLUSER property , anyhow I agree with you for this new property MACHINEELEVATED or USERELEVATED never heard about the same. This seems to be custom created property what do you say Viking?
I'm sorry I keep on forgetting this ALLUSER property , anyhow I agree with you for this new property MACHINEELEVATED or USERELEVATED never heard about the same. This seems to be custom created property what do you say Viking?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.