Let’s understand how to fix SCCM Task Sequence Failed to find a valid network adaptor. The task sequence prompts an error Failed to find a valid network adaptor when you start the operating system deployment with Configuration Manager during pxe boot.
You could easily see the error message from the task sequence prompt. That means the machine doesn’t have network connectivity or a valid NIC driver. Examining the SMSTS log for task sequence failure issues is always recommended to help you understand the failure prompt, More you can explore SCCM OSD Task Sequence Troubleshooting Steps by Step Ultimate Guide SMSTS.log.
Let’s look at the list of official Microsoft tools for reading the SCCM related log files. You can use all these SCCM log viewer tools to check different types of log files. You can easily identify the SCCM log files .log or .lo_ file extensions. Top SCCM Log File Viewer Options for Admin
Issue Summary – SCCM Task Sequence Failed to find a valid network adaptor
The task sequence appears at the WinPE stage when you have started the deployment. Task Sequence fails with the following error message –
Task Sequencing Error: Failed to find a valid network adapter. For more information, contact your system administrator or helpdesk operator.
In this scenario, Task Sequence terminated at the beginning. You will collect the logs at WinPE X:\Windows\temp\smstslog\smsts.log. To get the command prompt window, you have to press the F8 key and locate the location to Open the log. Reviewing the SMSTS.log on the site server, you will get the highlight –
GetAdaptersInfo() failed.TSMBootstrap 24-09-2021 09:32:39 1396 (0x0574) VerifyNetworkAdapter() failed. 0x800700E8 TSMBootstrap 24-09-2021 09:32:39 1396 (0x0574) Failed to find a valid network adapter. For more information, contact your system administrator or helpdesk operator. TSMBootstrap 24-09-2021 09:32:39 1396 (0x0574) Failed to find a valid network adapter. Please ensure that this machine has a network adapter and appropriate network drivers. 0x800700E8. TSMBootstrap 24-09-2021 09:42:46 1396 (0x0574) oTSMediaWizardControl.Run(sMediaRoot, true, sTSLaunchMode), HRESULT=800700e8 (tsmbootstrap.cpp,1106) TSMBootstrap 24-09-2021 09:42:46 1396 (0x0574) Failed to run executing from media in WinPE Task Sequence Failed to find a valid network adaptor TSMBootstrap 24-09-2021 09:42:46 1396 (0x0574) Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, bReloadEnv, &uExitCode ), HRESULT=800700e8 (tsmbootstrap.cpp,1293) TSMBootstrap 24-09-2021 09:42:46 1396 (0x0574) Exiting with return code 0x800700E8 TSMBootstrap 24-09-2021 09:42:46 1396 (0x0574)
FIX – SCCM Task Sequence Failed to find a valid network adaptor
Let’s check the possible solution to fix SCCM Task Sequence Failed to find a valid network adaptor –
The boot image must have the appropriate NIC drivers added to it to find a network adapter and use it. You need to identify and download the necessary NIC driver for the boot image. To add Network drivers to a boot image –
Important – If you are making any changes to the existing boot image that might require content redistribution. It’s important to make a copy of the boot image and perform all necessary actions without impacting your production environment.
- In the Configuration Manager console, navigate to Software Library > Overview > Boot Image.
- Select the used Boot Image in Task Sequence deployment and Right click on Boot Image, Click Properties.
- Switch to Drivers tab – On the Drivers tab, add the drivers that are required to boot Windows PE. You can also view existing drivers already associated with a boot image. Consider the following points when you add device drivers –
- You must import device drivers into the drivers catalog before you add them to a boot image. For information about How to Import Windows Device Drivers into the Driver Catalog.
Note – You can also import the NIC driver, and when you import the driver in SCCM, the Import Drivers wizard will present you with an option in the import driver wizard to add it to boot images.
- As a best practice, add only NIC and Mass Storage Drivers to the boot image unless there are requirements for other drivers to be part of Windows PE. As WinPE already comes with many drivers built-in.
- To only display storage and network drivers, select Hide drivers that are not in a storage or network class (for boot images). This option also hides other drivers that aren’t typically needed for boot images.
- To hide drivers that don’t have a valid digital signature, select Hide drivers that are not digitally signed.
- To add multiple drivers to a boot image, select all the drivers you want to add, and then select Add or Remove Drivers to Boot Images from the context menu.
Once you are done with the driver import process, Click Apply and OK, close the Boot Image properties. The next important step is to distribute the boot image to distribution points before using the boot image to deploy an OS.
This allows you to boot into WinPE with your boot image and perform the task sequence deployment without any issue.
About Author -> Jitesh has over 5 years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus area is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.