Application not appearing in Add/Remove Programs
Hello all,
I saw a post very similar to the problem I'm experiencing:
http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning7537&mpage=1&key=릱
The final entry on this post is from VBScab who states that the log will probably show "ALLUSERS" being deleted - this is exactly the case with the application I'm working with.
If executed as the logged on (adminstrator) user the log does not contain the "ALLUSERS = Deleted" entry and the app happily appears in ARP
If executed by SCCM (local system account) then there is no entry in ARP...as I guess the app has been installed for this user only.
My question is how can this problem be remedied?
I've tried creating a response transform with install for "Everyone" selected and have specified "ALLUSERS = 1" on the command line SCCM is using but still no joy.
Any help would be appreciated...at the moment I'm getting msiexec to generate insulting logfile names just to amuse myself....
Thanks
Mos
I saw a post very similar to the problem I'm experiencing:
http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning7537&mpage=1&key=릱
The final entry on this post is from VBScab who states that the log will probably show "ALLUSERS" being deleted - this is exactly the case with the application I'm working with.
If executed as the logged on (adminstrator) user the log does not contain the "ALLUSERS = Deleted" entry and the app happily appears in ARP
If executed by SCCM (local system account) then there is no entry in ARP...as I guess the app has been installed for this user only.
My question is how can this problem be remedied?
I've tried creating a response transform with install for "Everyone" selected and have specified "ALLUSERS = 1" on the command line SCCM is using but still no joy.
Any help would be appreciated...at the moment I'm getting msiexec to generate insulting logfile names just to amuse myself....
Thanks
Mos
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Posted by:
mosquat
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
mosquat
14 years ago
Posted by:
mosquat
14 years ago
Even setting this property doesn't force anything to show up in ARP, the log file indicates a property change though.
Some new info - when I have installed the app using SCCM (and nothing appears in ARP) if I then install the application interactively (for "Everyone") it behaves as if the product is not installed - i.e I get no "Remove/repair" screen.
I do have a dirty workaround which involves importing the necessary registry entries but of course would rather the MSI did what it's supposed to do!
Some new info - when I have installed the app using SCCM (and nothing appears in ARP) if I then install the application interactively (for "Everyone") it behaves as if the product is not installed - i.e I get no "Remove/repair" screen.
I do have a dirty workaround which involves importing the necessary registry entries but of course would rather the MSI did what it's supposed to do!
Posted by:
mosquat
14 years ago
OK I guess this is a problem that isn't so easy to fix, just to help others I will post my workaround which is offered "as is" and I hope that it wont need to be used in many cases as it is filthsome:
Install product interactively (so that an entry in ARP is created)
Open regedit
Navigate to HKEY_CLASSES_ROOT\Installer\Products\
Sift throught the many installed products to find the one you just installed
Export the reg key to a file
Create an installation script so that after the product is installed via SMS/SCCM the reg key is then imported
Check ARP for the relevant entry
Using the "uninstall/repair" button from ARP does work for the product I have installed but the main reason I need an entry is so that SCCM can inventory this information allowing us to query and target systems with this product when an upgrade is required.
Hope this helps....and suggesting this disgrace doesn't get me banned
Mosq
Install product interactively (so that an entry in ARP is created)
Open regedit
Navigate to HKEY_CLASSES_ROOT\Installer\Products\
Sift throught the many installed products to find the one you just installed
Export the reg key to a file
Create an installation script so that after the product is installed via SMS/SCCM the reg key is then imported
Check ARP for the relevant entry
Using the "uninstall/repair" button from ARP does work for the product I have installed but the main reason I need an entry is so that SCCM can inventory this information allowing us to query and target systems with this product when an upgrade is required.
Hope this helps....and suggesting this disgrace doesn't get me banned
Mosq
Posted by:
anonymous_9363
14 years ago
main reason I need an entry is so that SCCM can inventory this informationI had a feeling something like this might appear...
You have a fundamental misunderstanding of Windows Installer and SCCM. WI always writes the required entries in the registry. Whether or not the application appears in ARP is governed by the presence of one value in the 'Uninstall' branch, SystemComponent. ALL the remaining entries will be present and it is THESE entries which SCCM uses to inventory installed products. If I could remember, I'd tell you which one specifically it uses but I've forgotten. (Sadly, I used to know the API it called from MSI.DLL, too...) Anyway, point is, whether it appears in ARP or not, it can still be inventoried. You can build a simple script to test that, using the WindowsInstaller.Installer object to test the InstalledState property against a product's ProductCode.
Posted by:
ankorpo
14 years ago
Posted by:
anonymous_9363
14 years ago
FFR, ARPSYSTEMCOMPONENT merely needs to be present as a property for it to disallow the package's entry in ARP. Many assume that setting it to '1' enables it and '0' disables it. Wrong: If it contains ANY value, it will be acted upon. So, if you want an ARP entry, remove the ARPSYSTEMCOMPONENT property.
Posted by:
mikkojarvinen
14 years ago
ORIGINAL: VBScab
When ALLUSERS isn't specified, which is effectively the case here, the install is done per-machine, not per-user.
It's just the opposite. If ALLUSERS is not defined, install is per-user. This causes problems if the installing account is Local System.
http://msdn.microsoft.com/en-us/library/aa367559(VS.85).aspx
When deploying MSI's with SCCM (or SMS) and Package's 'Program' is set to 'run with administrative rights' (that is Local System) always make sure that ALLUSERS=1. You can define it from command line or put it to Property table.
[hr]
Mikko Järvinen
Posted by:
anonymous_9363
14 years ago
Posted by:
package_aligator
14 years ago
Posted by:
mikkojarvinen
14 years ago
ORIGINAL: VBScab
I know! How embarrassing! That's what happens when you're not concentrating because you're looking forward to your Christmas drin...lunch.
This is why I give advice only on April 1st. If I was wrong (which never happens) I can always say I was just april fooling. And now it's time for some Easter drin...egg hunt.
[hr]Mikko Järvinen
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.