You can add ALLUSERS=1 to the commandline you are using to install to make it a per machine installation.
Commandline should look something like this Msiexec.exe /I whatever.msi ALLUSERS=1 /qb-! Jimmy Martin (901) 227-8209 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Beardsley, James Sent: Monday, February 24, 2014 8:49 AM To: mssms@lists.myitforum.com Subject: [mssms] SCCM/Windows Installer issue This is kind of off-topic but I hope there are some Windows Installer experts out there that may have some ideas. We started pushing QuickBooks (all versions) to users using AD groups about 3 weeks ago. Since then, we've had 5 or 6 instances (out of maybe 25-30 installs) where after its installed, it gives the user an error when they try and open it. It starts to open and then they'll see the Windows Installer come up similar to when its trying to repair something and then within a few seconds, they get an error that states "ALLUSERS property is not 1 - this MSM cannot be used in a per-user or fallback to per-user install". We can't uninstall it from Add/Remove once that happens. The only way to get it off the machine is with something like Revo or by using Windows Installer Cleanup. Then once its actually off the machine, reinstalling doesn't help. The only fix (according to Intuit) is to rebuild the users Windows profile... not fun! This may not be SCCM related at all but since we never had this problem in SCCM 2007 when pushing to machines, I have to think it is something related to the way we're pushing the application to the user. I have it configured to install as user (like in 2007) and I'm using the same command line as in 2007. But since we're targeting users instead of machines, maybe it's installing it differently. I am going to check with Intuit to see if I need to add the ALLUSERS property to the command line, maybe that'll help. But since they don't support installing it by .msi, I doubt they'll offer any advice. Does anyone have any ideas as to what that error means? I've never heard the term MSM so I was hoping there are some Windows Installer specialists out there that have an idea what that is referencing and maybe lead me down the right path to figuring out the root cause. I'm trying to avoid having to go back to pushing to machines. Pushing to users is so convenient. Thanks, James ________________________________ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
