PENDING Issue using PXE boot Configuration Manager is looking for policy

[michaelalzipperer0]

I have been having issues with setting up PXE Boot I have the feature enabled and WDS installed letting PXE Boot install it, I had installed it myself first then enabled PXE Boot before but I was getting the same errors so I Disabled PXE Bood uninstalled WDS and then let SCCM install WDS when I re-enabled PXE Boot after rebooting it.
the Boot Image for both X64 and X86 are Distributed and show up under Content Status as 100% compliant.

on the computer, it shows that it starts to talk to the server and then I get a message that states Message from Administrator: Configuration Manager is looking for policy. then it states its contacting the server then moves to boot to next device.

 

[michaelalzipperer0]

yes

 

[Edy]

delete your deployment of the TS and re-deploy and this time make it as available instead of required.

 

[Edy]

on TS, it was trying to load x86 boot image. you need to redistribute the x64 boot image to make it the primary boot image. which boot image did you assign to your TS?

 

[michaelalzipperer0]

ok ill recreate my deployment, it is a x64 ill redistribute the x64 and I assigned the x64

 

[Edy]

i forgot the most important thing. have you injected the network driver to your boot image?

 

[michaelalzipperer0]

No, When I had set this up back in February and had it running I did not need to do that.
Do I need to find drivers for this Workstation and add them to the Deployment somehow?

 

[michaelalzipperer0]

Is updating the Distribution point the same as Re-Distributing?

 

[michaelalzipperer0]

This time I got to preparing network connection in the Windows PE boot screen then it did a reboot.

 

[Sam Banford]

Why am I getting a deja-vu on this whole thread? Did we just go through this with someone else not so long ago?

That last log shows what looks to be a good sequence; sees it as unknown and gets the x64 image. If you're getting to PE, PXE's good. I've never had to add network drivers but that's all dependent on the hardware you're using. If you've not done it in the past and both PXE and OSD worked I wouldn't do it now.

 

[michaelalzipperer0]

So history, we use to have an SCCM server but it was torn down by the previous System Admin, I replaced him later and was tasked with building a new one I built it and had PXE boot working but could not get windows updates to push and found out it was because of the version of SQL server I had installed so tore it down and rebuilt the server from scratch and got the updates working now but not the PXE boot, when I did have PXE boot working drivers where not needed for the devices I'm deploying to.

Why am I getting a deja-vu on this whole thread? Did we just go through this with someone else not so long ago?

That last log shows what looks to be a good sequence; sees it as unknown and gets the x64 image. If you're getting to PE, PXE's good. I've never had to add network drivers but that's all dependent on the hardware you're using. If you've not done it in the past and both PXE and OSD worked I wouldn't do it now.

 

[Edy]

in other thread, the fix for the pxe issue was setting up DHCP scope. do you have this in place?

 

[michaelalzipperer0]

in other thread, the fix for the pxe issue was setting up DHCP scope. do you have this in place?

Yes the scope is set up

 

[steveo1984]

Have you tried using ip helpers on your L3? This resolved the issue for us.