Hi Everyone,
I am facing a difficulty and need your help. Here it is:
Using a administrator account I ran command Setup.exe /v"ALLUSERS=1" to install my product for all users, then I logged off and logged in as a normal user, I did see short cuts on the desktop. However, when I tried to run them, it asked me to find the temporary MSI to finish the install, and because this is a normal user account, I could not access administrator's directory where the temporary msi stays - c:\documents and settings\ABC\Local Settings\Temp. (Admin account is ABC)
I am using InstallShield to make my installer. Please help me how to do with this problem. Thank you very much!
0 Comments   [ + ] Show 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.

Answers

0
Hi,

Was this question answered? jus curious to know the soultion..
Answered 05/31/2010 by: t.brammavidhyambika
Yellow Belt

Please log in to comment
0
Does your application contains user data
Answered 05/31/2010 by: Hussi
Purple Belt

Please log in to comment
0
try using active setup if it works
Answered 05/31/2010 by: mayur_mak
Senior Purple Belt

Please log in to comment
0
Thank you mayur_mak. What is an active setup?
Answered 06/01/2010 by: sai21
Yellow Belt

Please log in to comment
0
Hit the search button here on app deploy and type: active setup. [8|]
Answered 06/01/2010 by: Rheuvel
Brown Belt

Please log in to comment
0
Extract the MSI from the EXE in the usual way to a universally-accessible location and use THAT to install.

And BTW, this forum is intended for posts concerning errors returned by the Windows Installer engine. Your post ought to have been made in the 'Package Development' forum. A moderator may move it there.
Answered 06/01/2010 by: VBScab
Red Belt

Please log in to comment
0
Really thank you for help. I solved this by using 1) cache msi to a public folder 2) using run-time path to execute msi
I wish oneday I could help you in return. [:D]
Answered 06/02/2010 by: sai21
Yellow Belt

Please log in to comment
0
It seems like you solved the problem behavior, not its cause. When using shortcuts to your application on other user accounts, the installer is requested because an on-demand installation is triggered. Basically, your package installs resources (usually registry entries) in per-user locations and those resources are not available to other user accounts. In this case Windows Installer automatically tries to install those resources for the current user to make sure that the installation is intact.

A better solution is to install these resources in per-machine locations from the start. Let me know if you need some debugging tips.
Answered 06/12/2010 by: john.pirvu
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity