You mention that only the x64 boot image has been deployed to your PXE server. Whether you use them or not, You must have both an x86 and an x64 PXE-enabled boot image deployed to the distribution point for the PXE deployment to succeed.
Check out the "Distributing Boot Images to the Distribution Point" section on this page: https://technet.microsoft.com/en-us/library/hh397405.aspx Try deploying both to your DP and see if you have the same issue. Jerry From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Wednesday, January 21, 2015 8:43 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: SCCM 2012 R2 and PXE boot Of course, your WDS needs to be working in general. But once you have it going then you will need to deploy your TS to the Unknown Computers collection so your unknown machine can PXE boot. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden Sent: Wednesday, January 21, 2015 8:34 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: SCCM 2012 R2 and PXE boot 1. Just the default x64 image on the PXE enabled DP. 2. It is assigned to this sequence. (Using Windows Noob set of instructions.) 3. It is deployed to all systems. 4. Unknown machine at this point. Reviewing the SCCM 2012 server. WDS is getting a 1067 when trying to start. No WDS, no PXE. GoogleFU shows KB2905002 helps but that hotfix is unavailable at the moment from Microsoft. PXE-032 TFTP timeout PXE- Abort ^ Makes sense with WDS being down. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Wednesday, January 21, 2015 8:27 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: SCCM 2012 R2 and PXE boot What exactly is happening when it fails? Are you getting a PXEAbort, or is it attempting and the boot process is failing at some point? Some basics to check. 1. Do you have both the 64bit and 32bit boot images on your PXE enabled DP? 2. Is one of those boot images the one assigned to your task sequence? 3. Is your task sequence deployed/advertised to a collection? 4. Is the machine you're trying to PXE boot a member of that collection? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden Sent: Wednesday, January 21, 2015 8:05 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] SCCM 2012 R2 and PXE boot I am trying to PXE boot my first workstation to SCMM 2012 R2. My PXE boot on my workstation sees my DHCP server. I have added 066 and 067 to the DHCP options but the workstation fails to boot. It gets an address from the DHCP server then it trys to TFTP?? Then it fails. I see it in the DHCP lease but I see nothing in the SMSPXE.log on the SCCM 2012 server?? I have never booted to PXE in the past so I am a total virgin in this area. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues