WDS and PXE issue when initiated on DP

[Config_Mgr_noob]

Hi,

 

We just recently installed and configured SCCM 2012 on our VM server 2012. We created a DP during the installation process and initiated PXE after the installation was completed. We are able to distribute to our DP and update it as well. However, when I look at the WDS role, installed by SCCM, the PXE response tab is set to "Do not respond to any client computers". Shouldn't this tab be set to Respond to all client computers(known and unknown) after PXE has been initiated on the DP? Any help would greatly be appreciated.

[bob442]

You shouldn't need to configure anything in WDS, just leave that alone. All PXE config should be done within the PXE tab in the distribution setting for that server.

[Config_Mgr_noob]

I figured WDS did not have to be configured. However, shouldn't the PXE Response tab within WDS be checked on when PXE is enabled on the Distribution Point? Because when I tried to PXE boot a client I'm receiving a "PXE-53: No boot filename received". My network manager already set an ip helper on our router to route PXE response to the configmgr server vs DHCP option 67 and 66 configurations. Any idea how to resolve this? I have attached my smspxe.log to this form.

[bob442]

I'm no expert but it looks like a permission or configuration problem. take a look at these two links, hope this helps.

 

http://www.windows-noob.com/forums/index.php?/topic/7281-management-point-pxe-boot-error-80004005-after-sp1-upgrade/

 

http://www.windows-noob.com/forums/index.php?/topic/4468-using-sccm-2012-rc-in-a-lab-part-7-build-and-capture-windows-7-x64/

[Config_Mgr_noob]

Do you think by importing a PKI client certificate vs the default Self-signed certificate would do the trick? I read at the bottom of the forum that one user imported a PKI certificate to his distribution point after he upgraded to SP1. If so, would I have to configure a ADCS and create a PKI cert from there? Or would it be through IIS Manager? I'm trying to avoiding recreating the Installfolder and every other folder the DP created from my drive as this presented other problems before. I also attached a screenshot of the error message I receive when I PXE boot a client.

 

Also, I have RemoteInstall folder with shared and the NTFS to full control for administrators and system only, should I add Everyone or Domain users to have Read permissions? Not sure if this plays a role.

[Config_Mgr_noob]

I've also noticed when I PXE boot my clients now, the smspxe log is stating these entries with no error lines.

[Iroqouiz]

The log says the client is unknown and that it can't find any advertisements. Have you deployed your task sequence to All Unknown Computers?

[Config_Mgr_noob]

Thanks Iroqouiz! That did it. I am now able to PXE boot my clients and deploy my images.

[Iroqouiz]

Great.

 

Just a heads up: at my site we always regard computers as unknown, even if it's a "refresh/replace" scenario. So our OSD task sequences are always only deployed to All Unknown Computers. This means that whenever we are reinstalling a computer, we have to delete it from the SCCM console first, otherwise the computer will still be in the database and thus "known", and therefore not getting any deployments. Keep that in mind if you decide to go the same way.

[Config_Mgr_noob]

Thanks for the heads up; I'll keep this in mind. Also, would you be able to help with a Task Sequence error message I receive today when capturing an image during the Build and Capture task sequence. I attached an image below. I've read online it might be associated with NIC drivers not being injected into the task sequence. However, during the WinPE stage I was able to receive an IP address when I ran the F8 cmd prompt.