<div>
Hi,<br />
<br />
You have the answer (twice): (1) Ensure that the server has boot images installed for this architecture.<br />
and (2) The PXE server processed a request from a client of architecture x86x64<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;^^^^^^^<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; this bit is wrong - it is either x86 or x64. <br />
<br />
Whichever one you have, you need the other architecture. For <b>PXE booting you need BOTH boot architectures available on the PXE enabled DP </b>regardless of the final OS you are deploying. Distribute the one that is missing and it will work. I am going to guess you didn't distribute the 32-bit boot WIM at a guess.<br />
<br />
Read this article for the nitty gritty troubleshooting (including guidance to use IPHelpers) <br />
<a href="https://blogs.technet.microsoft.com/configurationmgr/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007/" rel="ugc nofollow">https://blogs.technet.microsoft.com/configurationmgr/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007/</a><br />
but the key steps are 16/17.<br />
<br />
PXE has not changed (much) since 2007 so it all still applies perfectly.<br />
<br />
Mike
</div>


<div>
Thanks, Mike.<br />
<br />
I have both boot images one for 64 an another for 32.<br />
IP helper is working, PC can get IP from DHCP.<br />
About the error on &nbsp;WDS &nbsp;this is literal from the server log &quot;The PXE server processed a request from a client of architecture x86x64. &nbsp;However, there were no boot images installed for this architecture. &nbsp;PXE clients of this architecture will not be able to complete the boot process successfully. &nbsp;To resolve this problem, add at least one boot image for this architecture.&quot;<br />
I try a x32 boot image in the task sequence but I got same error.<br />
System was working fine Friday and Monday I have this error.
</div>


<div>
Hi,<br />
<br />
OK, that changes things slightly. I have to ask now &quot;has anything changed&quot;? If it was working Friday it would still be working unless either someone changed something or, less likely, files corrupted on the DP.<br />
<br />
Cause 1: someone changed on of the boot wims<br />
Fix 1: revert to previous copy of WIMs; if no backup was made (available) go to Fix 2<br />
<br />
Cause 2: unknown/corruption<br />
Fix 2: delete both boot WIMs for the DP and re-distribute.<br />
<br />
As a side note, how many drivers are in the boot WIMs? Is this a new setup or has it been going for a long time?<br />
Best practise, especially for W10, is don't bother adding any drivers at all! The chances are high that W10 native WinPE drivers are already there and will work. Point 2 - you only need disk and network drivers. Don't add Bluetooth, wireless, audio, etc.<br />
<br />
The point is, it might be a good time to review the boot WIMs and slim them down. The result is booting will be faster, so the end-user experience is better and just &quot;feel&quot; better.<br />
<br />
I would also say PXE itself looks to be working fine - it is purely the boot WIM needing to see and recognise both architectures before it proceeds to boot with your one. <br />
<br />
<br />
Mike
</div>


<div>
I think about that but I only redo the x64 and I added the Dell WinPE drivers. I will do your plan redo both images without drivers, this Wednesday. I will let you know. &nbsp;Thanks for your help.
</div>


