none
TFTP Download: smsboot\x64\pxeboot.com keeps repeating and repeating until turn off laptop

    Question

  • So trying to image a machine in a new office that we setup to be able to use SCCM for OSD.

    I get the following

    Architecture: x64

    WDSNBP Started  using DHCP Referral

    Contacting Server 10.6.10.88 (Gateway: 10.6.12.1)

    The details below show the information relating to the PEX boot request this computer. Please provide these details to your Windows Deployment Service Administrator so that this request can be approved.

    Pending Request ID: 19655

    Contacting Server: 10.6.10.88.

    Then the following below just keeps repeating and repeating until i power down the laptop.

    TFTP Download: smsboot\x64\pxeboot.com

    .

    TFTP Download: smsboot\x64\pxeboot.com

    .

    Tuesday, December 18, 2012 1:48 PM

Answers

  • No, you should remove them using the ConfigMgr console. This will properly clean up the files extracted from the WIM also by the PSP.

    Jason | http://blog.configmgrftw.com

    Wednesday, December 19, 2012 3:34 PM
  • That failure is normal.

    I would start by removing the boot images from the PSP and then reading them as its possible there is some corruption of the WIM from which the PSP extracts the necessary PXE boot files.

    Have you also disabled your AV product on the site server to make sure it's not getting in the way?


    Jason | http://blog.configmgrftw.com

    • Marked as answer by DMobley232 Thursday, December 20, 2012 4:12 PM
    Wednesday, December 19, 2012 2:05 PM

All replies

  • Does this happen on every system you try to PXE boot?

    Jason | http://blog.configmgrftw.com

    Tuesday, December 18, 2012 5:02 PM
  • Tried two computers and same problem.

    In the SMSPXE.log  I dont see any errors, but i do see some warnings:

    WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode. smspxe 12/18/2012 8:46:17 PM 3396 (0x0D44)
    WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode. smspxe 12/18/2012 8:46:17 PM 3396 (0x0D44)
    WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode. smspxe 12/18/2012 8:46:17 PM 3396 (0x0D44)
    WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode. smspxe 12/18/2012 8:46:17 PM 3396 (0x0D44)
    Saving Media Variables to "D:\RemoteInstall\SMSTemp\2012.12.18.20.46.17.0004.{857CAAB9-4E6B-45A6-8620-9BF3F91C87E5}.boot.var" smspxe 12/18/2012 8:46:17 PM 3396 (0x0D44)
    [010.006.010.088:4011] Recv From:[010.006.012.182:68] Len:303 183d830 smspxe 12/18/2012 8:46:34 PM 3336 (0x0D08)
    MAC=00:26:B9:AF:AA:2C SMBIOS GUID=4C4C4544-0038-4C10-8057-C6C04F324C31 > Device has been accepted. smspxe 12/18/2012 8:46:34 PM 3396 (0x0D44)
    [010.006.010.088:4011] Recv From:[010.006.012.182:68] Len:303 1352f70 smspxe 12/18/2012 8:46:54 PM 3336 (0x0D08)
    MAC=00:26:B9:AF:AA:2C SMBIOS GUID=4C4C4544-0038-4C10-8057-C6C04F324C31 > Device has been accepted. smspxe 12/18/2012 8:46:54 PM 3396 (0x0D44)

    Wednesday, December 19, 2012 2:59 AM
  • I searched "failed" and found

    Failed to read PXE settings.
    The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 12/18/2012 8:46:15 PM 3396 (0x0D44)

    Wednesday, December 19, 2012 3:08 AM
  • That failure is normal.

    I would start by removing the boot images from the PSP and then reading them as its possible there is some corruption of the WIM from which the PSP extracts the necessary PXE boot files.

    Have you also disabled your AV product on the site server to make sure it's not getting in the way?


    Jason | http://blog.configmgrftw.com

    • Marked as answer by DMobley232 Thursday, December 20, 2012 4:12 PM
    Wednesday, December 19, 2012 2:05 PM
  • AV is disabled and same issue.

    As far as removing the boot images, can i just browse to D:\RemoteInstall\SMSIMAGES\SMSPKG and delete The DEN00001 folder and DEN00002 folder which contain the .wiw files for x86 and x64 or is there a better process to follow?

    Wednesday, December 19, 2012 3:15 PM
  • No, you should remove them using the ConfigMgr console. This will properly clean up the files extracted from the WIM also by the PSP.

    Jason | http://blog.configmgrftw.com

    Wednesday, December 19, 2012 3:34 PM
  • So I did as you said and removed the wim and re-added and we now are prompted with the F12 and moving forward with our process. Thanks Jason.
    Wednesday, December 19, 2012 5:34 PM