I have a single parent site server with 30 secondary DP's and PXE Everything's been working fine, I've been updating my PE with drivers seemingly with no problem when I noticed some of my secondaries stopped working, come to find out the WDS services would not start on some of the secondaries, after some research I discovered that if i remove the PE boot images the service would start, then I added them back in and some would not start. ALl my secondaries are setup exactly the same, why don't some start, what the heck. Can anyone help? 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: 0x11c4 Faulting application start time: 0x01cc9417ddaab840 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\system32\wimgapi.dll Report Id: 1c757ee7-000b-11e1-807a-00155d010f09

are they definetly running SCCM 2007 sp2 ?, you could try reinstalling WAIK from the SCCM media to see if it resolves My step by step SCCM Guides I'm on Twitter > ncbrady

ALL my secondaries are setup exactly the same, all are 100% uptodate.

Do you have the WDS hotfix installed on them? It's described in KB article 976073.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

You had me excited for a moment but when I tried to install it on one of the secondary sites experiencing this problem it would not install, said, "Setup has detected that the build version of this dydtem installed does not match the update you are applying to it. You can only install this update on Build 2195 to Build 6005." This is build 6.1.7601 Don't give up on me yet, any thing else I can try? Should I install this on the parent? Even those many of the secondaries are working?

Did you download the correct version? For some reason, the default version that gets displayed when you go to the request page is the SP1 version. If you click the show hotfixes for all version link it'll show the SP2 versions.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I believe so yes, there's only one to choose from. Note: I just created a new 32 bit PE, clean original and replicated it to one of the problem secondaries and WDS works so I can conclude something is wrong with my update PE, why its happening only on R2 is very strange but now i know its centered around the PE. Its vital that I have these extra driveres embeded so I am at a loss which one is causing the problem.

Given your above error message containing version numbers, you did not download the correct version. I'm assuming of course that you're on SP2. Also, 6.1.7601 is the Windows version and has nothing to do with ConfigMgr. Are you sure you have the right hotfix? The Windows Deployment Service stops responding when you use a PXE service point on a computer that is running a System Center Configuration Manager 2007 SP1 or SP2 site server: http://support.microsoft.com/kb/976073. Also, how are you injecting drivers? And, have you reviewed smspxe.log?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

yes, that is the one I tried on Windows 2008 R2 SP1 and got the error. There is only once to choose from the link you provided. ConfigMgr Client Version 4.00.6487.2157 I go to the Drivers pool, right click the driver and add to x86 PE I found no errors in the random pxecontrol.log I checked using trace32, do not see a smspxe.log

update I created a new x86 PE and populated it with a handful of network drivers, replicated it out to a problem secondary and it worked, WDS stayed running. So at this point I know I still need to add more drivers I just don't know which one caused the corruption in the first place, I would expect a red X under the Windows PE tab but there aren't any.

Did you click the link that said show hotfixes for all versions?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Sorry I didn't see that now that I did I would still select this one SCCM2007_SP1_KB976073_X64_ENU which I did for my Windows 2008 R2 SP1 64 bit and i get that error.

I'm just going to run with the new PE, seems to solve the problem. Thanks for your time.

So are you still on ConfigMgr 2007 SP1?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

whats this "ConfigMgr Client Version 4.00.6487.2157"

That's SP2, which takes me back to why are you trying to use the SP1 version of the hotfix? SCCM2007_SP1_KB976073_X64_ENUJason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

You had me excited for a moment but when I tried to install it on one of the secondary sites experiencing this problem it would not install, said, "Setup has detected that the build version of this dydtem installed does not match the update you are applying to it. You can only install this update on Build 2195 to Build 6005." This is build 6.1.7601 Don't give up on me yet, any thing else I can try? Should I install this on the parent? Even those many of the secondaries are working? Update! I was incorrect, all my secondaries are not exactly the same although they are all up to date and all Windows 2008 not all are R2. The secondaries experiencing this problem are all 2008 R2 SP1, thats the common denominator, hope that helps. (with the exception of one of them WEIRD) help! update - comparing the one that works only had the 64 bit PE so I'm assuming that the pronlem might be the 32 bit PE? BUt why are the 08 SP1 affected - ugh! Final Update Summary - WDS will not start on any Windows 2008 R2 SP1 that has my 32 bit PE (which I have been adding drivers to) The secondaries with Windows 2008 SP2 are NOT experiencing this problem Please advise

doesn't look like they have a patch for me

Huh? What's wrong with SCCM 2007, English, x86, sp2 SCCM2007_SP2_KB976073_X86_ENU Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I'm sorry, keep think OS, my OS is 64 bit. So I should use sp2 SCCM2007_SP2_KB976073_X86_ENU then?

Correct.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I didn't realize ConfigMgr came in 64bit.

It doesn't. The pre-SP2 hotfixes were separated by OS version. They realized this was not correct and caused tons of confusion right before SP2 came out and so switched to only offering x86 versions of the patches to match ConfigMgr only being x86. Of course the mid-stream switch has caused almost as much confusion.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

lol - add me to that confusion. Thanks for clearing it up though! :-)