PENDING Windows 10 PXE deployment issues

[Marc Murphy]

Hello!

I'm currently having an issue deploying windows 10 via PXE. Its running SCCM 1606. The client will boot up get an IP and contact the WDS server but it wont find the WinPE image. The image is on the server. I've already removed and redistributed it. I've removed the PXE role from the DP and readded. I've even removed the DP role and readded it. The Boot Image is set to "Deploy this Boot image...". Still gives the same error.

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16792882" ServerName=""><Machine><ClientID>GUID:37705003-F519-4C59-9592-73B0F3E03976</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="WAL20010" OfferIDTime="10/20/2016 9:46:00 AM" PkgID="WAL0002D" PackageVersion="" PackagePath="http://WAL-SCCM-OSD1.ad.edc.org/SMS_DP_SMSPKG$/WAL00027" BootImageID="WAL00027" Mandatory="0"/></ClientIDReply>
SMSPXE 10/20/2016 10:12:19 AM 2264 (0x08D8)

00:21:CC:64:94:F8, 70E6BA01-5125-11CB-80F6-BC22C629C2EE: found optional advertisement WAL20010 SMSPXE 10/20/2016 10:12:19 AM 2264 (0x08D8)

Looking for bootImage WAL00027 SMSPXE 10/20/2016 10:12:19 AM 2264 (0x08D8)

Any help would be greatly appreciated.

 

[Prajwal Desai]

The client will boot up get an IP and contact the WDS server but it wont find the WinPE image - Could you attach a screenshot ?.

 

[Marc Murphy]

That is correct.

 

[Prajwal Desai]

That's weird. I suspect the win PE image is corrupt or might have issues. Does the BIOS clock on the target computer match the clock on the SCCM server?.

 

[Marc Murphy]

The time is with in a 2 or 3 seconds. When this issue first started the system was running SCCM 2012R2. It was suggested by a coworker to upgrade to 1606 since i'm trying to deploy windows 10. First I tried just updating the ADK to Windows 10. So when I did that I created new boot images. Same issue. So I did the whole upgrade and installed the latest ADK. Which again I created new boot images. Still the same issue.

 

[Travis]

You are hitting F12 at that prompt in your screenshot right? That looks like you aren't and letting it timeout from your screenshot.