Problem with device drivers during OSD

[trhg]

Hi,

I'm having

a problem with applying drivers to my PowerEdge M600/610 And 620.

 

I have made

a package with drivers, sent it to the DP's and added the packed to the task
sequence.

The problem: The network drivers won't install during OSD. But when i put the

drivers on a USB stick and install them manually ( Computer -->
Properties --> DeviceManager)

 

It Works. so it's no problem with the driver it self i guess?

We are using SCCM 2012 SP1.

Anyone seen a similar problem ?

[Rocket Man]

You have used a WMI query for these models in the driver package properties in the TS?

[trhg]

You have used a WMI query for these models in the driver package properties in the TS?

Yes "SELECT * FROM WIN32_COMPUTERSYSTEM WHERE MODEL LIKE "%PowerEdge M610%"

 

I can see it hits the right package

[Rocket Man]

Have you injected the NIC drivers for these models into the boot.wim that you are using?

[trhg]

Have you injected the NIC drivers for these models into the boot.wim that you are using?

 

 

No i didn't need to. It PXE booted without any fuzz..

[Rocket Man]

I had a similar experience with a specific model of machine, not DELL.

I had to download the drivers manually test them and then package them.

The machines would boot no problem and at the apply drivers task it would stop at the correct package and apply.

I also had quite a bit of software to apply also which was part of the TS, but after the setup windows & configMgr task it would bomb out.

Once loaded into the OS it was apparent what was happening, the NIC drivers did not get applied, so thus no connection to the content shares for software(Strange)

I decided just to manually add the specific NIC drivers to the boot.wim(even though they were already booting).

After I did this they still booted, still picked up the driver package, but this time successfully applied the NIC drivers so my software was installed etc etc..

 

It is strange as to why doing this solved my problem as I thought that injecting drivers into the boot.wims is only to get a successful boot at PXE time?

[trhg]

I had a similar experience with a specific model of machine, not DELL.

I had to download the drivers manually test them and then package them.

The machines would boot no problem and at the apply drivers task it would stop at the correct package and apply.

I also had quite a bit of software to apply also which was part of the TS, but after the setup windows & configMgr task it would bomb out.

Once loaded into the OS it was apparent what was happening, the NIC drivers did not get applied, so thus no connection to the content shares for software(Strange)

I decided just to manually add the specific NIC drivers to the boot.wim(even though they were already booting).

After I did this they still booted, still picked up the driver package, but this time successfully applied the NIC drivers so my software was installed etc etc..

 

It is strange as to why doing this solved my problem as I thought that injecting drivers into the boot.wims is only to get a successful boot at PXE time?

its a bit strange but i will give it a shot!

 

ill be back with updates !"

[trhg]

its a bit strange but i will give it a shot!

 

ill be back with updates !"

 

 

I had a similar experience with a specific model of machine, not DELL.

I had to download the drivers manually test them and then package them.

The machines would boot no problem and at the apply drivers task it would stop at the correct package and apply.

I also had quite a bit of software to apply also which was part of the TS, but after the setup windows & configMgr task it would bomb out.

Once loaded into the OS it was apparent what was happening, the NIC drivers did not get applied, so thus no connection to the content shares for software(Strange)

I decided just to manually add the specific NIC drivers to the boot.wim(even though they were already booting).

After I did this they still booted, still picked up the driver package, but this time successfully applied the NIC drivers so my software was installed etc etc..

 

It is strange as to why doing this solved my problem as I thought that injecting drivers into the boot.wims is only to get a successful boot at PXE time?

 

 

Didn't work

[Rocket Man]

Where did you get the driver package from?

Is it an intel or broadcom NIC card that you have currently got active?

have you got both NIC driver sets packaged for this model?

[Ocelaris]

To troubleshoot, remove any WMI queries in case that's the issue, and just have it run unconditionally. You also ought to double check the PCI Device ID to verify that it is indeed the correct driver, Open up the .inf file and look for the line that says something like this:

 

"PCI\VEN_8086&DEV_2A42&SUBSYS_30DB103C"

 

compare that to device manager, hardware IDs... to confirm at LEAST VEN_####&DEV_#### match.

 

 

Also checking ""Do Attended installaiton of unsigned drivers on versions of Windows where this is allowed" helps a lot.