SCCM 2007 PXE boot error – The SMS PXE Service Point does not have a boot image matching the processor architetcure

I recently came across an error in SCCM 2007 R2 when using the Operating System Deployment task sequence. I was trying to PXE boot and deploy an operating system, however it was continuously failing and the below error showing in the SCCM logs:

The SMS PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device..

Device MAC Address:<replaced_mac_address> SMBIOS GUID:<replaced_guid>. Boot
Image Architecture:0

And yes, ‘architetcure’ is spelt incorrectly, just as it is in the SCCM error logs!!

Eventually I realised that I hadn’t yet added the boot images to the PXE service point and a quick check of \\servername\SMSPXEIMAGES$ confirmed this because the folder was empty.

To add boot images to the PXE service point (taken straight from the Technet article http://technet.microsoft.com/en-us/library/bb932177.aspx):

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management /Operating System Deployment / Boot Images.

2. Run the Manage Distribution Points Wizard by right-clicking the boot image you want to add to the PXE service point, and then selectManage Distribution Points.

3. On the Welcome page, click Next.

4. On the Select Destination Distribution Point page, specify the task you want to perform, and then click Next.

5. On the Package page, select the PXE service point you want to copy the image to, and then click Next.

   The PXE service point displays in the list with the associated SMSPXEIMAGES$ shared folder displayed in the path.

6. On the Completion page, verify the boot image you are copying to the PXE service point, and then click Next.

7. On the Summary page, click Next.

8. To close the wizard, click Close.

Share/Save

Possibly related posts (auto generated):

1. x86 or x64 Boot Images during SCCM OS deployment
2. Error creating SCCM TS media
3. Exchange 2007 BuildToBuildUpgrade error