[SCCM 2010] PXE & IP-Helpers

[CHiLL]

Since upgrading to SCCM 2010, I'm having issues with the distribution point, where known working Task Sequences were failing due to a variety of reasons, such as content not available, etc. As part of my diagnosing, I removed the Distribution Point and reinstalled it. I took this opportunity to remove the DHCP options 66 & 67 for PXE boot and look at the IP-Helper route. I have added the IP addresses of both DHCP servers and the SCCM server on the core switch, and all edge switches (HP ProCurve range). However, the client I'm testing with won't PXE, it's just sat on the DHCP screen until it times out. SMSPXE.log reports the following:

 

Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 762B58D7
Sec Since Boot: 16 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.022.100.001
Addr: ec:b1:d7:58:2b:76:
Magic Cookie: 63538263
Options:
 Type=53 Msg Type: 1=Discover
 Type=55 Param Request List: 0102030405060b0c0d0f10111216171c28292a2b3233363a3b3c42438081828384858687
 Type=57 Max Msg Size: 04ec
 Type=97 UUID: 003db2dcb4cc44e86484eeb8d042385490 

PXE::MP_GetList failed; 0x80070490
PXE::MP_LookupDevice failed; 0x80070490
PXE::MP_GetList failed; 0x80070490
PXE::MP_ReportStatus failed; 0x80070490
PXE Provider failed to process message. 
Element not found. (Error: 80070490; Source: Windows)
EC:B1:D7:58:2B:76, B4DCB23D-44CC-64E8-84EE-B8D042385490: Not serviced.

 

1. Does the IP-Helper need to be configured on all edge switches, or just the core?
   
2. Do I just specify the IP of the server for helpers, or do I have to include the ports?
   

 

I can't figure out what I'm missing to get IP-Helpers to work. If I put the DHCP scope options back in, it will PXE but then have problems loading the boot image.

 

I have completely removed the PXE and WDS roles from the server and reinstalled them, which didn't resolve the issue.

Edited February 26, 2021 by CHiLL

[Steve21]

What version were you running previously? There was some changes to PXE back in 18XX something that enabled new options in SCCM that can clash unless you make some changes to regenerate boot images, which may be linked to why it's having problems with your boot image even if you change the helper back etc

 

Try going to Admin->DP->Properties->Disable PXE support

 

Wait a few minutes (it'll uninstall WDS), and then rename RemoteInstall folder, restart the server, re-enable PXE and wait again while it reinstalls WDS and regenerates RemoteInstall

 

(Obviously make sure you have backups as normal before any changes to SCCM as always )

 

-Edit and regarding the IP helper the short answer is it's only needed on whatever is routing between subnets/VLANs so normally core only unless you have multiple L3s

 

Steve

Edited February 26, 2021 by Steve21

[CHiLL]

What version were you running previously? There was some changes to PXE back in 18XX something that enabled new options in SCCM that can clash unless you make some changes to regenerate boot images, which may be linked to why it's having problems with your boot image even if you change the helper back etc

 

Try going to Admin->DP->Properties->Disable PXE support

 

Wait a few minutes (it'll uninstall WDS), and then rename RemoteInstall folder, restart the server, re-enable PXE and wait again while it reinstalls WDS and regenerates RemoteInstall

 

(Obviously make sure you have backups as normal before any changes to SCCM as always )

 

Steve

I was on 2006 prior to the 2010 upgrade. Unfortunately I've already tried both rebuilding the boot image, including with the latest 20H2 ADK and also disabling PXE and re-enabling it, neither worked. I also disabled PXE and manually uninstalled WDS and renamed the RemoteInstall folder, again, no luck

[Steve21]

Can you reach the MP from a browser ok?

 

http://ServerName/sms_mp/.sms_aut?mplist

 

Steve

[CHiLL]

Can you reach the MP from a browser ok?

 

http://ServerName/sms_mp/.sms_aut?mplist

 

Steve

HTTP is Access Denied

HTTPS works:

9040

[Steve21]

Are you using PKI certs between clients on your server for management and distribution? Might just be worth checking your site properties for communication security if you weren't expecting that

 

Steve

[CHiLL]

Are you using PKI certs between clients on your server for management and distribution? Might just be worth checking your site properties for communication security if you weren't expecting that

 

Steve

They're just self-signed certificates.

[FN-GM]

To answer your question to on about helpers. They only need to be on the layer 3 switches (core).

 

Have you checked boundaries? Have you also distributed both x86 and x64 boot images (even if you are only using x64).

[CHiLL]

To answer your question to on about helpers. They only need to be on the layer 3 switches (core).

 

Have you checked boundaries? Have you also distributed both x86 and x64 boot images (even if you are only using x64).

Our core is a HP ProCurve 5406zl (layer 3) and our edge switches are HP ProCurve 2530 (which are layer 2 I believe). The IP helpers specify my domain controllers for DHCP and the SCCM server. When I remove the DHCP scope options, the client just sits waiting on the DHCP screen when attempting to PXE boot. Then times out with PXE-53: No boot filename received. SMSPXE.log can see a connection attempt, but the IP reads as 000.000.000.000. Whereas with the DHCP scope options, it will show the client's DHCP address.

 

My boundaries haven't changed in 5 years, but they are defined as: 10.22.0.1 - 10.22.255.254 (which covers all our VLANs) and our Active Directory site. Both have been combined into a boundary group.

[FN-GM]

Have you distributed both boot x64 and x86 images?

[CHiLL]

Have you distributed both boot x64 and x86 images?

Oh sorry, missed that bit. Yeah, both x86 and x64 are distributed.

[FN-GM]

Are you using legacy BIOS or UEFI?

[CHiLL]

Are you using legacy BIOS or UEFI?

We have some clients that operate BIOS and some UEFI.

[CHiLL]

I'm one step further, though not entirely sure how. IP helpers are in place on the core switch and none of the edge switches.

 

With the DHCP scope options disabled and using IP Helpers, the client was just hanging. I managed to get the IP helper method to get an IP by changing a setting on WDS on the SCCM server: WDS > Server > Properties > PXE Response > Respond to all client computers (known and unknown). This was originally set as 'Do not respond to any client computers'.

With DHCP scope options defined, the client was getting a DHCP address.

 

Now I have an IP only using IP Helpers, the client is getting the same error that it was when using DHCP scope options.

 

The message displayed is:

Downloaded WSDNBP from  

Press F12 for network service boot
Architecture: x64
Contacting Server: 
TFTP Download: boot\x64\pxeboot.n12

Once that downloads, I get a Windows Recovery error screen saying:

Your PC/Device needs to be repaired

The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture.

File: \Tmp\x86x64{GUID}.bcd
Error code: 0xc0000098

You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.

I have attempted to rebuild the boot image from the ADK.

I've redistributed the ADK on the DP.

I have re-deployed my x64 TS to all unknown computers.

I've unchecked 'Deploy this boot image from the PXE-enabled distribution point', waited, and then re-enabled it.

Edited March 1, 2021 by CHiLL

[savi007]

Hi Chill

Did you got the solution for this issue yet? i am stuck in exact same situation after the sccm upgrade.

[georgeescott]

If you've recreated the boot image, have you made sure it's set on the Task Sequence?

Software Library -> Operating Systems -> Task Sequences -> Right-click 'Your task sequence here' -> Properties -> Advanced Tab -> Tick 'Use a boot image' and select the appropriate one.

 

Failing that, I've troubleshooted PXE issues with Port Mirroring and Wireshark (I do it in Hyper-V with a test VM https://www.vembu.com/blog/hyper-v-port-mirroring/) so you can see the response from SCCM to see what's going on.