xc3ss1v3 Posted March 24, 2014 Report post Posted March 24, 2014 Good morning... Over the weekend last week, I upgraded both my CAS and PSS to R2 seemingly without issue. However, later in the week while working on OSD, I noticed that my test machine was no longer able to boot to PXE. In doing some investigating, I've noticed that on my PSS (where I have PXE enabled as a part of the DP role), the WDSServer service fails to start. I've tried several different basic ways of resolving, i.e. removing/re-adding the PXE setting in the DP role, removing/re-adding the WDS role from the server itself, but I have not been able to resolve. Here is some of the information I've found... From the Application Windows Log... Faulting application name: svchost.exe_WDSServer, version: 6.2.9200.16384, time stamp: 0x50108897 Faulting module name: ntdll.dll, version: 6.2.9200.16384, time stamp: 0x5010acd2 Exception code: 0xc0000005 Fault offset: 0x000000000001fb20 Faulting process id: 0x116c Faulting application start time: 0x01cf4778e3902d9c Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 25e57802-b36c-11e3-9417-0050569d2fd8 Faulting package full name: Faulting package-relative application ID: And from the System Windows Log... - System - Provider [ Name] Service Control Manager [ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4} [ EventSourceName] Service Control Manager - EventID 7034 [ Qualifiers] 49152 Version 0 Level 2 Task 0 Opcode 0 Keywords 0x8080000000000000 - TimeCreated [ SystemTime] 2014-03-24T15:54:56.455038100Z EventRecordID 265475 Correlation - Execution [ ProcessID] 528 [ ThreadID] 3980 Channel System Computer SCCM-PSS-01. Security - EventData param1 Windows Deployment Services Server param2 3 5700440053005300650072007600650072000000 Any help with this would be highly appreciated. Quote Share this post Link to post Share on other sites More sharing options...
xc3ss1v3 Posted March 24, 2014 Report post Posted March 24, 2014 My apologies... apparently, I wasn't searching for the right topics before posting this. Found a different thread that eventually pointed to a hotfix that resolve the issue. Feel free to mark this one closed. For anyone that stumbles upon this thread, here's the link. http://support.microsoft.com/kb/2905002 Quote Share this post Link to post Share on other sites More sharing options...
