PENDING SCCM OSD inject drives practice for HP, DELL models?

[eavenhuang]

Dear Experts,

I've set up SCCM OSD and successfully deployed the latest Windows 11 to ASUSD320 models, all is good. Now I need to deploy the same OS to the HP laptops but when I tried F12 to network boot, it flashed in less than 1 second and switched back to the boot order option wizard. Since it's working fine with ASUS models, I suspect it had something to do with the network drive not being detected or injected.

In MDT, we use the general driver packs for HP and Dell and it works fine for our models including HP430G7, G8, HP440G8, Lenovo L389/390, etc. but this seems challenging for SCCM.

Any idea? If we need to deploy the same driver package to SCCM TS, what are the correct steps to get this to work? Thank you very much.

 

[Stanley Road]

Dear Experts,

I've set up SCCM OSD and successfully deployed the latest Windows 11 to ASUSD320 models, all is good. Now I need to deploy the same OS to the HP laptops but when I tried F12 to network boot, it flashed in less than 1 second and switched back to the boot order option wizard. Since it's working fine with ASUS models, I suspect it had something to do with the network drive not being detected or injected.

In MDT, we use the general driver packs for HP and Dell and it works fine for our models including HP430G7, G8, HP440G8, Lenovo L389/390, etc. but this seems challenging for SCCM.

Any idea? If we need to deploy the same driver package to SCCM TS, what are the correct steps to get this to work? Thank you very much.

I had the same with Lenovo ages ago and i think it was a BIOS setting, maybe secure boot, maybe a cross check with a working Asus laptop? What does the pxe log say?

 

[eavenhuang]

I had the same with Lenovo ages ago and i think it was a BIOS setting, maybe secure boot, maybe a cross check with a working Asus laptop? What does the pxe log say?

I also tried Lenovo laptops and the same result. I'm not sure why the default boot image works with ASUSD320 but not others, maybe the default boot image has some generic network drivers already?

When I'm using MDT to deploy the OS to these problematic laptops, they worked just fine, so I don't think this should be anything to do with the BIOS setting as we didn't touch any during the whole test, SCCM vs MDT.

 

[AhmedLS]

i use the WinPE Drivers for both dell and hp (downloadable from dell and hp sites) in the boot image and have no problem booting any so far.
been using this boot image for all Zbooks and Probooks up to latest month releases.

 

[Stanley Road]

I also tried Lenovo laptops and the same result. I'm not sure why the default boot image works with ASUSD320 but not others, maybe the default boot image has some generic network drivers already?

When I'm using MDT to deploy the OS to these problematic laptops, they worked just fine, so I don't think this should be anything to do with the BIOS setting as we didn't touch any during the whole test, SCCM vs MDT.

So just going back a step, before you had sccm how and where was your pxe responder configured. It's not clear to me how your whole mdt set up looks like. For example, before i had sccm i used MDT standalone with TFTP32 and PXE Linux installed on a lan connected pc. I'm going to assume you now have a pxe enabled DP in your environment which has an smspxe.log you can check?