546 reputation
31123
bio website
location Hillsboro, OR
age
visits member for 5 years, 2 months
seen May 22 at 16:18

Nov
13
awarded  Notable Question
Sep
21
awarded  Popular Question
Jul
2
awarded  Curious
May
23
awarded  Famous Question
May
22
comment Troubleshooting Application Evaluations in SCCM2012
It's important to note that the "unistall" registry location is used to list programs in the "Uninstall a program" section of the control panel. From what I can tell, this could be deleted and msiexec will still be able to find the package if you feed it the "/x {GUID}" command. For 99% of all programs, I can use this location to detect programs, but it is not an authoritative source.
May
21
awarded  Popular Question
Apr
21
awarded  Famous Question
Mar
18
comment Troubleshooting Application Evaluations in SCCM2012
I did find a class that seems to hold the information (Namespace=root\CCM\CIModels;Class=CCM_MSIProduct). When I install an MSI file, both this location and the Win32_Product update with the GUID and such. What's really interesting is that the CCM_MSIProduct is a lot faster at returning a query result in powershell. Don't know if that is significant.
Mar
17
comment Troubleshooting Application Evaluations in SCCM2012
Thank you for the long response. I've seen that area in the past and it's a red herring for SCCM deployments. SCCM is looking looking elsewhere when you perform the "Windows Installer" detection method. I'm sure I could add it into the logic, but I'm looking to avoid checking multiple places for the presence of the app. To make something work, I need to match the GUID to a location that have the version number. If I don't, I won't be able to perform minor updates.
Mar
17
answered Troubleshooting Application Evaluations in SCCM2012
Mar
17
asked Troubleshooting Application Evaluations in SCCM2012
Mar
17
answered Removing old application versions
Feb
6
awarded  Nice Question
Aug
3
awarded  Famous Question
Aug
1
awarded  Notable Question
Jul
24
awarded  Notable Question
Mar
21
awarded  Notable Question
Feb
13
comment BINLSVC warning in event log - netclass.inf parsing Manufacture
Also, after realizing that RIS doesn't like a lot of different software, I moved to a WDS method. It's more similar to the traditional "sysprep and duplicate" method of deploying windows.
Jan
31
awarded  Notable Question
Jan
16
comment BINLSVC warning in event log - netclass.inf parsing Manufacture
Once I realized that BINLSVC is part of the WDS Service, it made a lot more sense. This error is driver specific and does not affect the deployment process. The problem I was having related to the intel driver not loading from the $oem$ location. I had to copy it into the i386 folder with everything else.