First off, did  you try this without the WMI condition to ensure that the 
drives you have in the package are the proper one for you system.

In the log does is show the step being executed or skipped?  I know that we 
have had a lot of trouble with HP model names.  HP is not known for their 
consistency in branding their machines unfortunately.

In our case we just use a much simpler set of conditions to limit the driver 
package selection.  We have a group that keys off of the maker 
(Hewlett-Packard) and then a WMI query for each particular model.  In the case 
of the 600 we just do a simple "Select * from Win32_computerSystem where Model 
like "%600%"".

Thanks
Mike


From: [email protected] [mailto:[email protected]] On 
Behalf Of Brian McDonald
Sent: Monday, March 24, 2014 10:20 AM
To: [email protected]
Subject: [MDT-OSD] Driver Injection HP ProDesk 600 G1 SFF

I am trying to setup support for an HP ProDesk 600 G1 SFF PC. Drivers don't 
seem to be injecting properly. For my initial test I am utilizing an SCCM TS 
only. I have disabled the Apply Device Drivers Step and created the Apply 
Driver Package step with the following query:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE '%HP ProDesk 600 G1 SFF%'

In the SMSTS.log file it shows that the task sequence processes the query and 
that the step is complete, however, it doesn't inject the NIC driver, 
therefore, my device doesn't join to the domain and the other drivers do not 
install.

I have confirmed I have downloaded the proper drivers from HP's website. I 
looked in my NIC folder and noticed I have several different NIC drivers and 
I'm not sure which one should be used and if I should clean up the other 
directories. I did clean up all the Windows 8 drivers from the source files 
before creating my driver package. Could the fact that I have multiple drivers 
NIC drivers as part of my driver package be causing issues with driver 
injection?

Thank you!
Brian
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues 

Reply via email to