Craig Paulsen
asked on
PXE - WDS Service - SCCM 2012
On Friday morning and on Sunday morning this week the Windows Deployment Services service on both our SCCM servers that service PXE requests broke and stopped responding correctly to PXE requests, and also started consuming significant amounts of CPU resources on the server.
This state led to machines not receiving PXE requests when rebooted (workstations configured to NETWORK boot as first boot option), causing some machines to stall at boot,
Stalled machines rebooted while the services were broken would most likely stall again.
In both cases, restarting the WDS services while in this state restored proper service. However, I am concerned that this behaviour is going to continue to occur. Any ideas what could be causing this? This was working fine for about 2-4 months, no patches applied in last week, we running version 6.3.9600.16384 for WDS,
Any ideas will be most appreciated
Thanks in advance,
This state led to machines not receiving PXE requests when rebooted (workstations configured to NETWORK boot as first boot option), causing some machines to stall at boot,
Stalled machines rebooted while the services were broken would most likely stall again.
In both cases, restarting the WDS services while in this state restored proper service. However, I am concerned that this behaviour is going to continue to occur. Any ideas what could be causing this? This was working fine for about 2-4 months, no patches applied in last week, we running version 6.3.9600.16384 for WDS,
Any ideas will be most appreciated
Thanks in advance,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for your response, we've found the issue to be with the WDS service on the x 2 DP's, the service appears to have been in a hung state as a result of the reboot storm (IE: workstations configured via a GPO to reboot at 3am on a Sunday morning)
Restarting the service resolved the issue.
Restarting the service resolved the issue.
ASKER