PXE works once but then not again!

[P.Keen]

Hi,

 

I have a problem where a device will PXE boot once but then after getting the flag I clear it and it won't run again. I have deleted the device from sccm and reimported it manually. The pxe log says nothing of interest when searching the "resource id" in the logs.

 

I originally thought this was because I set the deployment to "dont rerun" so I changed it back almost 30 minutes ago but still the same thing.

 

Same device worked just 1 hour ago and as I said i cleared the flag and now just getting the

 

PXE-E53 - No boot filename received

 

PXE-M0f - Exiting broadcom PXE ROM.

 

Regards

Peter

[Rocket Man]

Have you tried fushing out the WDS from PXE adds...just restart the WDS service to do this...by default it will flush out every 120 mins

[P.Keen]

Have you tried fushing out the WDS from PXE adds...just restart the WDS service to do this...by default it will flush out every 120 mins

 

@Rocket Man thanks for the advice. I have since restarted the SQL server and the sccm machine as well but still nothing.

 

I just restarted the WDS Server service but still nothing.

 

I have also deleted the HB discovery entry and manually imported but same thing.

[P.Keen]

This might be my problem.

 

 

<p>

• Members
  
• 
  
• 37 posts
  

• 
   
  

 

Posted 19 July 2012 - 07:59 AM

Ok I finally got it to prompt me for F12 to start Boot.

 

Changes I made:

DHCP Server I enabled option 66 and 67. This is on another server than SCCM.

In WDS I changed options:

Respond to all client Computers (known and unknown)

Multicast IP Address: Obtain IP address from DHCP

 

--------------------------------------------------------------------------------

Can anyone confirm that these settings should be configured in WDS? Currently I have Multicast = Use addresses from the following range 239.0.0.1 - 239.0.0.254 and PXE response = Do not respond to any client computers.

 

Im think the "do not respond to any client computers" could be my issue? Can anyone confirm before I go changing settings.

[P.Keen]

Further testing - tried to use a USB device bootable media and it says there is no TS available.

 

Checking the Collection the device is in there and it 100% has a deployment for it.

 

Ok so took it out of that collection and put it in a exsisting collection and PXE works fine. WTF. \

 

HAHAHAHAHAHHAHAHAHAHAAHAHA worked out what was going on, feelsbadman.jpg. So it wasnt a OSD deployment to the collection it was a package a package that I put in a OSD so I accidently deployed a packaged instead of an OSD deployment to that collection. The reason why it was working once and not again was because it was running a TS from another collection so when I saw it was the wrong one I would remove it from that collection then bam it wouldnt work because it basically had no OSD deployment to do. What a waste of time and stress.

[Rocket Man]

Changes I made:

DHCP Server I enabled option 66 and 67. This is on another server than SCCM.

In WDS I changed options:

Respond to all client Computers (known and unknown)

Multicast IP Address: Obtain IP address from DHCP

 

--------------------------------------------------------------------------------

Can anyone confirm that these settings should be configured in WDS? Currently I have Multicast = Use addresses from the following range 239.0.0.1 - 239.0.0.254 and PXE response = Do not respond to any client computers.

 

 

No need to do any of this!!

[hhancock]

No need to do any of this!!

 

I concur. I set DHCP Scope Options on my DHCP server. You might have to reboot DHCP after this.

 

Make sure you remove any Unknown objects from ConfigMgr.