<div>
I recreate both images one x64 and another x86 but I have the same error.<br />
I used:<br />
COPYPE.CMD x86 c:\WINPE86\<br />
COPYPE.CMD amd64 c:\WINPE64\<br />
WDS has these two errors:<br />
1- &quot;The PXE server processed a request from a client of architecture x86x64. &nbsp;However there were no boot images installed for this architecture. &nbsp;PXE clients of this architecture will not be able to complete the boot process successfully. &nbsp;To resolve this problem, add at least one boot image for this architecture.&quot;<br />
2- &quot;The PXE server processed a request from a client of architecture x86. &nbsp;However there were no boot images installed for this architecture. &nbsp;PXE clients of this architecture will not be able to complete the boot process successfully. &nbsp;To resolve this problem, add at least one boot image for this architecture.&quot;<br />
<br />
Any other suggestion.<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/09_w36/1381063/Boot-images.PNG" target="_blank" class="file-inline" title="Boot-images.PNG (32 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Boot-images.PNG</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2018/09_w36/1381064/bootimage-PXE-enable.PNG" target="_blank" class="file-inline" title="bootimage-PXE-enable.PNG (21 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>bootimage-PXE-enable.PNG</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2018/09_w36/1381066/Properties-distribution-point.PNG" target="_blank" class="file-inline" title="Properties-distribution-point.PNG (17 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Properties-distribution-point.PNG</a>
</div>


Boot-images.PNG

Properties-distribution-point.PNG

bootimage-PXE-enable.PNG

<div>
Hi,<br />
<br />
I can see from the screenshot that you unfortunately have already deleted the default boot images from Microsoft. If you hadn't I would say use those.<br />
As it's too late, did you follow the steps as Anders describes here?<br />
<br />
<a href="https://www.andersrodland.com/create-sccm-boot-image-using-dism/" rel="ugc">https://www.andersrodland.com/create-sccm-boot-image-using-dism/</a><br />
<br />
If not, just delete the current ones and follow those steps. WDS and PXE look fine. As you have already said everything was working, how long was it working for?<br />
<br />
There is an excellent troubleshooting guide here:<br />
<a href="https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007/" rel="ugc">https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007/</a><br />
<br />
Other than that can you attach the full SMSPXE.log - redact server names if you like.<br />
<br />
Mike
</div>


<div>
This system is working for three years.<br />
Here is the SMSPXE.log<br />
All my boot images were created after the error. &nbsp;I delete all boot images created before the error.<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/09_w36/1381918/SMSPXE.log" target="_blank" class="file-inline" title="SMSPXE.log (328 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>SMSPXE.log</a>
</div>


SMSPXE.log

Oscar Powers

<div>
These are are my actual steps:<br />
1) Untick the &quot;Enable PXE option&quot; on the DP. Answer yes that you want to remove the Windows Deployment service.<br />
2) Remove the boot images from your distribution point<br />
3) After few minutes delete the contents of %windir%\temp<br />
4)Reboot server<br />
5)Remove WDS role<br />
6)Reboot server<br />
7)Delete remoteinstall folder<br />
8)Re-install WDS role<br />
9) Reboot the server again.<br />
10)Add the PXE point back by checking the box on the DP properties<br />
11)Distribute the boot images again and then try PXE.<br />
<br />
Thanks, Mike for all your help.
</div>


<div>
Glad you got it working. It can be frustrating but such a relief when it's back!
</div>


<div>
<div class="content wysiwyg-content">
SCCM 2012, PXE boot stops working. I have SCCM version 1806.<br />
The contact with DHCP gets the IP address, next download WDSNBP from my SCCM server. &nbsp;Everything looks working fine until I got the line &quot;Press F12 for network service boot&quot;.<br />
&nbsp;if I press F12 I got this error: &quot;&nbsp;The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture. Error code:0x0000098&quot;<br />
Else the computer skips the image mode and goes to Windows.<br />
WDS has this error &quot;The PXE server processed a request from a client of architecture x86x64. &nbsp;However, there were no boot images installed for this architecture. &nbsp;PXE clients of this architecture will not be able to complete the boot process successfully. &nbsp;To resolve this problem, add at least one boot image for this architecture.&quot;<br />
If I use a DVD with the boot image the image process goes through without problems.<br />
Things that I tested:<br />
1-Disable PXE support on Distribution points waits for the server to remove the files, reboot and re-enable PXE again.<br />
2-Create a new boot image.<br />
3-Create a new task sequence.<br />
4-Remove support for unknown computers.<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/08_w35/1377625/SmartSelect_20180828-093032_Photos.jpg" target="_blank" class="file-inline" title="Computer Boot Screen (799 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>SmartSelect_20180828-093032_Photos.jpg</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2018/08_w35/1377626/20180828_081920.jpg" target="_blank" class="file-inline" title="Error when I try F12 for network boot (6.3 MB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>20180828_081920.jpg</a>
</div>
</div>


SmartSelect_20180828-093032_Photos.jpg

20180828_081920.jpg

SCCM 2012, PXE boot stops working. I have SCCM version 1806.
The contact with DHCP gets the IP address, next download WDSNBP from my SCCM server.  Everything looks working fine until I got the line "Press F12 for network service boot".
 if I press F12 I got this error: " The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture. Error code:0x0000098"
Else the computer skips the image mode and goes to Windows.
WDS has this error "The PXE server processed a request from a client of architecture x86x64.  However, there were no boot images installed for this architecture.  PXE clients of this architecture will not be able to complete the boot process successfully.  To resolve this problem, add at least one boot image for this architecture."
If I use a DVD with the boot image the image process goes through without problems.
Things that I tested:
1-Disable PXE support on Distribution points waits for the server to remove the files, reboot and re-enable PXE again.
2-Create a new boot image.
3-Create a new task sequence.
4-Remove support for unknown computers.

SCCM 2012 PXE boot problems

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Systems Center Configuration Manager (SCCM, formerly known as Systems Management Server) is Microsoft’s system software for managing large groups of not only Microsoft computers, but those running other operating systems, such as Linux, OS-X, and various mobile technologies.