SCCM 2012 - PXE Boot woes

[stebo730]

Right!

 

I am pretty sure I have SCCM 2012 set up correctly. WDS was installed from within SCCM by enabling PXE boot on a Distribution Point. No config on WDS at all.

 

PXE Booting is hit or miss, I am getting a lot of PXE-E53 No boot filename received errors. This can happen on a particular computer and fine on another. Another computer it will be fine and boot up to the task sequences, the next time I try on the same PC I get the PXE-E53 error message.

 

The only thing I can think of is maybe SCCM knows about that PC because of the MAC address in the SCCM CLient software installed on a PC. I am lost, any pointers again would be most welcome.

 

I do not have any 66 or 67 options in DHCP as this is not advised.

 

Thank you.

[FN-GM]

i dont have the DHCP setup either, i used to have the same problem.

 

I fixed it by putting an IP Helper in the vlan. It shouldn't be needed if the clients are in the same vlan as the servers but it sorted it. What switches do you have?

 

I assume the machines have a TS assigned to them with pxe boot enabled on it?

[Norphy]

Is your DP on the same server as the DHCP server?

[stebo730]

I had set it to deploy to Unknown Devices and for whatever reason it was a known device and would go no further.

 

I did a quick test by setting it to the TS to go to All Systems, which I don't really want to do, so any advice on the best course of action so I can target specific machines would be good.

 

Finally it looked like it was working the I got a TS Error 0x80091007 just after the wim had downloaded :-(

 

One problem after the next!

[Norphy]

That is a hash mismatch error. Run the task sequence again and see if you can grab the logs from x:\windows\temp\smstslog. Find out which package is generating the hash mismatch and redistribute it to your DP.