I am trying to push out an msi using SCCM. The status reported successful, but for some reason it's not showing in the add/remove program or creates a shortcut on the desktop if I use SCCM to push it out. I look at the local drive and it looks like all the files are copied properly and registry enties are added correctly.

But if I manually run the same script after I've logon with my account which is part of local admin group then it's showing in the add/remove program.
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
Are you installing per machine or per user? If you are installing per user and installing with the system account via SCCM you will not see it because it is only installed for the system account.
Answered 04/24/2009 by: bigherrm
Senior Yellow Belt

Please log in to comment
0
I tried both ALLUSERS = 1 and ALLUSERS=2 on the msi command line property but getting the same result.

msiexec.exe /i "EDIS 4.2.msi" ALLUSERS=1 /m MSISPQJA /qn /l*v C:\medhost.log
msiexec.exe /i "EDIS 4.2.msi" ALLUSERS=2 /m MSISPQJA /qn /l*v C:\medhost.log
Answered 04/24/2009 by: darklord12
Senior Yellow Belt

Please log in to comment
0
I'll bet the log shows ALLUSERS being deleted...
Answered 04/27/2009 by: VBScab
Red Belt

Please log in to comment
0
In case of your package installation the ARPSYSTEMCOMPONENT property is set to 1,for this reason the Package installation would not show any ARP entry.

In order to View the ARP entry make ARPSYSTEMCOMPONENT=0 or remove this property from your MSI.
Answered 12/22/2009 by: sushantnarlawar
Yellow Belt

Please log in to comment
0
FYI

the value of the ARPSYSTEMCOMPONENT doesn't matter so you would need to remove it
Answered 12/22/2009 by: AngelD
Red Belt

Please log in to comment
0
Try installing it with your admin user, then logging in with a different user account. If it is in ARP for only your admin account, then it is most definitely a per user installation.
Answered 12/31/2009 by: elgwhoppo
Senior Purple Belt

Please log in to comment
0

I know it's been a while, but someone may come across this thread, just like I just did, searching for clues...

In my case it was the ARPNOMODIFY=1 set in the original MSI's Property table. The MSI installed per system, puts all the Installer and Uninstall entries in the registry where expected (all HKLM, not the User's) but still not showing in the "Change or Remove" list.

To fix this on the existing configuration, without removing and reinstalling anything, I first lookup the local cache file for the MSI, getting it from the registry here: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserDtat\S-5-18\Products\<flippedProductCodeGUID>\LocalPackage=C:Windows\Installer\<something>.MSI

(one can use the HKCR\Installer shortcut, too...)

 

then I go and edit that package with  ORCA, change the APRNOMODIFY to eual 0, save, then run repair against the very same locally cached MSI. Right after that it comes up showing on the list.

 

Answered 09/05/2012 by: jarekp
Senior Yellow Belt

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