Currently having an issue with a client computer trying to complete the OSD. The client PXE boots ok and initializes the OSD. the Windows image gets applied and then the machine reboots to install an application. Once the application is installed, it reboots again before trying to install the rest of the applications. After completing the second reboot, the client loses it's network card driver and as such fails the OSD because it can't contact the DP. I've seen issues before where a machine will PXE ok, but then drop after rebooting into the Windows environment, however this is working ok in the Windows environment up until the second reboot. The strangest thing is that this machine used to work all the way through the OSD without any issues. Any help would be most welcome. Thanks RichardRichard Green, MCSE Windows Server 2003

What is initiating the second reboot? Is it a restart computer task? If so, make sure that it is set to reboot into the currently installed OS and not the boot image. How are you verifying that the network connection is being dropped? What does smsts.log say?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I have seen something simular, where the IP lease time was to short.. I was server deployment though, but might be worth checking out. what program are you installing?Michael Petersen My Deployment Blog - http://blog.coretech.dk/mip

What is initiating the second reboot? Is it a restart computer task? If so, make sure that it is set to reboot into the currently installed OS and not the boot image. How are you verifying that the network connection is being dropped? What does smsts.log say? Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys Jason, The restart is initiated by a McAfee VirusScan package installation. The restart parameteres are definatly correct as the same sequence runs without issues on other models of machine (it's a Window 7 thin image deployment, so there is one image for all models). I am pressing F8 to open the Command Prompt, then running IPCONFIG, which prior to the reboot shows the Local Area Connection with a valid IP etc, however after the reboot, no Local Area Connection is present. Opening devmgmt.msc shows the Ethernet Adapter, however it is shown with a warning exclaimation that there is no driver for it. Thanks RichardRichard Green, MCSE Windows Server 2003

Have you checked to ensure that you are applying the correct drivers to the image for that specific model? As Jason suggested, posting your smsts.log will help identify the issue

So it seems that something is causing the NIC driver to disappear (based on your above description). I can't say I've ever seen that happen but the usual suspect here is McAfee (just saying the name makes me cringe btw). How about doing an IPConfig right before the reboot and/or during the AV installation to see if the driver is loaded? The general recommendation (even from McAfee) is to use ePO to McAfee? Deploy the ePO agent during the TS, but then let McAfee do the rest. Does this behavior persist if you completely remove McAfee from the TS?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys