Hi,

Is there an change in PXE troubleshooting PXE PE boot issue, in 2012?

I cant find wat I am used to...

Hi,

the smspxe.log file is still there, either in the directroy you installed Configuration Manager \logs or in SMS_CCM\Logs directory.

Regards,
Jrgen

I cant find wat I am used to...

Is it a secret what you're missing? How should we help you if you don't tell the exact problem?

Hi,

One of our PXE point get some issue, I could not set my finger on it.

I could not find any log file and I expect an smspxe.log in D:\Program Files\SMS_CCM\Logs (Primary site server) so I think something is wrong. The PXE worked after I put .Net 4 on the server.

Is it a secret what you're missing? How should we help you if you don't tell the exact problem?

No secret but I am not sure by my self what state the DP server have. 

Today I add an new PXE server to our environment, but I still cant find any SMSPXE.log. Is there any configuration you can do to get SMSPXE.log.

browse to D:\Program Files\SMS_CCM\Logs (if you installed on D:\)

you may have to gain access to that folder..

once done, look for SMSPXE.log, do you see it ?

Thanks Niall,

No I dont have it, I even set up a new DP with an PXE today still no smspxe.log in D:\Program Files\SMS_CCM\Logs

you may have to gain access to that folder.. for the DP server or?

Also look at the System32 folder. You might find the SMSPXE.log file there. Sadly, there is a bug that causes the log file to end-up there sometimes.

I have found it in the System32 and c:\windows\ccm\log.

Just a side comment about PXE.. I noticed, that it is important, that you do things in right order in 2012.
1. Enable PXE support in boot images
2. Add PXE support in DP properties, it will add WDS role in Windows Server OS itself.
3. Distribute or redistribute boot images to DP.
4. In some scenario you might need to restart WDS service.

If the setup order is done in wrong order, you will get PXE-E53.

Hi

I still have that same issue - I followed Yannara's manual just above, but still don't see smspxe.log. Also in regedit in HKLM\software\Microsoft\SMS I don't have no PXE folder, so information about the logfile is not in registry.

PXE boot fails with PXE-E53.

WDS was restarted (I verified that it was installed by SCCM - and that is fine).

Any idea about what to look for?

best regards Soren

I noticed that the logfile was suddenly there - then I restarted the SCCM Server and the logfile is now missing again. Alsto PXE-E53 error on pxe client.

No evidence of something wrong in windows logfiles and WDS service is running.

Any ideas?

D:\Program Files\Microsoft Configuration Manager\Logs Folder if its a Site server.

If its a Remote Site System, then under the SMS_DP$ folder.

Hi,

I have just been looking at my SMSPXE.log file and found the error 'Could not find an Available boot image ASH00088.wim, this is strange as the boot image is on the server and it hasn't changed. I am in the middle of updating the DP's to see if this make a difference. If this doen't I will import a new boot image and see if that helps. 

Is the ASH00088.wim in the RemoteInstall\SMSimages directory on the server hosting the PXE role?

Just a side comment about PXE.. I noticed, that it is important, that you do things in right order in 2012.
1. Enable PXE support in boot images
2. Add PXE support in DP properties, it will add WDS role in Windows Server OS itself.
3. Distribute or redistribute boot images to DP.
4. In some scenario you might need to restart WDS service.

If the setup order is done in wrong order, you will get PXE-E53.

In my case it was Step 2.  I had enabled PXE support and this does install the WDS role on the SCCM server, but it requires a restart.

Check the distmgr.log to ensure it is installing the PXE role on your DP correctly?