nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sccm

Lee H

Hi

Is anyone good with SCCM

PXE-E53: No boot filename received

I restarted service "Windows deplotment services server" closed SCCM then i was able to get an image deploying to 1 laptop, then I try another laptop and get error again

Only been using this since last Friday so am not very clued up on it

Thanks

Find more posts tagged with

SAVE $250 on Your Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Boot Camps

Comments

Claymoore

I'm studying SCCM now, but I don't have a lot of experience with it yet...

Are DHCP and WDS running on the same server?

Do you have more than one PXE server on that network?

Have you distributed your boot image to the DPs?

Planning for PXE Initiated Operating System Deployments
Administrator Workflow: PXE Deployment

jmritenour

Has the PXE boot option been defined in DHCP? Is the SCCM server on the same subnet as the computers you're trying to image?

This might shed some light on the situation. Cannot get PXE boot from SCCM | Teh Wei King's System Center Blog

Lee H

Are DHCP and WDS running on the same server? No

Do you have more than one PXE server on that network? No

Have you distributed your boot image to the DPs? Yes

Has the PXE boot option been defined in DHCP? Yes

Is the SCCM server on the same subnet as the computers you're trying to image? Yes

As I said before once I have imaged 1 laptop and closed the SCCM app I then restart the service "Windows deplotment services server" it will work again but only for 1 more image then I have to do it all again, 1 laptop at a time is not very productive

Thanks for you help anymore ideas please let me know

Lee H

I am able to do 2 at a time by turning them on at the exact same time so they both start downloading the image file together, if I had 3 arms I could do 1 more

Any ideas what this could be or is there a particular log file that would give me a clue

Thanks

jmritenour

There should be a pxe related log in X:\Program Files\SMS_CCM\Logs.

Lee H

Had a quick sniff round the log files and couldnt find anything that give a clue

None of the log file names had PXE in them

Claymoore

Look for the SMSPxe.log file or the MP_ClientIDManager.log file.
List of Log Files in Configuration Manager 2007

Lee H

In SMSPxe.log (now i see PXE doh!!!)

I find this line about a thousand times, is this anything to be concerned about

<![LOG[Unable to delete folder C:\Windows\TEMP\PXEBootFiles\ (0x80070091). Retry after 1 seconds]LOG]!><time="14:10:02.547+000" date="11-04-2010" component="smspxe" context="" type="1" thread="5308" file="ccmfile.cpp:1131">

Lee H

Also have just found this

<![LOG[WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode.]LOG]!><time="14:12:03.403+000" date="11-04-2010" component="smspxe" context="" type="3" thread="5672" file="varhdl.cpp:389">
<![LOG[WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode.]LOG]!><time="14:12:03.403+000" date="11-04-2010" component="smspxe" context="" type="3" thread="5672" file="varhdl.cpp:405">
<![LOG[WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode.]LOG]!><time="14:12:03.403+000" date="11-04-2010" component="smspxe" context="" type="3" thread="5672" file="varhdl.cpp:414">
<![LOG[WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode.]LOG]!><time="14:12:03.403+000" date="11-04-2010" component="smspxe" context="" type="3" thread="5672" file="varhdl.cpp:423">

Have no idea what this mean because I never set anything up, I just kickstart the image to the laptop, the guy who did set this up is now off on holiday for 3 weeks

Thanks for your help guys its much appreciated

jmritenour

Lee H wrote: »

In SMSPxe.log (now i see PXE doh!!!)

I find this line about a thousand times, is this anything to be concerned about

<![LOG[Unable to delete folder C:\Windows\TEMP\PXEBootFiles\ (0x80070091). Retry after 1 seconds]LOG]!><time="14:10:02.547+000" date="11-04-2010" component="smspxe" context="" type="1" thread="5308" file="ccmfile.cpp:1131">

So, it looks like what's happening - disclaimer, I'm not a SCCM expert by any means - is that a temp file is being created, but not being deleted, probably due to some permission mish-mash. I'm guessing that the next computer that comes along wants to create a temp file with the same name, and it's not happening because the first computer has a lock on the file/folder, or at least the server thinks it does. Resarting WDS service resets it all, and everything's kosher until you start the next one, then the cycle repeats itself.

If you still feel like messing with this, have a look at this thread on Technet. I don't know that it's the exact same situation you're dealing with, but I see a lot of common threads, and this might yet some results for you.

The second set of warnings from the log you posted could present a problem if SCCM is running in native mode, but even then, I don't think it would generate the problem you're seeing.

Lee H

Thanks for your help i will look into that on Monday

Lee H

Hi

Not sure if these lines of text are what I should be seeing if anyone can see anything like a clue can you please let me know

This is at the point of PXE boot failure

<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 b2bbb0]LOG]!><time="09:24:03.135+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">
<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 17ef570]LOG]!><time="09:24:05.166+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">
<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 bc1970]LOG]!><time="09:24:09.176+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">
<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 58ef30]LOG]!><time="09:25:48.678+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">
<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 b26d30]LOG]!><time="09:25:50.669+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">
<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 17fecf0]LOG]!><time="09:25:52.701+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">
<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 bcb930]LOG]!><time="09:25:56.710+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">
<![LOG[[192.010.009.223:67] Recv From:[000.000.000.000:68] Len:548 58c6b0]LOG]!><time="09:26:04.730+000" date="11-09-2010" component="smspxe" context="" type="0" thread="5852" file="smspxe.cpp:663">

Thanks

jmritenour

Sorry, no clue - I've seen those lines in logs from systems that are working fine...