Network driver not available anymore after 'Setup Windows and ConfigMgr' step in task sequence

[Bram]

We're having a weird issue with network drivers that are successfully injected during the 'Auto Apply Drivers' step but not working afterwards so the entire task sequence fails because it can't find a proper network connection after the 'Setup Windows and ConfigMgr' step.

 

Some parts of the smsts.log:

 

Finding and installing the network driver during 'Auto Apply Drivers':

 

...
Ranking compatible drivers for Intel(R) 82579LM Gigabit Network Connection

...
Preparing to install driver "Intel(R) 82579LM Gigabit Network Connection". OSDDriverClient 12/04/2013 12:38:43 1904 (0x0770)
Resolving content for driver "Intel(R) 82579LM Gigabit Network Connection" OSDDriverClient 12/04/2013 12:38:43 1904 (0x0770)
...
Installing driver "Intel(R) 82579LM Gigabit Network Connection" OSDDriverClient 12/04/2013 12:38:48 1904 (0x0770)
Copying "C:\_SMSTaskSequence\ContentCache\A4D4FD89-88A3-4672-A404-E926B6C7E456" to "C:\_SMSTaskSequence\drivers\1". OSDDriverClient 12/04/2013 12:38:48 1904 (0x0770)
Successfully installed driver "Intel(R) 82579LM Gigabit Network Connection". OSDDriverClient 12/04/2013 12:38:48 1904 (0x0770)
...

Successfully completed the action (Apply Device Drivers) with the exit win32 code 0 TSManager 12/04/2013 12:38:48 1304 (0x0518)

The next steps workout fine:

 

Successfully completed the action (Setup Windows and Configuration Manager) with the exit win32 code 0 TSManager 12/04/2013 12:45:17 1304 (0x0518)
Successfully completed the action (Install Updates) with the exit win32 code 0 TSManager 12/04/2013 12:50:31 2896 (0x0B50)

The following steps install device driver packages based on a WMI query (Query = SELECT * FROM Win32_ComputerSystem WHERE Model Like "%9470%").

But there is no NIC available anymore:

 

Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)

When pressing F8, doing an 'ipconfig /all' shows no NIC at all, so the driver is actually not installed and the task sequence failed.

Anyone ever had this issue? I have a feeling it broke after upgrading to SP1 but I'm not 100% sure.

 

 

smsts-20130412-130716.log

[itguru1982]

Might be worth injecting the NIC drivers into your boot image.

[Bram]

Thanks for the tip but the drivers are already available in the boot image. Really weird problem.

[Oneone]

You have to install the driver in a driver package for that model, i have run into the problem you are having alot of times.

 

Even if you have the driver in the WinPE phase you cant use it after you install the client and it reboots to windows, so if you have a driver package for that modell doublecheck the network drivers that are on there.

 

good luck.

[Bram]

Thanks for the response.

I've added an extra driver pack for the model and added the 'Apply Driver Package' just before 'Setup Windows and Configuration Manager'.

It seems to be installed:

Start executing an instruction. Instruction name: Apply Driver Package. Instruction pointer: 7
Query = select * from Win32_ComputerSystem where Model like "%9470m%"
The WMI condition expression is evaluated to be TRUE
...
Successfully applied driver package "ISC0003F".
Successfully completed the action (Apply Driver Package) with the exit win32 code 0

Now during the installation of the package this error seems to pop up numerous times, but the installation seems to be successful if I may believe the log.

Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type

But still after the 'Setup Windows and Configuration Manager' which reboots the device, the driver is gone and no connection can be made to get other drivers/software.
I made sure the drivers in the pack are working by copying the pack folder to an usb stick and I'm able to install the NIC driver by pressing F8 after the task fails.

 

Do I need to install the driver at another step?

smsts.log

smsts-20130415-111620.log

[itguru1982]

There are a lot of errors in the log, can you post a screen print of your task sequence, give us an idea of what is happening and when. Thanks.

[Bram]

Found the issue. Our task still used setup.exe for Windows 7 deployment instead of WIM installation and this is not supported anymore in 2012 SP1. Would be nice if Microsoft added some kind of warning if you still try to do this because now it's totally unclear from within SCCM or the logging. I hope this topic helps other people who didn't rtfm of SP1 like me

 

http://scug.be/sccm/2013/01/13/configmgr-sp1-windows-7-deployment-is-not-supported-anymore-from-the-setup-exe/