Hi, I originally posted this question here: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/03b53480-9477-4e90-855a-3f9dbcd7f4b5/#2b0cbcbf-ac00-438d-90ca-4be44e7e6045 - but this is the more appropriate place for it. I have two secondary sites, both that run the PSP and DP roles locally. From my primary site I added network drivers to the WinPE image, and then distributed it to those DP's. Shortly after that I realised that clients trying to use those PSP's could no longer PXE boot. First I will explain what I have done so far: 1. After investigating the system status for those secondary sites I noticed the component status for the PSP was failed. I checked the pxecontrol logs on the secondary sites, both had this entry: "PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'." 2. Checking further I realised that the Windows Deployment Services Server (WDS) was not running. I attempted to start it but it came back with an error and would not start. I then checked the local servers event logs and found these two entries that started to occur at the same time my problem was happening: Log Name: System Source: Service Control Manager General: The Windows Deployment Services Server service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 600000 milliseconds: Restart the service. Log Name: Application Source: Application Error General: Faulting application name: svchost.exe_WDSServer, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: wimgapi.dll, version: 6.1.7600.16385, time stamp: 0x4a5be09a Exception code: 0xc0000005 Fault offset: 0x0000000000032a8e Faulting process id: 0x1338 Faulting application start time: 0x01cbfecfb154f4f3 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\system32\wimgapi.dll Report Id: f089f975-6ac2-11e0-9ddc-005056970055 This issue was similar to these posts: http://social.technet.microsoft.com/Forums/en-NZ/configmgrosd/thread/a1a176cf-c88f-4f17-81a5-df5d80fc36d3 http://www.windows-noob.com/forums/index.php?/topic/1867-sccm-osd-pxe-wds-service-fails-to-start/ I rebooted the server multiple times, same issue. 3. I then removed that boot image from those DP's via Boot Image > Distribution Points. Monitoring the distmgr.log from the primary site (parent) I could see it sending instructions to the secondary sites to tell them to remove the boot images from their DP's. Then looking at the distmgr.log on the secondary sites I could see it processing the "inboxes\distmgr.box\INCOMING" files, but it just kept trying to do the same jobs over and over again: *Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\DPZYHOYJ.PKG. *Adding package 0D100025 to the active package array. *Package 0D100025 requires a newer version (8) of source files and the new compressed files haven't arrived yet, current version is 7, skip C:\Program *Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\DPZYHOYJ.PKG *Removing package 0D100025 from the active package array. This would continue to happen every 15 minutes. Checking the "SMSPKG" folder on the secondary site I could see that the compressed files were still present in the share. Checking the "RemoteInstall\SMSIMAGES\SMSPKG" folder I could see that the boot image package had still not yet been deleted. At these point WDS would still not start. I rebooted the server multiple times, same issue. 4. I deleted the compressed files and the package files for the boot image from the above shares. I rebooted the server. I checked WDS and it had started. 5. With WDS fixed, and the pxecontrol log showing "PXE test request succeeded." I then decided to re-distribute that boot image to the DP's. From the primary site's distmgr.log I could see instructions being sent to install the package at the destinations DP's. Viewing distmgr.log at the secondary sites I could see it was still going through the same process shown above, and not downloading and installing the package. 6. From the console I then removed the boot image from the DP's. On the secondary sites I then deleted the ".PKG" files relevant to the boot images in \Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING. After that distmgr.log stopped trying to process the same files over and over and showed the following: Used 0 out of 3 allowed processing threads. Sleep 3600 seconds... 7. I then re-distributed that same boot image to the DP's. Reviewing distmgr.log on the secondary site I could see that the same behaviour before started happening again, and the package would not download and install at the DP: *Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\BPPMU6AX.PKG. *Adding package 0D100025 to the active package array. *Package 0D100025 requires a newer version (8) of source files and the new compressed files haven't arrived yet, current version is 7, skip C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\BPPMU6AX.PKG *Removing package 0D100025 from the active package array. 8. I then created a brand new boot image added the same drivers that the original one had, and configured it exactly the same, and then distributed it to the same DP's (normal and PXE) and it installed fine! Checked the WDS service and it was still running fine. Checked pxecontrol.log and no errors. Rebooted the server and everything still started up fine. So that's what I've done so far. These are the questions: 1. Why did adding new NIC drivers to a boot image and then updating and distributing that boot image kill the WDS service on my secondary site servers? Does this happen often and is there a hotfix? 2. Why can I not re-distribute the original boot image to those DP's (distributing to either normal or PXE DP is the same result)? As shown above, distmgr.log says: "a newer version (8) of source files and the new compressed files haven't arrived yet, current version is 7" but that is only partially true. It's correct that the current version was 7 (but I then removed via the console, and deleted the files locally as per above) - however the newest version of that boot image is 11, not 8. But each time I try to re-distribute it keeps saying 8. Any help is appreciated. Thanks! William Eriepa | New Zealand

I hate when you find something and can't find it again later. I thought I remember a notice about a patch for SCCM dealing with R2 and PXE on a blog from one of the Microsoft Deployment or SCCM chaps. I will mention it here and maybe you can find it while I look as well. At any rate, it has to do with DHCP and helper addresses being on the switch the SCCM DP is connected to, but I can't remember if it was a problem with PXE starting or if it was a problem with clients not being able to find the right service point. Regardless, I think it was in the last 30 days, and no later than 60.Anything worth doing is worth doing right.

· Hi, I think which TowedJimper-3504 stated is the following articles: PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67 SCCM 2007 OSD : How to allow DHCP broadcasts across VLAN's Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hey TowerHumper, thanks, my issue was definitely with the WDS service on the PSP not starting. Hey Sabrina, thanks for providing those links. In either case these do not explain why when I updated and distributed the boot image it killed the WDS service on the PSP Servers. Removing those boot images from the PSP Servers allowed WDS to start again and function properly. Creating a new boot image assembled with the same drivers and configuration as the old one and distributing it to the PSP Servers results in clients being able to successfully PXE boot. CheersWilliam Eriepa | New Zealand

Hi Will, any luck resolving this? I am experiencing the same problem...