the error above is because you are tryiung to boot x64 uefi hardware but configuration manager is responding with an x86n boot wim, most likely because the last task sequence deployed to your OSD collection contains an x86 boot wim, think of LIFO, last in, first out, so if you last deployed a task sequence with an x86 boot wim, it'll be the first to reply, and it will produce that error
to fix, either add your 64 uefi hardware to their own collection that HAS an x64 boot wim based task sequence deployed to it or deploy your x64 boot wim task sequence AFTER the x86 one, the end result of the latter is your other machines will pull the x64 boot wim down and then stage the x86, On Wed, Nov 19, 2014 at 5:33 PM, Bradley, Matt <[email protected]> wrote: > 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? > >
