xerxes2985 Posted August 17, 2017 Report post Posted August 17, 2017 I am encountering an issue with a Surface Book. The device PXE boots fine, and it pops a message like it's going to start and prompt me for the password. Then, it never pops up, and just reboots. any suggestions? the drivers are distributed, and in my task sequence. Quote Share this post Link to post Share on other sites More sharing options...
xerxes2985 Posted August 18, 2017 Report post Posted August 18, 2017 It quits at "Preparing Network Connections", however I cannot find any network drivers for the surface ethernet adapter (model 1821). It says they are included with W10 1511 and newer. But, that doesn't help me with SCCM. Quote Share this post Link to post Share on other sites More sharing options...
TrialandError Posted August 18, 2017 Report post Posted August 18, 2017 The Surface Ethernet adapter drivers are here. https://www.microsoft.com/en-us/download/details.aspx?id=38826 Quote Share this post Link to post Share on other sites More sharing options...
gavin1973 Posted August 18, 2017 Report post Posted August 18, 2017 Hi, Just to clarify the laptop is able to pxe boot and pull down your boot image but fails before the task sequence starts? Quote Share this post Link to post Share on other sites More sharing options...
xerxes2985 Posted August 18, 2017 Report post Posted August 18, 2017 51 minutes ago, gavin1973 said: Hi, Just to clarify the laptop is able to pxe boot and pull down your boot image but fails before the task sequence starts? Yes. I am using a surface Ethernet adapter model 1821 (Gigabit Ethernet USB 3.0). it fails when it's trying to prepare network connections. I have a surface Ethernet adapter model 1663 (gigabit Ethernet USB 3.0) and it allows me to get through the whole process. Quote Share this post Link to post Share on other sites More sharing options...
gavin1973 Posted August 18, 2017 Report post Posted August 18, 2017 It very much sounds like nic drivers needed in the boot image which has caused me headaches over the years and have you added the driver pack into SCCM task sequence? in past experience boot image has been fine but not having the correct drivers in the task sequence let me down. Quote Share this post Link to post Share on other sites More sharing options...
