Here's the situation. I had a computer crash mid through an OSD deployment. On the computer now is basically a corrupted OS. 1. I deleted the computer from SCCM, and in AD as well. 2. I did a full system discovery and updated the collection for All systems. The computer was not found. 3. I did a search via direct membership via mac address for the computer on All systems, the computer was not found. 4. I took the mac address for the crashed pc and used computer association and imported it to a collection called OSD Failure. 5. I cleared last pxe advertisement on All systems, unknown computers, and OSD Failure. 6. I stopped the WDS service, cleared the pxeboot files and re-started the WDS service. 7. I re-advertised the crashed TS to the OSD failure collection. Making it mandatory, also tried non mandatory, always re-run program,high.Here's is what happens, I boot the machine via PXE, it boots to WinPE, says there is a TS about to run in 180 seconds, I click ok, it says preparing network connections and then after about 30 secs it reboots back into the corrupted OS, and the TS never kicks off. I know the boot image has the correct nic drivers because I have pxe booted this pc in the past with the same boot image with 0 issues. How can I resolve this, I really need to image this computer.

After PXE booting, but before the task sequence kicks off, you'll need to 'clean' the drive. It's a problem that pops occasionally, basically there is left over Task Sequence information on the drive and it's somehow screwing things up. More prevalent with MDT task sequences seemingly. Run the following commands from a command prompt (make sure F8 for command prompt is enabled in your boot image). diskpart select disk 0 clean Exit from that, and try running the task sequence again. Good luck Cheers.

Seemingly I have to do this a lot to be able to re-run a TS. If a pc is known to configuration manager and I advertise a TS that has already been run on this machine, and even if I clear the last pxe advertisement the TS will not start even though the program behavior is always re-run. I boot to pxe, the machine boots to winpe and eventually just reboots, the only way I can get the TS to run is to wipe the drive first, than and only then the TS runs. Does anyone know why this is happening and if so is there a workaround other then wiping the drive?

If you haven't see password window or window with "Next" button, then this is only NIC problem. You can discover it. Enable command line for your boot image, press F8 when boot image will be loaded, prompt "ipconfig" in command line. If IP address not appears in cmd then add NIC driver to your boot image.

It's not the boot image it has the NIC.I am just not understanding configuration manager. My work flow is wrong. 1.Pc exists in configmgr 2. I advertise TS to collection which has that pc in it 3.Manually boot pc to pxe, it boots to winpe, (I press f8 to see if it is getting an IP) it is. 4. Eventually pc just reboots back into OS The TS is mandatory ASAP, always re-run. There is an existing OS on the drive that I want to image over. If I wipe the drive first the TS will eventually start. Obviously I am doing something wrong, as I should not have to wipe the drive to run a TS using pxe boot.