Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING PXE Boot for SCCM won't boot, gets IP address then changes to Startup menu

  • Thread starter Thread starter mpowis
  • Start date Start date
  • Replies Replies 17
  • Views Views 11K

mpowis

Well-Known Member
Messages
66
Solutions
1
Reaction score
0
Points
6
I have checked many articles, refreshed certificates, changed recommended settings and i cannot get it to PXE boot for SCCM.
The client computer searches for DHCP over IPv4, it looks like it receives an address but then the screen flashes and it goes to the manufacturer startup menu and in the SMSPXE log file it doesn't display a client IP.
I then changed the secure boot settings from Legacy to Secure, same outcome, when i changed it back it changed to the DHCP search as if it were searching for WDS rather than SCCM PXE and i get access violation and TFTP Server error messages.
SMSPXE.log
============> Received from client: SMSPXE 01/02/2024 11:27:08 3300 (0x0CE4)
============> Received from client: SMSPXE 01/02/2024 11:27:08 6704 (0x1A30)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.002
Addr: 50:81:40:ae:21:31:
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: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:08 3300 (0x0CE4)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.001
Addr: 50:81:40:ae:21:31:
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: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:08 6704 (0x1A30)
50:81:40:AE:21:31, 0ADEFB83-55CF-F457-2A1D-6F2B33B4139C: Not serviced. SMSPXE 01/02/2024 11:27:08 6228 (0x1854)
50:81:40:AE:21:31, 0ADEFB83-55CF-F457-2A1D-6F2B33B4139C: Not serviced. SMSPXE 01/02/2024 11:27:08 3992 (0x0F98)
============> Received from client: SMSPXE 01/02/2024 11:27:12 6704 (0x1A30)
============> Received from client: SMSPXE 01/02/2024 11:27:12 3300 (0x0CE4)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.002
Addr: 50:81:40:ae:21:31:
Magic Cookie: 63538263
Options:
Type=53 Msg Type: 3=Request
Type=50 Requested IP: 010.085.041.010
Type=55 Param Request List: 0102030405060b0c0d0f10111216171c28292a2b3233363a3b3c42438081828384858687
Type=57 Max Msg Size: 04ec
Type=54 Svr id: 010.085.032.035
Type=97 UUID: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:12 6704 (0x1A30)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.001
Addr: 50:81:40:ae:21:31:
Magic Cookie: 63538263
Options:
Type=53 Msg Type: 3=Request
Type=50 Requested IP: 010.085.041.010
Type=55 Param Request List: 0102030405060b0c0d0f10111216171c28292a2b3233363a3b3c42438081828384858687
Type=57 Max Msg Size: 04ec
Type=54 Svr id: 010.085.032.035
Type=97 UUID: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:12 3300 (0x0CE4)
============> Received from client: SMSPXE 01/02/2024 11:27:49 3300 (0x0CE4)
============> Received from client: SMSPXE 01/02/2024 11:27:49 6704 (0x1A30)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.001
Addr: 50:81:40:ae:21:31:
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: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:49 3300 (0x0CE4)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.002
Addr: 50:81:40:ae:21:31:
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: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:49 6704 (0x1A30)
50:81:40:AE:21:31, 0ADEFB83-55CF-F457-2A1D-6F2B33B4139C: Not serviced. SMSPXE 01/02/2024 11:27:49 3992 (0x0F98)
50:81:40:AE:21:31, 0ADEFB83-55CF-F457-2A1D-6F2B33B4139C: Not serviced. SMSPXE 01/02/2024 11:27:49 6228 (0x1854)
============> Received from client: SMSPXE 01/02/2024 11:27:53 3300 (0x0CE4)
============> Received from client: SMSPXE 01/02/2024 11:27:53 6704 (0x1A30)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.001
Addr: 50:81:40:ae:21:31:
Magic Cookie: 63538263
Options:
Type=53 Msg Type: 3=Request
Type=50 Requested IP: 010.085.041.010
Type=55 Param Request List: 0102030405060b0c0d0f10111216171c28292a2b3233363a3b3c42438081828384858687
Type=57 Max Msg Size: 04ec
Type=54 Svr id: 010.085.032.035
Type=97 UUID: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:53 3300 (0x0CE4)
Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 3121AE41
Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.085.040.002
Addr: 50:81:40:ae:21:31:
Magic Cookie: 63538263
Options:
Type=53 Msg Type: 3=Request
Type=50 Requested IP: 010.085.041.010
Type=55 Param Request List: 0102030405060b0c0d0f10111216171c28292a2b3233363a3b3c42438081828384858687
Type=57 Max Msg Size: 04ec
Type=54 Svr id: 010.085.032.035
Type=97 UUID: 0083fbde0acf5557f42a1d6f2b33b4139c
Type=93 Client Arch: Intel x86PC
Type=94 UNDI: 010201
Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 01/02/2024 11:27:53 6704 (0x1A30)
 
Forgot to add this was a working setup, used for years and just stopped servicing connections last week, I also updated the console, but still have a few updates to install.
1706787897795.png
 
Was the PXE boot working earlier?. You can plan to install the latest update and get your ConfigMgr to latest version so that existing issues in the current version are resolved.
 
Hi,
the PXE was working earlier, I have run some updates, I now cannot finish the last update, it just sits there after updating the ODBC driver.
the SMSPXE log is now showing this:
1707140060299.png
 
Try this one last method: Uninstall the PXE, reboot the server, install it again and try..
Tried it, removed PXE, uninstalled WDS, deleted Remote install folder and cleared Temp folder, restarted and reinstalled readded boot images to dist point and tried again and still getting the same errors.
 
Why are you still using WDS and not PXE responder?. We switched to PXE responder because on latest server OS, the WDS always had issues.
 
Why are you still using WDS and not PXE responder?. We switched to PXE responder because on latest server OS, the WDS always had issues.
Its how the system was setup and has always worked, I tried the responder as well and that didn't make a difference.
 
We have tried all the troubleshooting steps (except MP re-install). I would recommend logging a case with MS support for this.
 
I have now got it on the PXE responder, I'm now getting winhttp invaid CN certificate but this isn't connected to the cloud, part of this it suggested the ODBC driver 18 could be an issue and to update config manager to the latest update which had originally got stuck on prereq checks but i have now cleared that and downloading the latest update again.
 

Forum statistics

Threads
7,135
Messages
27,868
Members
18,159
Latest member
jordysmits
Back
Top