Hi Guys, Having an issue currently. We have a new model netbook which is an Acer One D255E. We are able to push windows 7 images to the older Acer One (the 532H) Currently I am able to PXE boot the machine and WinPE seems to load but it restarts at the point when it should bring up the task sequence wizard in order to retrieve policy for the computer. Id has a mouse pointer and also a black background but the wizard never displays and at that point it just restarts I have had a look around. Apparently we can inject drivers into the boot image (.wim file) but I dont think this is previously how my predecessor did it because there were no drivers loaded in the Windows PE tab for the boot image (either X86 or X64). Is there another way that he possibly did this? I know that he has various driver packages but I thought these would only be applied once the selected image starts to pull down Any suggestions would be great.

WinPE in CM07 SP2 is based upon Windows 7 and comes with a lot of drivers built-in. You older models most likely used one of the built-in NIC drivers but the newer models use a NIC type without a built-in drivers. The defintive way to test is to press F8 as soon as you can in WinPE to get a command prompt and then do an ipconfig. If the only thing that displays is the header, "Windows IP Configuration", and no other info, then the driver is missing (or did not load properly for some reason although that rarely happens). Here's a guide on adding drivers to your boot image(s): http://technet.microsoft.com/en-us/library/bb680705.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Thanks, unable to bring up command prompt using F8 during the WinPE stage, I have ticked "Enable Command Support" (was not ticked to begin with) in the WinPE(x86) properties and then attempted to update distribution points but it does not update for some reason. Does not even display "Install Pending" which is very weird. It just has the last time that this was copied to the distribution points?

Refresh the console -- this is still an MMC Snap-in :-( Check the distmgr.log if that doesn't change anything.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Left it overnight and eventualy the .wim copied to DPs. Once again you were on the money with the network driver suggestion (added this to the boot########.wim. Awesome, thanks so much. Real big help Nick