Hey everybody I've just rolled out the 14 or so August updates on around 20 servers. Two of them were unusable on reboot. One (my main SCCM server which is virtual) was stuck on configuring updates for hours. Hard resetted and it eventually got to a logon screen the 2nd time round. Logging in accepted the password but never made it to a desktop, it just sat spinning and spinning. RDP not working, remote services and event viewer were working (ridiculously slowly though). Exactly the same thing happened to another (physical) server at a different location. Safe mode booted fine and quick. svchost was going crazy on both servers running at CPU 100% and using around 3GB of RAM. I eventually nutted it down to the WDS service and disabled it (both are PXE SCCM SP's). Rebooting both servers has brought them up fine without PXE obviously. I haven't gotten around to reinstalling WDS yet to see if that resolves it but a quick heads-up to everybody that the August updates (not sure which one) may break your SCCM server if you're using WDS. This happen to anyone else? Any solutions?

No problems experience in our test deploy. But we haven't tested it on any machines that are running WDS. Did you try the last know goog configuration or do a role back to the restore point. Have you opened a case with Microsoft CSS with the details.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Neither yet, have had no time today and I can live without the PXE booting for the moment. All I did was disable the WDS service in Safe Mode which has brought the server back to life. I will likely try reinstalling WDS and the PXE SP's when I get the chance.

OK. I've just done the following: (Both my servers are 2008R2, SCCM 07 R3) 1. Removed the SCCM PXE Service Point from my remote server. 2. Uninstalled WDS 3. Installed WDS 4. Added PXE SP. Waited for it to install and start the WDS service. CPU is fine. 5. Rebooted. Service is running fine. CPU is fine. Issue resolved. (But a major PITA!) No idea which update caused it. The only other commonality between the two servers is Sophos AV. Hopefully this doesn't happen to anybody else.. Might be worth disabling the WDS service before running the updates?

Issue recently. Sounds all too similar. We have brought in the August updates (seemingly) without issue. Everything seemed ok, however I then added some new drivers for a new model of PC into sccm, as this model wouldnt PXE, I added the x64 driver to the x64 boot wim. The driver is for a REALTEK GBE intergrated network card. The driver added ok, however from that point on the WDS service on the deployment server went critical (100% cpu) and the machine is unresponsive. Disabling wds service and restarting gives me a responsive box, but no pxe facilities to OSD. Also noticed that the SMSBOOT files for the X64 were now empty.?? not sure at which point these went ? We then removed all remnants of the new model and drivers, removed all drivers from boot.wim and eventually got SCCM working again. Got replacement files for the SMSBOOT\x64 area also. So - I then try to add the x32 realtek network driver to the pxe boot.wim for the new make and model. same issue - deployment server wds service spikes at 100% - server slows up. I noticed all SMSBOOT\x32 file had now gone missing this time.... Currently sitting with the service disabled and a happy server, but no OSD. Awaiting a colleagues return to see what he thinks, may try your remove PSP and WDS and reinstall. Anyone got anything else ? Thanks and regards - Hope to hear something.

I think, You can try to restart the server and you can try to follow the process mentioned above by OzVicAnoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Issue recently. Sounds all too similar. We have brought in the August updates (seemingly) without issue. Everything seemed ok, however I then added some new drivers for a new model of PC into sccm, as this model wouldnt PXE, I added the x64 driver to the x64 boot wim. The driver is for a REALTEK GBE intergrated network card. The driver added ok, however from that point on the WDS service on the deployment server went critical (100% cpu) and the machine is unresponsive. Disabling wds service and restarting gives me a responsive box, but no pxe facilities to OSD. Also noticed that the SMSBOOT files for the X64 were now empty.?? not sure at which point these went ? We then removed all remnants of the new model and drivers, removed all drivers from boot.wim and eventually got SCCM working again. Got replacement files for the SMSBOOT\x64 area also. So - I then try to add the x32 realtek network driver to the pxe boot.wim for the new make and model. same issue - deployment server wds service spikes at 100% - server slows up. I noticed all SMSBOOT\x32 file had now gone missing this time.... Currently sitting with the service disabled and a happy server, but no OSD. Awaiting a colleagues return to see what he thinks, may try your remove PSP and WDS and reinstall. Anyone got anything else ? Thanks and regards - Hope to hear something. I have the exact same problem - also a Realtek driver... Anyone?Sysadm