Hello good I would like to know how to follow few steps to properly install a SCCM PXE Point role, when you install WDS it has this set or not set the wds is recommended and then install the SCCM PXE role. It should configure the DHCP option 60 if not on the same machine and also listen on port 67. Is there any official document from Microsoft. Thanks and regards,

Here's the official documention for installing the PSP: http://technet.microsoft.com/en-us/library/bb680668.aspx You should *not* configure WDS manually, the PSP will take care of this. Using DHCP scope is generally discouraged and is *not* supported by Microsoft. If you need to PXE boot across broadcast boundaries, then you should use iphelpers.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Here's the official documention for installing the PSP: http://technet.microsoft.com/en-us/library/bb680668.aspx You should *not* configure WDS manually, the PSP will take care of this. Using DHCP scope is generally discouraged and is *not* supported by Microsoft. If you need to PXE boot across broadcast boundaries, then you should use iphelpers.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Hi, In addition, you can read this technet blog about WDS and PXE service point troubleshooting. Inside the blog, not only troubleshooting tips but also step-by-step configure WDS and PXE service point are referenced. http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx Please reference the following parts of the blog post: Co-hosting DHCP and WDS On The Same Server How To Properly Install And Set Up A New Instance Of WDS And A PXE Service Point Hope this will help. Thanks

Hi, In addition, you can read this technet blog about WDS and PXE service point troubleshooting. Inside the blog, not only troubleshooting tips but also step-by-step configure WDS and PXE service point are referenced. http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx Please reference the following parts of the blog post: Co-hosting DHCP and WDS On The Same Server How To Properly Install And Set Up A New Instance Of WDS And A PXE Service Point Hope this will help. Thanks

I used to swear by Option 66 and 67 but after running across one very obscure set of circumstances where it wouldn't work, I now swear by IPHelpers. So... Get someone in networking to setup your IPHelpers on the appropriate VLANs. Install WDS. Do not touch it or initialize it. Reboot. If you want to install R2, do it now. Enable Unknown Computer support soonest if you plan to use it. Install the PXE Service Point. Watch the PXESetup.log + the MSI log for any errors. Reboot once the install logs show everything is good. Push both x86 and x64 boot images to the PXE distribution point (server share). Once that's come down, verify the SMSBoot\x86 and \x64 directories have all the network boot files. WDSNBP.com is one of them. (If the SMSBoot directories won't populate, check the SMSPXE.log for issues. If on 2008, you can have a problem with the c:\windows\temp\pxebootfiles directory and may need to delete it and restart WDS). Once you've got the network boot files in the X86/X64 directories, setup a non-mandatory advertisement and run a test. (Be careful as to the scope of that test, obviously) The PXEControl.log and SMSPXE.log are the most salient logs here. One point to remember - if you aren't getting requests from MAC addresses aside from the self-tests, the problem is usually on the network side. I've been on too many bridge calls blaming the PXE Service Point, only to find the IPHelper wasn't configured properly. If you absolutely HAVE to use DHCP scope options, set option 66 to the hostname or IP address of the server, then option 67 as the bootfile path. Don't use Option 60 - I've never seen that work or be helpful in anyway. My two cents....