SOLVED SCCM Boot Image Windows PE reboots without error

[Curtis Parker]

I have recently updated to the the latest version of SCCM from 2012 R2 to 1601 I believe. After doing this and installing the latest Windows 10 ADK I created the new boot images as recommended. When I try to boot to the 64 bit image it gets to initializing network and then reboots. If I boot to the 32 bit image it gets me to a x:\windows\system32 prompt and doesn't go any further. It doesnt appear to be a network driver error because if i run ipconfig at the prompt I get an IP address. Any ideas?

Thanks
Curtis Parker

 

[Prajwal Desai]

From my understanding you have not added the correct drivers in your boot image. Just make sure you update your distribution points after doing so.

 

[Curtis Parker]

Unfortunately even after adding the drivers and updating the DPs I am still getting the same result. This is happening on both a test VM and also on a workstation that I have attempted to test on.

 

[Prajwal Desai]

For a test VM (hyper-v / vmware ) you don't need any drivers. you could remove all the drivers (you could just keep the vmware drivers - https://prajwaldesai.com/import-vmware-drivers-to-your-sccm-boot-image/) > update the boot images > test the OSD on a VM first.

 

[Curtis Parker]

I am still getting the same results. It is showing "Prepairing network connection and then rebooting". Also, it doesn't seem to pick up the vmxnet driver. If I do the F8 and run ipconfig I do not get an IP address when using vmxnet. However, I do if I switch the network adapter to the E1000. It does the same on both though with showing preparing network connections and then rebooting.

 

[Curtis Parker]

I have attached my smsts.log file from the VM. This is with using the E1000 network adapter.
Thanks
Curtis

 

[Prajwal Desai]

Okay,

Set command line: "X:\sms\bin\i386\smstftp.exe" -i 192.168.0.29 get X:\sms\data\variables.dat TSPxe 6/28/2017 1:33:55 PM 1416 (0x0588)
Executing command line: "X:\sms\bin\i386\smstftp.exe" -i 192.168.0.29 get X:\sms\data\variables.dat TSPxe 6/28/2017 1:33:55 PM 1416 (0x0588)
Process completed with exit code 1 TSPxe 6/28/2017 1:33:55 PM 1416 (0x0588)
Succesfully removed firewall rule for Tftp TSPxe 6/28/2017 1:33:55 PM 1416 (0x0588)
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185) TSPxe 6/28/2017 1:33:55 PM 1416 (0x0588)
Failed to download pxe variable file. Code(0x00000001) TSPxe 6/28/2017 1:33:55 PM 1416 (0x0588)
PxeGetPxeData failed with 0x80004005 TSPxe 6/28/2017 1:33:55 PM 1416 (0x0588)


Check this - https://prajwaldesai.com/community/threads/task-sequence-issue.116/

 

[Curtis Parker]

I checked on this. I did not previously have any IP helpers set for the PXE server just the one for my DHCP. I added one for the PXE as well and still getting the same result.

 

[Prajwal Desai]

Try the resolutions mentioned in this thread. Let me know if it helps.

 

[Curtis Parker]

Prajwal. Tried the process of removing distribution point. Reinstalling WDS and readding distribution point roll. Unfortunately, still the same result.

 

[Curtis Parker]

I just also attempted to boot using a CD ISO media file without PXE boot. getting similar results after typing in the password. Here is the smsts.log file from that.

 

[Curtis Parker]

After trying several things have had no luck getting issues resolved. I have ended up reverting back to snapshot of older version of SCCM that was functional so I can continue with imaging and other summer projects. May have to reattempt this down the road sometime possibly as a fresh rebuild. But for now will have to move on to other things as I have spent too much time on this already. Thanks for all of your help though Prajwal.

 

[Prajwal Desai]

@Curtis Parker Thanks for the update