SOLVED Issue with PXE booting

[manesh1983]

I have facing an issue with PXE booting. While trying to boot through PXE it shows PXE--T00: Failed to Open File (Also getting PXE-E36,PXE-M0F), but after delete the target machine from SCCM Administration console -> Assets and Compliance -> Devices, I can able to boot with the PXE service. Is it any solution for avoid the manual device deletion from SCCM?

 

[Prajwal Desai]

Did you review the PXE logs to determine what's happening during the PXE boot?

 

[manesh1983]

Thanks for the reply. I have resolved this issue with the one change in client machine BIOS configuration, there was a setting called Intel "VMD", turned it off and that PXE boot worked and successfully updated the OS.

 

[manesh1983]

I am facing an issue with PXE booting. While trying to boot through PXE it shows PXE--T00: Failed to Open File (Also getting PXE-E36, PXE-M0F), but after deleting the target machine from SCCM Administration console -> Assets and Compliance -> Devices, I can able to boot with the PXE service. Is there any solution to avoid the manual device deletion from SCCM?

please find the SMSPXE log file. After getting this error I searched for this Mac address in the SCCM management console ->Devices -> Search with that Mac address and delete that system. After this step I rebooted the same workstation, in that time it was perfectly booted with PXE.

Can you please give me a solution to avoid the device deletion every time?

 

[Prajwal Desai]

Have you been manually adding the devices using Mac address in SCCM for PXE boot?.

 

[manesh1983]

Have you been manually adding the devices using Mac address in SCCM for PXE boot?.

No.. I am trying to update the existing device's OS build from 1903 to 22H2.

 

[Prajwal Desai]

In my previous organization, I encountered the same issue where I had to delete the devices from the ConfigMgr database for PXE boot to work. We were manually importing the devices into SCCM using a Mac address for imaging. I had to log a call with Microsoft support to troubleshoot this issue.

 

[manesh1983]

Thanks for the update. I will log the call regarding this into Microsoft support. Request you to close this tread as resolved