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.

 

[Sam Banford]

Check that your boot image is being deployed:
Software Library>Operating Systems>Boot Images>MyBootImage... Properties>Data Source>"Deploy this boot image from the PXE-enabled distribution point"

Also check that unknown computers are being deployed a task sequence.

 

[michaelalzipperer0]

Yes to the first question and second question.

 

[Sam Banford]

When you deployed the TS did you:
Set "Make available to the following" to an item that included PXE?
Set the scheduling availibility to 12 - 23 hours in the past and not use "as soon as possible"?

 

[michaelalzipperer0]

the first part yes I did have it set to ASAP but changed it to the same time as become available, I can't put it before then because it won't let me and I cant set the scheduled time before the time im creating it.

 

[Sam Banford]

Delete and redeploy, on the scheduling set availible to D-1, H+1.

I never had WDS installed, I notice on your first screen shot the checkbox for "Enable a PXE responder without Windows Deployment Services" is still enabled (though not checked) which gives me the impression SCCM still thinks it's there and a reboot may be required.

 

[michaelalzipperer0]

Did a reboot and still same issue, that checkbox is to Enable PXE to respond without using Windows Deployment I leave that unchecked sins from what I understand that is for if I want to try to use PXE boot without having WDS at all. I have not tried that sins every documentation I have looked at so far states that WDS is used and no one ever checks that of.

 

[Edy]

your client and server on different vlans or you just have a big subnet? you would need ip helper set up if they are on different subnets.

 

[Edy]

also, the last boot image you update to the DP is the one that will be used

 

[michaelalzipperer0]

they are on different Vlans however the Workstation is talking to the SCCM server. I updated the X64 last

 

[Edy]

"talking" and "PXE Boot" are different.

 

[michaelalzipperer0]

According to the information that I was reading you are supposed to set up 066 and 067 options in the DHCP server, all the information I found on IP Helper was if It failed to find the SCCM server however as you see in the logs they both see each other and are communicating. did I read incorrectly?

 

[Edy]

ok, thats how i knew to get pxe boot working if client and servers on different vlans.

have you assigned boot image to your TS?

 

[Edy]

probably try changing your TS from required to available to all unknown computers

 

[michaelalzipperer0]

I just changed the Workstation to the same Vlan and same issue.

 

[michaelalzipperer0]

Yes the TS has a boot image assigned to it. ill need to make a new TS in order to change it. ill try that.

 

[Edy]

just delete the deployment and redeploy to all unknown computers with available purpose

 

[michaelalzipperer0]

Now the log is different but PXE still failing log below.

 

[Sam Banford]

What do you have option 67 set to in that dhcp scope?

 

[michaelalzipperer0]

smsboot\x64\wdsnbp.com