/bundles/itninjaweb/img/Breadcrumb_cap_w.png
I've tried for a long time to solve this problem. So I hope someone can point me in the right direction..

This installation is an addon package, MSI based. Running this manually with msiexec.exe works fine. When I run the installation silent w/propertie settings (as descriped in the program documentation), the program installs only for the user. Meaning; If another user log on, you will not see the program as an addon or in the Add/remove Prog.
I've checked registry and the manual install, installs program registry in LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer
However, running the silent installation, the program spesific registry ends in CURRENT_USER\Software\Microsoft\Installer

Any idea anyone? Thanks in advance..
0 Comments   [ - ] Hide Comments

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

Answers

0
What is it an addon for?
Set the ALLUSERS property with a value of 1 to install it as per-machine.
Make sure that you have an entrypoint that can trigger a repair for user related resources such as HKCU and files located in the user's profile.
Answered 06/09/2008 by: AngelD
Red Belt

Please log in to comment
0
It works! Thanks a lot..
It's an addon SW for a program called Solid Edge.

By the way, is it normal for a program installation to behave in this way?
Answered 06/11/2008 by: Ladort
Senior Yellow Belt

Please log in to comment
0
As for Per-Machine and Per-User; yes.
Answered 06/11/2008 by: AngelD
Red Belt

Please log in to comment
0
Yes, but I was thinking more in direction; Is it normal that you have to add this property

I've installed hundreds of MSI installations in my business. Never have I had this problem.

Thanks for all help..
Answered 06/13/2008 by: Ladort
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: Ladort
Yes, but I was thinking more in direction; Is it normal that you have to add this property

Depends what deployment solution you're using.

For AD/GPO this will be done automatically
For manual install you need to handle the ALLUSERS property. If the property does not exist the installation will be forced as per-user.

For the behaviour of the ALLUSERS property have a look at http://msdn.microsoft.com/en-us/library/aa367559(VS.85).aspx

I've installed hundreds of MSI installations in my business. Never have I had this problem.
It's all about how the author designs the package.
Answered 06/13/2008 by: AngelD
Red Belt

Please log in to comment
0
Exelent! Thank you for all help and guidance.
Answered 06/16/2008 by: Ladort
Senior Yellow Belt

Please log in to comment