I would follow on the instructions Neil provided. Basically, make sure your task sequences are using the desired boot image. i.e., double check the TS properties. . . Jeff From: mbrad...@quiktrip.com To: mssms@lists.myitforum.com Subject: RE: [mssms] Matching Processor Architecture Boot Image Not Found Date: Wed, 19 Nov 2014 17:30:44 +0000
Yes, those are checked. I checked that folder location…good tip. I’m only seeing two boot images. Both are x86 ones. One is a 6.2 version, and another the 6.3 version that came into place after the 2012R2 upgrade. I take it I should be seeing the x64 and I’m not. Not sure why. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jeff Poling Sent: Wednesday, November 19, 2014 10:46 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] Matching Processor Architecture Boot Image Not Found Just confirming. . .you have "Deploy this boot image from the PXE-enabled distribution point" checked on both boot images? And you have distributed the boot images to the PXE-enabled DP? Do you see the WIM files in the WDS RemoteInstall\SMSImages folder? Jeff From: mbrad...@quiktrip.com To: mssms@lists.myitforum.com Subject: [mssms] Matching Processor Architecture Boot Image Not Found Date: Wed, 19 Nov 2014 16:33:02 +0000 Has anyone seen that show up in the SMSPXE log before? I’m in a situation where I can’t PXE boot. Even though both the x86 and the x64 boot images are checked off for PXE deployment, I still get a failure. Even more strange, I can create a bootable USB drive and it is boots the task sequence selection just fine. This actually all started because I was getting a winload.efi error, perfectly screenshot by Niall here: http://www.windows-noob.com/forums/index.php?/topic/11135-why-do-i-get-a-winloadefi-status-0xc0000359-error-when-using-uefi-network-boot-in-system-center-2012-r2-configuration-manager The only difference is I indeed had both x86 and x64 checked off. As a test, I unchecked the x86, tried to PXE, it failed due to the requirement both x86 and x64 be available, and then rechecked the x86 image availability again, and then now I’m getting this. I’m tired updating the distribution points on both images, but I’m still stuck with nothing to boot. Any ideas?
