The smsts.log generally doesn't reflect this specifically as the driver load process occurs before the task sequence engine loads. Some symptoms do appear in the smsts.log like not being able to communicate properly. The normal distinct symptom is that the system reboots almost immediately after booting to WinPE. Dropping to a command-prompt before the reboot and running ipconfig is a definitive way to determine whether or not an appropriate NIC driver loaded or not.
Custom boot image in OSD
Hi Everyone,
Hope everyone would be doing good and being safe !!
Need some experience dealing with an issue when we had to import the driver for a certain model in our boot image as they don't PXE boot in the absence of it.
I need the help to know the exact line i should be spotting in SMSTS that could give me an idea of that boot.WIm needs a NIC driver to be imported???
Hope someone's help and experience can benefit me.
Thanking you in advance.
Regards,
Shashi Dubey
-
Jason Sandys 31,291 Reputation points Microsoft Employee
2021-01-12T19:04:24.007+00:00
1 additional answer
Sort by: Most helpful
-
Gary Blok 1,736 Reputation points
2021-01-13T06:03:09.03+00:00 The Task Sequence will tell you the assigned boot media, then you go into that boot media and modify it to add the drivers:
https://docs.recastsoftware.com/ConfigMgr-Docs/TaskSequence/ModifyBootImages.html