clickmaster Posted February 25, 2015 Report post Posted February 25, 2015 Hi folks, today I ran into an issue with a HP G800. I started a Windows 7 task sequence with PXE and the only step that was done was the OS installation. The reason was a wrong/missing network driver in the x86 boot image. Doing some troubleshooting I asked myself when exactly the task sequence leaves the WinPE environment and continues in Windows. Because after installing Windows 7 the client does a reboot into windows. After that...is there any step in WindowsPE again? Can somebody describe the process in which WinPE handles over the NIC driver from the boot image to Windows 7 OS? There has to be a point in the task sequence where the deployed OS gets the NIC driver from the boot image, right? In most cases if I forgot to inject the NIC driver into the boot image, WinPE can download the windows .wim file. So I guess WinPE doesn´t need a specific NIC driver because it can use the NIC without the vendor driver. The problem occurs later in the OS with the consequence that no software is installed and the client is not member of the domain. The main reason to inject a NIC driver into the boot image seems to be that WinPE has to copy the driver to the OS after deploying the .wim file. Is this correct? I know how I get this to work, but I want to know why I have to do this . Thanks a lot! Regards... Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted February 25, 2015 Report post Posted February 25, 2015 during setup windows and configmgr Windows is laid down and after installing device drivers it boots into Windows... does that help ? nic drivers inserted into your boot wim are only for WinPE sections of the task sequence, for the rest of the task sequence use the apply driver package step where it injects drivers into Windows Quote Share this post Link to post Share on other sites More sharing options...
