SCCM - PXE - Unable to enter OSD

[newpersn]

Hello

 

We just had some network work done and trying to fix our SCCM server pxe boot so we can reimage our IT Rooms,

 

I have added options 066 and 067 in and the server tries to pxe boot, The option to enter OSD goes too quick. (Not even tapping enter allows me to get there) 

 

In the working scope i only have 066 set and that works without issue. 

In the new scope i have tired with and without 067, Sever name and ip address.

I have added the new ip range in the sccm boundaries.

 

Computer will boot in to Windows and work as normal. (I get ip address, Ping servers and internet works) 

 

I have took a video but slightly too big to upload here currently. 

 

Any ideas?

 

 

 

 

[newpersn]

I should add. Timeout value on SCCM is 5 seconds. 

 

Video attached. 

Edited July 23, 2025 by newpersn

[StephenPink]

What network work was done? Depending switching/config may need to add the SCCM server IP to the DHCP/IP helper address list for the relevant VLANs

[newpersn]

New core switches with new vLans Added the SCCM server already in with the file path on 067

 

I have spend most of the morning fixing this - Managed to get it to boot in to SCCM without asking for the "enter key" being touched. Not sure how though.. 

[Geoff]

Using DHCP options is far from ideal. There are a number of limitations. The better solution is to add DHCP helpers to your switch configurations that relay requests to the SCCM VM.

 

You want to PXE Boot? Don't use DHCP Options. | Microsoft Community Hub

[ThomL]

Error message from video:

 

Looks like you need to investigate the error code PXE-E23.

From a quick google, some fixes that have apparently worked for people:

• Rebooting the server to restart all services has fixed this for some people
• Create/distibute/use a new boot image
•  'Deploy this boot image from the PXE-enabled distribution point' not being selected
• Removal of PXE from the DP and adding back
• Redistributing the boot image you're using
• Something worth taking a quick look at is administration -> overview -> distribution points; properties; general tab: create self signed certificate or import....
• Might be worth checking the servers pxe log:  (Drive letter)\Program Files\Microsoft Configuration Manager\Logs\SMSPXE.log

Hopefully something helpful in the above?

 

EDIT

Just notice you've fixed this issue, ah well - leaving this here might save someone some googling/investigation!

Edited July 25, 2025 by ThomL