Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING pxe-e16 no offer received

rankinf

Member
Messages
9
Reaction score
1
Points
3
Hello

We upgraded to SCCM 2107 5.00.9068.1008. After the upgrade our PXE is no longer working. We get an error showing:

Start PXE over IPv4
Station IP Address is (our internal ip range)
PXE-E16: No valid offer received

We took a look at the SMSPXE.log file and it has not updated since March of 2020. So, I am confused where to go next. Any assistance would be appreciated.
 

Attachments

if the smspxe.log is not updated that means it is created somewhere else. search for it on the pxe enabled distribution point. on the other hand try booting the laptop or desktop with another network card, like a usb network card or a docking station.
 
Hello,

The distribution point is the same server. There is no other network card and using a docking station wouldnt fix the problem as we have to image 50 machines.
 
would you search the server for smspxe.log. it could be located under windows folder but searching will definitly bring some hits
 
Made some progress. Found the wdsmgfw.efi in the \boot\x64 folder was missing. Copied a local version of it to the directory and now the pxe continues but fails stating that there is a problem now with the .wim file. In the updated log we see that
 
Hi,
I had the same problem and my problem was the certificate
I updated every certificate from Sha1 to SHA256

I am not sure if this helps you
 
Hello,

So we finally resolved the issue. We ended up doing the following:
1. Remove the PXE role
2. Remove the Multicast role.
3. Remove the WDS role(If installed manually).
4. Rebooted the machine.
5. DO NOT INSTALL WDS.
6. Renamed the RemoteInstall folder.
7. Reinstalled WDS (this will also re-create the Remoteinstall folder)
8. Enable the SCCM Multicast role and the SCCM PXE role.
9. Re-enabled the unknown machine option

After doing all that, PXE and the image began working again. What we are surmising is that the .wim files got corrupted somehow in the last patch to 2107 and PXE was broken somehow also in the upgrade.
 

Forum statistics

Threads
7,165
Messages
27,965
Members
18,264
Latest member
markmumford

Trending content

Back
Top