Weird SCCM WinPE Issue

[dan400007]

Morning,

 

I've got a weird SCCM error that I can't get to the bottom of. When booting from PXE or USB Media, WinPE will load and then immediately exit and reboot the system. Doesn't even stay online long enough to hit F8 and stop the reboot.

 

I've uninstalled and reinstalled ADK / WinPE.

Recreated the Boot Images, etc

 

It just doesn't work and I can't think of any reason why. Any suggestions or pointers?

 

Cheers, Dan

[FN-GM]

This usually means the device cannot get an IP address. The drivers might not be in Windows PE. If that is the issue injecting the wired NIC driver into the Windows PE image will fix it.

[dan400007]

Thanks, unfortunately I don't think it even gets to the point of trying to get an IP. Also happens with a Hyper-V VM.

[dmason2]

silly question but may be worth checking, after you've reinstalled winPE did you deploy the updated boot image out to the distribution point and wait till it succeeded?

[dan400007]

Yep, distributed to the DP's Ok.

[Whisky]

This usually means the device cannot get an IP address. The drivers might not be in Windows PE. If that is the issue injecting the wired NIC driver into the Windows PE image will fix it.

 

I would agree with this.

[clareq]

Do you have a Task Sequence deployed to that machine? I've had machines reboot if they can't find anything to apply.

[dan400007]

Yep, Task Sequence is deployed to the machine and the same thing happens for unknown computers.

 

It shouldn't be driver based issues as it happens with a Hyper-V too.

 

It's the speed at which the reboot happens that makes me think something is wrong with the boot images.

[clareq]

Anything in the SMSPXE.log on the server?

[dan400007]

No, nothing useful in the SMSPXE.log.

 

The client is correctly shown as an unknown client and is assigned the correct boot image and proceeds to PXE boot (tt's picking up the correct Management Point too). But, once it gets to WinPE it reboots before loading anything more than the background.

[clareq]

Does this help with the hyper-v machine? https://kickthatcomputer.wordpress.com/2014/06/03/configmgr-osd-fails-to-start-in-winpe/

[dan400007]

Thanks, not for this one unfortunately. Startup memory is configured to 1024Mb.