SCCM 2012 Can't Boot from PXE 0xC0000001

[smmb]

Hi All,

 

I followed the tutorials step by step, for sccm install and Seven osd, capture have been successful.

I create a new task sequence for deploy seven, it begins installatio, and at firt restart

 

 

 

Then it proceeds to loading the \SMSboot\boot.sdi. Some times it fails right here other times it proceeds to \SMSImages\SBG00043\winpe.SBG00043.wim. Either way it gets a bit into the progress bar but always fails

SMSPXE.log

[Whisky]

Have you updated the network drivers.

[anyweb]

you need to grab the smsts.log from the failed pxe boot before the C0000001 message above appears (and after pressing f12),

so have you tried that ?

[smmb]

you need to grab the smsts.log from the failed pxe boot before the C0000001 message above appears (and after pressing f12),

so have you tried that ?

 

Kindly show me how to grab the file smsts.log before the message coming only have sort time after pressing f12 ?

[anyweb]

enable command support in your boot wim, then redistribute your boot images to the dp, once done, pxe boot again, and immediatly after pressing F12, once WinPE loads, press F8, then grab the logs from x:\windows\temp\smstslog\smsts.log

[Lightjm]

enable command support in your boot wim, then redistribute your boot images to the dp, once done, pxe boot again, and immediatly after pressing F12, once WinPE loads, press F8, then grab the logs from x:\windows\temp\smstslog\smsts.log

 

I tried these instructions and after repeatedly pressing F8, the command prompt does not show. I know this is enabled because it works on other models just not this one. I have loaded the drivers several times and still no go. I did notice that upon PXE boot the version shows 2.1.1.1 and my driver version is 2.1.1.27. Is this an issue or am I looking in the wrong place?

 

Thanks!!

[Lightjm]

Ok, I think I fixed my issue.

 

I was reading another thread and it was talking about the registry string RamDiskTFTPBlockSize. I had to lower my setting to 2048 instead of 8192 (I tried 4096 but it still did not work). I am wondering if the NIC cannot handle that block size.

 

Does this make since to any one?

[ludi2014]

Did you deployed X86 and X64 winpe boot images PXE DP points.

 

kind regard

Safet Grahic

http://www.learnmesccm.com/

https://www.linkedin...ahic/a0/842/b21

 

 

[Peter van der Woude]

Ok, I think I fixed my issue.

 

I was reading another thread and it was talking about the registry string RamDiskTFTPBlockSize. I had to lower my setting to 2048 instead of 8192 (I tried 4096 but it still did not work). I am wondering if the NIC cannot handle that block size.

 

Does this make since to any one?

 

Makes sense. Not everything can handle a bigger block size, that's why you should always test this very well when used in a production environment.

 

For an example of a situation that doesn't work, see: http://www.bctechnet.com/vmware-pxe-limitations/