Network Connectivity issue in PXE boot during the driver installation phase in SCCM OSD

SCCM Ver 2403 Boot image 22000 Deploying W11 23H2

Good afternoon, all! I’ve been working on this for about a week with a single work around. Issue : all of a sudden, PXE cannot complete an image. This is happening to all hardware that we’ve previously imaged as well as new hardware that just came in.

– hit F12 > choose IPV4 boot

– gets to WinPE > choose correct TS

– partitions hard drive > applies OS > applies windows settings > as soon as it gets to the driver pack, it loses all network knowledge.

Went to the dell site (we are a dell shop) and grabbed the latest Windows 11 driver pack. Created a new boot image > injected only the windows 11 drivers into that pack (according to dell, this is the only driver pack you’ll need for windows PE and their devices) tried to image and same issue is happening… created the basic TS from SCCM and did not change a thing – same thing happens.

upon booting, i can get an IP address (obviously, or we’d have other issues) – i can ping the MP and all DP’s that are needed. once it gets to the driver install (not always, but i’d say 90% of the time it happens here) i bring up a command prompt when it fails and i do an ipconfig and cannot find any network info. This is where it gets a bit odd ….

If i bring up a command prompt and have a constant ping out to the management point upon starting the TS, it will always get past the driver area and continue on to the “setup windows and configuration manager” area and flow right on through the task sequence… Normally i had say “driver issue” However,

– i’ve gone to dells website and downloaded all network and storage drivers for this model and injected them into the boot image. – this all of a sudden happened to every model at the same time. I’d also say network issue as we did change our core switch around the same time this happened, but no IP addresses changed… all configurations came over, plus i can’t think what word cause a computer to lose an IP address part of the way through a TS.

Here is some Snippers from tech SMSTS log from the X: drive –

it basically is happy until it needs to send it’s message to the MP and it can’t as it cannot find an IP address. QUESTIONS : i am still half way between a driver issue, even though i have all drivers for this model (even though it’s all models) -am i missing something here? if it’s network related – what would i have the network guys check? supposedly they moved all the configs over to the new switch, but ya never know…

————— this is where it’s going through and adding the drivers to the offline driver store . .

DISM successfully added drivers to the offline driver store. OSD Driver Client 9/3/2024 1:14:27 PM 2460 (0x099C) Successfully added “C:_SMS Task SequencePackagesADC00891FFF7BC80-A8B0-4D79-A882-C48FA5EEFB7F” to the Windows driver store. OSD Driver Client 9/3/2024 1:14:27 PM 2460 (0x099C) Successfully got a list of drivers to apply from the driver package “ADC00891” and installed them. OSD Driver Client 9/3/2024 1:14:27 PM 2460 (0x099C) Release Source() for C:_SMSTaskSequencePackagesADC00891. OSD Driver Client 9/3/2024 1:14:27 PM 2460 (0x099C) reference count 1 for the source C:_SMSTaskSequencePackagesADC00891 before releasing OSD Driver Client 9/3/2024 1:14:27 PM 2460 (0x099C) Released the resolved source C:_SMSTaskSequencePackagesADC00891 OSD Driver Client 9/3/2024 1:14:27 PM 2460 (0x099C) Exiting with return code 0x00000000 OSD Driver Client 9/3/2024 1:14:27 PM 2460 (0x099C) Process completed with exit code 0 TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) !——————————————————————————————–! TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Successfully completed the action (Apply Driver Package) with the exit win32 code 0 TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) MP server http:// . Ports 80,443. CRL=false. TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Setting authenticator TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Sending Status Message TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Setting the authenticator. TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) CLIB SMS Message Win Http Transport::Send: Win Http Open Request – URL::80 CCM_POST /CCM _System/request TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Not in SSL. TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) ——————— This is where it craps the bed and cannot send it’s notice to the MP. Error. Received 0x80072ee7 from Win Http Send Request. TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) unknown host (get host by name failed) TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) HR, HRESULT=80072ee7 (D:dbsshcmgm502_134106cmd1ySRCFrameworkOSD Messaginglibsmsmessaging.cpp,10293) TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Sending with win http failed; 80072ee7 TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Will retry in 4 second(s) TS Manager 9/3/2024 1:14:27 PM 2028 (0x07EC) Retrying… TS  Manager 9/3/2024 1:14:32 PM 2028 (0x07EC) CLIB SMS Message Win Http Transport::Send: Win Http Open Request – URL: :80 CCM_POST /CCM _System/request TS Manager 9/3/2024 1:14:32 PM 2028 (0x07EC) Not in SSL. TS Manager 9/3/2024 1:14:32 PM 2028 (0x07EC) Error. Received 0x80072ee7 from Win Http Send Request. TS Manager 9/3/2024 1:14:32 PM 2028 (0x07EC)