If your actually starting the task sequence, then, if you have enabled command line support on your boot WIM, you should be able to type F8 on your test system to open a command prompt. Check to be sure the system is getting an IP Address (ipconfig /all).
Also, you can check the SMSTS.LOG for errors. You can find it in one of the following locations, depending on how far your TS is getting: During OS Deployment Before your hard drive is formatted and partitioned X:\windows\temp\smstslog\ After your hard drive is partitioned formatted X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\ Within Windows before the SCCM agent is installed: C:\_SMSTaskSequence\logs\smstslog\ after the SCCM agent installed: C:\windows\system32\ccm\logs\smstslog\ When the Task Sequence completes For x86 C:\windows\system32\ccm\logs\ For x64 C:\windows\SysWOW64\ccm\logs\ Check here on how to enable command line support if you have not already: https://technet.microsoft.com/en-us/library/hh397288.aspx#BKMK_BootImagePropertyPage Jerry From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden Sent: Wednesday, January 21, 2015 1:19 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] RE: SCCM 2012 R2 and PXE boot Almost there. Starts the PXE install of windows 7 sp1 x64 and bombs out close to the end. x80004005. Looks like I need to add a drivers package? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Wednesday, January 21, 2015 11:19 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] RE: SCCM 2012 R2 and PXE boot Checkbox on boot image properties to deploy to PXE points! Sent from my Windows Phone ________________________________ From: Bradnan, Jerry<mailto:jerry.brad...@bluechip-llc.com> Sent: 2015-01-21 16:35 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: SCCM 2012 R2 and PXE boot No, you only need to deploy it to the DP. Only reference the Boot image you need in the TS. Jerry 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 10:24 AM To: 'mssms@lists.myitforum.com' Subject: [mssms] RE: SCCM 2012 R2 and PXE boot Do I make the x86 available in the task sequence in Software Library? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Gushue, William Sent: Wednesday, January 21, 2015 10:12 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: SCCM 2012 R2 and PXE boot I am pretty sure this is true. We had just recently rebuilt the PXE setup and left these out. One of our sites had these images installed and the others did not. Only the site with both boot images available had successful booting. The others did not until we re-added both boot images. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Bradley, Matt Sent: Wednesday, January 21, 2015 9:45 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: SCCM 2012 R2 and PXE boot Microsoft support once told me that you had to have both an x86 and x64 boot image available, even if you weren’t using the x86. Don’t know if that’s true or not. Also, make sure you’re fully patched to CU3. CU3 fixed an issue where it wouldn’t always serve up the proper architecture. That one in particular bit me hard, as it kept serving up x86 boot images to UEFI devices, and of course, that won’t work. CU3 fixed that. 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 7: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. ________________________________ ******************************************************************** This e-mail message is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited. Le contenu du présent courriel est privilégié, confidentiel et soumis à des droits d'auteur. Il est interdit de l'utiliser ou de le divulguer sans autorisation. ******************************************************************** 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. 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.
