Hi All

I am having an issue in my TS with the following model

HP ProDesk 600 G1 TWR

I have to deploy win7 x64 Pro using OSD

I am using SCCM 2012 R2 and ADK 8.1

The OS install but the drivers for the NIC does not install and obviously it does not get joined to the domain, also the password that I specify for administrator also does not get applied

I am now struggling for about 2 weeks and cannot find a resolution

previously I had a boot image with most of the drivers injected into it but I have reverted to a "clean" boot image as I read that it can also cause issue

in other words I have a "clean" boot image as well as a "clean" windows 7 capture image -

I have now created a separate TS with a new "Clean" Boot image - which contains no drivers for this model

I then created a driver package - I have in fact tried several different methods to create the driver package - from using the original driver that came with the DVD to downloading the drivers from the following URL to capturing drivers from an installed HP ProDesk 600 G1 TWR - none worked

if I build a system from a WIN 7 DVD I can install the supplied drivers or even the drivers that I have downloaded

http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html

here is the WMI query that I am using to detect the model

SELECT * FROM Win32_ComputerSystem WHERE Model = "HP ProDesk 600 G1 TWR"

In my task sequence I am also catering for KMDF driver and I followed this post - I tried to do it through offline servicing but it failed for some reason as well

https://deploymentramblings.wordpress.com/2013/10/24/osd-injecting-the-windows-7-kernel-mode-driver-framework-kmdf/#comment-134

here is a link on one drive to the smsts.log file

http://1drv.ms/1GLSOuk

from the log file it does not seem to create the "scratch" folder for some reason and then the KMDF driver does not install either and this I believe is what is causing the failure for the drivers not to install

if I test the TS on "older" models it works without a problem (on these models I however I do not use KMDF)

I need some clarity I on this

How are you adding the KMDF update to the deployed image?

The info at

https://anothermike2.wordpress.com/2011/06/06/nice-to-know-why-did-windows-7-pick-that-driver/ may also be helpful to track down why the driver is not being chosen.

Is that the only smsts.log file? Is there a dated one as well? Because this does not appear to include all th TS steps. Regardless, I think you need to move your Apply Driver Package step up above the Setup Windows and ConfigMgr step. The "Setup" step is the first reboot and you haven't applied drivers yet, so when it tries to join the domain it's going to fail.

Regardless, I think you need to move your Apply Driver Package step up above the Setup Windows and ConfigMgr step. The "Setup" step is the first reboot and you haven't applied drivers yet, so when it tries to join the domain it's going to fail.

This is absolutely correct. The Apply Drivers tasks simply copy drivers to the target system and inject them into the deployed image so that they are available during Windows setup. Anytime after that is useless (and will fail).

Hi
apologies for only replying now
although the TS says reboot in PXE mode - this is an out of the box install - we are doing a F12 PXE Boot
as for the KMDF driver
I have created a pkg without a program and added it to all distribution points
I first create a folder on the OS partition with the following command in the Make Scratch Directory step
cmd.exe /c mkdir %OSDisk%\Scratch
I then created the following step in the TS
"Install KMDF 1.11 Update" and using the the following command line - PS The package ID for the KMDF driver is "ID100104"
cmd.exe /c X:\windows\system32\dism.exe /ScratchDir:%OSDisk%\Scratch /Image:%OSDisk%\ /Add-Package /PackagePath:%_SMSTSMDataPath%\Packages\ID100104\Windows6.1-KB2685811-x64.cab

thank you - I will have a look at the provided link as well

ps I have moved the driver installation step up and will test

Mike

• Edited by mikeg_gf 22 hours 22 minutes ago

None of that matters; i.e., ignore my first post. As pointed out above, a driver package must be applied in a TS before the setup windows and configmgr task.

Hi
apologies for only replying now
although the TS says reboot in PXE mode - this is an out of the box install - we are doing a F12 PXE Boot
as for the KMDF driver
I have created a pkg without a program and added it to all distribution points
I first create a folder on the OS partition with the following command in the Make Scratch Directory step
cmd.exe /c mkdir %OSDisk%\Scratch
I then created the following step in the TS
"Install KMDF 1.11 Update" and using the the following command line - PS The package ID for the KMDF driver is "ID100104"
cmd.exe /c X:\windows\system32\dism.exe /ScratchDir:%OSDisk%\Scratch /Image:%OSDisk%\ /Add-Package /PackagePath:%_SMSTSMDataPath%\Packages\ID100104\Windows6.1-KB2685811-x64.cab

thank you - I will have a look at the provided link as well

ps I have moved the driver installation step up and will test

Mike

• Edited by mikeg_gf Wednesday, July 01, 2015 9:23 AM