PXE-E53 No boot filename received

[Kingskawn]

I have one secondary point that cannot deploy images

 

In the past I had a problem with binlsvc as this wouldn't start the WDS service. To resolve this I have to use the 'initialize' command to configure WDS.

After that WDS/PXE server gave 'PXE-E53 No boot filename received' untill now.

So yesterday I reinstalled it following this:

Everything started directly as it should. (I also had to delete everything inside c:\windows\temp\)

 

Inside this LAN there is no active VLAN nor DHCP installed on secondary point. Ports 66 and 67 aren't configured for SCCM.

The RemoteInstall folder was empty so I copied this folder from a working secondary point but still no luck.

 

The pxecontrol.log gives me successful all the time;

 

Sent 274 bytes to 010.075.011.023:4011~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:21:35.055 2010 Romance Daylight Time><thread=3080 (0xC08)>

PXE test request succeeded.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:21:35.274 2010 Romance Daylight Time><thread=3080 (0xC08)>

Successfully performed availability check against local computer.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:21:35.274 2010 Romance Daylight Time><thread=3080 (0xC08)>

Received a registry change notification. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.438 2010 Romance Daylight Time><thread=3080 (0xC08)>

------ RegisterForNotification(): Registering again! -------~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.438 2010 Romance Daylight Time><thread=3080 (0xC08)>

Successfully handled registry changes. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>

Received a registry change notification. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>

------ RegisterForNotification(): Registering again! -------~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>

Successfully handled registry changes. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>

adding address to server list 10.75.11.23 $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>

adding address to server list 127.00.00.01 $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>

Sending availiability packet to: 10.75.11.23~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>

Sent 274 bytes to 010.075.011.023:4011~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>

PXE test request succeeded.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.283 2010 Romance Daylight Time><thread=3080 (0xC08)>

Successfully performed availability check against local computer.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.283 2010 Romance Daylight Time><thread=3080 (0xC08)>

 

On the client machine when I launch, it gives the correct ip address of the secondary point but says PXE-E53

 

Also I just saw that the advertised task sequence isn't attached as being advertised to the collection but nevertheless it must give me an abortPXE then?

[anyweb]

have you tried configuring options 66 and 67 on the dhcp server ?

[Kingskawn]

have you tried configuring options 66 and 67 on the dhcp server ?

No is that a requirement? And if I must, what's the procedure, do you have a guide? I'll test it

 

EDIT: Just put "\smsboot\x86\pxeboot.com" to the port 67? Not 66? I need to restart DHCP, can't do this in production I suppose otherwise I'll block some people

[anyweb]

test it first in your test lab

 

from memory...

 

option 66 is for the wds server name (or ip)

 

option 67 is for bootfile name

[Kingskawn]

test it first in your test lab

 

from memory...

 

option 66 is for the wds server name (or ip)

 

option 67 is for bootfile name

 

Ok we can close this topic. I already found out what it was. I needed to simply copy the boot file to the PXE server. Something I thought was done and couldn't see in de advertisement status.

[dopod07]

Ok we can close this topic. I already found out what it was. I needed to simply copy the boot file to the PXE server. Something I thought was done and couldn't see in de advertisement status.

 

 

Hi Kingskawn,

 

Can you let me know which boot file you copy into which folder ? i am having the same issue with booting from PXE with Secondary server. thanks.

 

 

Dan

[Kingskawn]

Hi Kingskawn,

 

Can you let me know which boot file you copy into which folder ? i am having the same issue with booting from PXE with Secondary server. thanks.

Dan

 

I think it was

 

For: .\smsboot\x86

 

abortpxe.com

bootmgr.exe

pxeboot.com

pxeboot.n12

wdsnbp.com

 

For: .\smsboot\x64

 

abortpxe.com

bootmgfw.efi

bootmgr.exe

pxeboot.com

pxeboot.n12

wdsnbp.com

 

And do an update of bootfiles after that