Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > msi setup issues
 

msi setup issues

I havecouple ofissues with the msi setup that I created for my application. We are also using SMS to push the msi package to all the machines. If I install manually using windows add/remove then it works fine.

Here are the details
1. The msi package is created using VS 2005 with install option for Everyone.
2. We have found that for some users it installs with just for me option as opposed to for every one when pushed through SMS.
3. As a result of 2 I am looking for ways to uninstall the product that got installed with just for me. Our users don't have admin rights for their machines.

Thanks
  • Moved byYiChun ChenMSFTFriday, July 24, 2009 7:18 AMDeployment issue (From:.NET Framework Setup)
  •  
SanChips  Wednesday, July 22, 2009 3:14 PM
Part of this may be the way VS setups work, which I don't thinkis deterministic enough. The MSI file is built with an ALLUSERS property value of 2, which means "do an Everyone install if the user is privileged, otherwise fall back to a Just me install". This might be having an effect.

So I think if you are doing the "assign to machine" install (if I remember thatexpression correctly) then SMS will try to do a per-machine Everyone install, but itwill fall back to per-user if you haven't set up the environmentformanaged installs. That's related to the AlwaysInstallElevated setting here:
http://msdn.microsoft.com/en-us/library/aa369784(VS.85).aspx
that a non-administrator can't set, but Group Policy can.


Phil Wilson
PhilWilson  Friday, July 24, 2009 10:31 PM
Hi SanChips,

I am moving this thread from Base ".NET FrameworkSetup" forum to the "ClickOnce and Setup & Deployment Projects" forum, since the issue is related to deployment. There are more deployment experts in the "ClickOnce and Setup & Deployment Projects" forum.

Thanks
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
YiChun Chen  Friday, July 24, 2009 7:18 AM
Part of this may be the way VS setups work, which I don't thinkis deterministic enough. The MSI file is built with an ALLUSERS property value of 2, which means "do an Everyone install if the user is privileged, otherwise fall back to a Just me install". This might be having an effect.

So I think if you are doing the "assign to machine" install (if I remember thatexpression correctly) then SMS will try to do a per-machine Everyone install, but itwill fall back to per-user if you haven't set up the environmentformanaged installs. That's related to the AlwaysInstallElevated setting here:
http://msdn.microsoft.com/en-us/library/aa369784(VS.85).aspx
that a non-administrator can't set, but Group Policy can.


Phil Wilson
PhilWilson  Friday, July 24, 2009 10:31 PM

You can use google to search for other answers

Custom Search

More Threads

• Is there a group for Composite UI Blocks?
• MSI installation via SMS that uninstalls previous versions
• COM depoyment in ClickOnce
• C# custom setup
• Declare statement securityException
• Problem adding files to deployment project.
• How to get values from canned setup dialogs - and what to do with them?
• Setup Project + Access the App.config
• Newbie with deployment projects, having a problem with VB2005
• Error 1001. Item has already been added. Key in dictionary: