Reputation
606
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 14 24
Newest
 Yearling
Impact
~126k people reached

  • 0 posts edited
  • 0 helpful flags
  • 7 votes cast
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.
Jan
16
accepted BINLSVC warning in event log - netclass.inf parsing Manufacture
Jan
10
asked BINLSVC warning in event log - netclass.inf parsing Manufacture
Nov
28
awarded  Popular Question
Nov
7
awarded  Popular Question
Nov
2
awarded  Popular Question
Oct
30
awarded  Notable Question
Oct
25
awarded  Popular Question
Oct
18
comment Purge print driver cache on windows 7 with powershell script
It's actually Explorer.exe which has the file locked. You can kill the process (which kills the windows interface) delete the file, and then relaunch explorer to bring back the windows interface. It's not a good experience for the end user if all of their windows suddenly disappear.