Hi, 1. Remove PXE images (if already added) from SCCM Console on PXE point..Uninstall WDS and reboot server. 2. Remove PXE role from ConfigMgr console. Monitor PXESetup.log to verify that the PXE Service Point uninstalled correctly 3. Install, but DO NOT configure, Windows Deployment Services (WDS) on the server that will host the PXE Service Point. DO NOT try to manually configure or start the WDS service 4. Configure PXE service point and monitor PXESetup.log and verify that the PXE Service Point installed correctly. 5. Add BOTH the x64 and x86 Boot Images on the SMSPXEIMAGES$ DP on the server where the PXE Service Point was created 6. Once the Boot Images have installed on the SMSPXEIMAGES$ DP, open the Services console on the PXE Service Point server and ensure that the Windows Deployment Services Server service has started. Additionally make sure that the RemoteInstall folder has been created and boot images exists in SMSIMAGES folder. 7. Create a ‘Task Sequence’ and advertise it on collection. To know more about Task Sequence , take a look at http://technet.microsoft.com/en-us/library/bb680818.aspx 8. Boot your client via network. for more information , http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

Hi, 1. Remove PXE images (if already added) from SCCM Console on PXE point..Uninstall WDS and reboot server. 2. Remove PXE role from ConfigMgr console. Monitor PXESetup.log to verify that the PXE Service Point uninstalled correctly 3. Install, but DO NOT configure, Windows Deployment Services (WDS) on the server that will host the PXE Service Point. DO NOT try to manually configure or start the WDS service 4. Configure PXE service point and monitor PXESetup.log and verify that the PXE Service Point installed correctly. 5. Add BOTH the x64 and x86 Boot Images on the SMSPXEIMAGES$ DP on the server where the PXE Service Point was created 6. Once the Boot Images have installed on the SMSPXEIMAGES$ DP, open the Services console on the PXE Service Point server and ensure that the Windows Deployment Services Server service has started. Additionally make sure that the RemoteInstall folder has been created and boot images exists in SMSIMAGES folder. 7. Create a ‘Task Sequence’ and advertise it on collection. To know more about Task Sequence , take a look at http://technet.microsoft.com/en-us/library/bb680818.aspx 8. Boot your client via network. for more information , http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

ok well have you added any images in SCCM osd ? I have plenty of step by step guides in my signature below, pick the OS of your choice My step by step SCCM Guides I'm on Twitter > ncbrady

Today we use WDS on srv 2003 as are OSD and we use SCCM as application deployment. Knoe I want to use SCCM as OSD to. How do I configure the WDS so I can use SCCM instead. Today SCCM 2007 R2 is running on srv 2003.

install the psp (pxe service point) role on that wds server and sccm will take care of it, cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

The PXE service point is installed on the WDS server, we press F12 to boot, and get images from WDS. But I want SCCM to to that instead?

The PXE service point is installed on the WDS server, we press F12 to boot, and get images from WDS. But I want SCCM to to that instead? If you look at the ProvidersOrder registry string under HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSPXE, you will see the providers that hand out the boot programs. SMSPXE is probably not the first one in your case. You can re-order that and put SMSPXE as the first one. Or, the safest would be, is, to simply uninstall the SMSPXE role and then uninstall WDS, and then re-installed WDS followed by a re-install of SMSPXE. Plus, redistribute the boot images to the SMSPXE DP share. If the provider order already has SMSPXE as the first one, then it means that SMSPXE could not find the reason to service the booting client, and so it ignores it and WDS moves on to the next provider. In this case, you should look at the SMSPXE log file and see why the client is being ignored or rejected. The most common reasons are... (1) you have not distributed the boot images to the SMSPXE DP share, or (2) there are no advertisements for the client.