Danny-B-

Quick workaround to this problem is to open command prompt (F8) and type TSBootShell ... This will restart the Task Sequence environment and as the network card has now initialized, everything will work as expected. Longer term workaround is to mount the boot image (Boot.wim in the extracted boot meida Sources folder) - I Used Gimagex to mount the boot.wim file to a folder on my C: Drive Find the winpeshl.ini file in Windows\System32 folder Edit to read as follows: [LaunchApps] %windir%\system32\wpeinit.exe %windir%\system32\ping.exe -n 30 127.0.0.1 > NULL %SYSTEMDRIVE%\sms\bin\x64\TsBootShell.exe save the file and close any open file explorer windows .... commit the changes and unmount the image. Overwrite the boot.wim file, and use in your deployments (media boot / PXE etc) It just adds a short wait before running the TsBootShell.exe, enough for crappy NICs to initialize anyway. Bear in mind that if you recreate your boot file or update it at all, it will be overwritten and you'll have to do the same process again.

Hi Grant, It has to be the "Join Domain or Workgroup" task as the other option is a sysprep step which applies in WinPE and wont do the same task. I have mine placed in my task sequence after the SCCM client install step ... When you fill in your Domain and OU settings then enter your username/pass does this verify correctly when you click the verify button? Ensure that a domain admin account is used here... The only time my Join domain task has failed is when the drivers didn't apply properly, and no network driver was present.

Thanks for the reply Jorgen. I have tried the prestat commands option, i think i happened to find that reddit article a few weeks ago actually ... It didnt resolve the issue for me though, that "Failed to find a valid network adapter" message appears before the prestat command kicks in, I'm pretty sure that if i can find a way of delaying the built in network adapter check, it will work fine. i guess i'll have to mount the boot image and take a look at the WinPE scripts that call this network adapter script.

Hi Ingram, We seem to be in the exact same boat ! I have exactly the same issue with a Lenovo E530, the x86 driver injects properly into the WinPE image though, but it still doesn't work to boot. Please let me know if you have managed to resolve this issue as we have a vast number of these to image/ReImage ... somwhere in the region of 170! Cheers

Hi folks ! We're fairly new to SCCM, having only been using it now for about 4 months, but only recently in a production environment. We come from a background of Symantec Altiris, and have been using that for 4 years or so ... I have most models in our environment working fine with OS Deployment but one model (Lenovo E530 laptop) will refuse to boot to the point that we can run tasks. When booting to WinPE (Media or PXE) I get the "Failed to detect a valid network adapter" message. Normally this is due to incorrect or missing drivers from the WinPE image, but if i press F8 to get the command prompt window, i can type "ipconfig" and it WILL display an IP address ... which would indicate to me that the drivers are correct !! I can also maps a drive etc, so i'm sure they are working fine. So why the message? is it possible that the check for a valid network adapter runs to quickly for adapter and returns a negative result before initialized properly? How can i overcome this? All other models in our estate seem to work fine. Thanks in Advance