SCCM 1806 PXE Responder Issues

[Selby]

Hi,

I've updated to 1806 with all the hot fixes applied and decided to turn on "Enable a PXE responder without Windows Deployment Service"  unfortunately it doesn't work and I've had to turn WDS back on which works.  Below is the lines from the SMSPXE log.

We have IP Helpers rather than using DHCP Scope options. 

 

PXE: BC:83:85:F5:0B:63: Parsed a discover/solicit packet.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: C76B7D02-EA50-B10F-5E89-8BEFAA6609C9: Client is 64-bit, UEFI, Firmware.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: Prioritizing local MP http://(our MP).    17/10/2018 16:24:14
Not in SSL    17/10/2018 16:24:14
Not in SSL    17/10/2018 16:24:14
Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="15673" ClientID="GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="1"/><ClientIDInfo ItemKey="16798564" ClientID="GUID:39A05B11-0A61-4CB5-8827-5052E9CD3191" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="2"/></ClientIDReply>
    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: System records:    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63:   15673, GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E, SMBIOS ID is a match, MAC Address is NOT a match.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63:   16798564, GUID:39A05B11-0A61-4CB5-8827-5052E9CD3191, SMBIOS ID is NOT a match, MAC Address is a match.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: Using system record 15673, GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E.    17/10/2018 16:24:14
PXE: Sending reply to 255.255.255.255, DHCP.    17/10/2018 16:24:14
 

[VinnieBaz]

On 10/17/2018 at 6:03 PM, Selby said:

Hi,

I've updated to 1806 with all the hot fixes applied and decided to turn on "Enable a PXE responder without Windows Deployment Service"  unfortunately it doesn't work and I've had to turn WDS back on which works.  Below is the lines from the SMSPXE log.

We have IP Helpers rather than using DHCP Scope options. 

 

PXE: BC:83:85:F5:0B:63: Parsed a discover/solicit packet.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: C76B7D02-EA50-B10F-5E89-8BEFAA6609C9: Client is 64-bit, UEFI, Firmware.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: Prioritizing local MP http://(our MP).    17/10/2018 16:24:14
Not in SSL    17/10/2018 16:24:14
Not in SSL    17/10/2018 16:24:14
Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="15673" ClientID="GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="1"/><ClientIDInfo ItemKey="16798564" ClientID="GUID:39A05B11-0A61-4CB5-8827-5052E9CD3191" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="2"/></ClientIDReply>
    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: System records:    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63:   15673, GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E, SMBIOS ID is a match, MAC Address is NOT a match.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63:   16798564, GUID:39A05B11-0A61-4CB5-8827-5052E9CD3191, SMBIOS ID is NOT a match, MAC Address is a match.    17/10/2018 16:24:14
PXE: BC:83:85:F5:0B:63: Using system record 15673, GUID:8D9AD297-22DE-49F9-96B6-F5E04C18297E.    17/10/2018 16:24:14
PXE: Sending reply to 255.255.255.255, DHCP.    17/10/2018 16:24:14
 

Any new info on this?

I was testing this out earlier and got it to work on our "primary" VLAN. We are using IP-helper and from what I can tell it´s configured the same way on all VLANs. Using WDS works fine on any VLAN byt SCCMPxe doesnt ?

[Selby]

No can't seem to find anything to suggest what is causing it.  I've also got something on TechNet but no update on that either but I've noticed there are a few people with the same issue.  I know everything is configured correctly as WDS work perfectly without any issues and all this is effectively doing is replacing that server role.

[VinnieBaz]

7 minutes ago, Selby said:

No can't seem to find anything to suggest what is causing it.  I've also got something on TechNet but no update on that either but I've noticed there are a few people with the same issue.  I know everything is configured correctly as WDS work perfectly without any issues and all this is effectively doing is replacing that server role.

We had some old DHCP options still present on the Scopes even though we are using IP-Helper, removing those got us running on one VLAN.

[Selby]

I've double checked to make sure but we don't have any old DHCP Scope Options.  Are you getting the same last line as i'm getting PXE: Sending reply to 255.255.255.255, DHCP ? 

[VinnieBaz]

13 minutes ago, Selby said:

I've double checked to make sure but we don't have any old DHCP Scope Options.  Are you getting the same last line as i'm getting PXE: Sending reply to 255.255.255.255, DHCP ? 

Indeed I am.

[SighBee]

I've just run into this. I found a thread on Reddit where a "MSFT Official" says this is a bug which is fixed in 1810: https://www.reddit.com/r/SCCM/comments/9fvol5/nupxe_not_booting/

 

[Selby]

Thanks Sighbee will just have to wait till 1810 becomes available to us to confirm it's fixed. 

[VinnieBaz]

Thansk! No point of troubleshooting this then