I've finally got my secondary site working and reporting back to the Primary, and I have proceed to setup the PXE Service Point Role. I've followed the guides that I used to setup my primary, so I installed WDS (without configuring it etc.) and setup IIS and added the WebDAV authoring rule etc. However I have installed the PXE Service point rule, and I can't PXE boot. The issue is that after installing the PXE Service Point role, it has broken the WDS Service and WDS can no longer start. The following are logged in Event Viewer when I manually try to start the WDS service (in order) On 10/06/2011 09:05:20, component SMS_PXE_SERVICE_POINT on computer [SERVER NAME] reported: PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 16389 Possible Cause: PXE service point is not started or not responding. Solution: Manually restart the PXE service point. I then try to manually start the Windows Deployment Services service (which I am assume is what the previous event is asking) An error occurred while trying to initialize provider SMSPXE loaded from C:\Program Files (x86)\SMS_CCM\x64\smspxe.dll. If the provider is marked as critical the Windows Deployment Services Server will be shutdown. Error Information: 0x4005 An error occurred while trying to initialize provider SMSPXE. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x4005 An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown Error Information: 0x4005 I must be missing something, I have rebuilt this server and am still getting the same error, which leads me to believe that the issue is either with the Primary Site, or the Domain which the server is in. For background, all servers are 2008 R2 SP1, running SCCM 2007 SP2 R3, and the Primary is using SQL 2008 Standard for the database. Both servers are in the same Domain, but are in different IP Subnets, on different sites, hence the need for a secondary site and an additional PXE service point. I found this hotfix http://support.microsoft.com/kb/976073 but I am unable to download it as when I request it the MS page comes back with "the service is unavailable" so I guess this hotfix is not longer active. I have read numerous articles, about people fixing this via uninstalling the PXE service point role, and WDS, and starting again, which I have done numerous times, and had to do to the Primary site to fix a problem there, but this has not worked for this secondary site. Anyone have a guide to setting up a secondary PXE service point "properly"? Thanks in advance TechNet community.

That hotfix is the way to go IMHO and the link works fine for me.Torsten Meringer | http://www.mssccmfaq.de

It's certainly not working for me in the UK, tried multiple pcs, on different ISPs

I can confirm the hotfix is offline at the moment. Maybe someone @ MS can check that.Miguel Rodriguez

Hi, You can try by changing the region in the hotfix's page, i confirmed it can be downloaded in "United States". Thanks

Just to let everyone know, the hotfix is back online (in the UK, at least) I will be testing it to see if it fixes the issue.

Afraid to say that the Hotfix did not solve the issue :( Am now back to banging my head against the wall.

Have you followed these instructions already? http://blogs.technet.com/b/smsandmom/archive/2008/09/17/configmgr-2007-troubleshooting-pxe-service-point-issues-and-wds-service-not-starting.aspx Miguel Rodriguez