They all pick up the correct boot image and run the task sequence just fine. I can now successfully boot an x86 NON-UEFI machine, an 圆4 NON-UEFI machine, as well as a UEFI x86 machine. I also modified the Windows 8.1 task sequence to use the "Unknown 圆4 Computers" collection. I then modified the Windows 7 x86 task sequence to deploy to the "Unknown x86 Computers" collection. The collections each contain 1 member, the "圆4 Unknown Computer" and "x86 Unknown Computer", respectively. To get around the issue with publishing multiple task sequences to Unknown computers, I have created two Collections to try to separate the x86 Unknown Computers and 圆4 computers. So I need to be able to support Non-UEFI as well as UEFI PXE booting for both the x86 and 圆4 architectures. There are also both x86 and 圆4 non UEFI capable machines. I have a mixture of x86 (Latitude 10 tablets) as well as newer 圆4 UEFI machines. When you attempt to PXE boot in UEFI mode, the architecture of the boot image must match the architecture of the machine.
XCOM 2 PC 32 BIT ISSUE 64 BIT
I know I can boot the x86 image and deploy a 64 Bit OS. Therefore it would not always boot the correct architecture. However, this caused issues as SCCM was selecting the initial PXE boot image based upon the last deployment. I was initially deploying both the x86 and 圆4 task sequences to the "All Unknown Computers" group. No applications or anything special in the task sequence, just standard OS installation. One is a Windows 7 x86 sequence - using the x86 Boot Image.The other is a Windows 8.1 sequence - using the 圆4 Boot Image. I have two Task Sequences that I am testing. I have two boot images (x86 and 圆4), both are distributed to the DP's and Unknown Computer support is enabled. This is running in a test lab so it's a pretty simple setup at this time. The issue is only with 64-Bit machines using UEFI. I am having an issue with PXE boot while using SCCM 2012 R2. I have to apologize for the length of the post right up front.