Microsoft System Center Configuration Manager (SCCM) assists IT pros who manage data centers, computer networks, and individual devices. SCCM encompasses several IT solutions that are automated and easy to integrate. With less effort having to go into IT management, System Center allows organizations to stop fighting with technology so they can concentrate fully on their work. That is, unless technical errors arise. Below is the story of an SCCM PXE Boot Error that one of Directions’ Technical Experts was able to address successfully.

A recent student asked me about a problem he was having with his System Center Configuration Manager environment.

The problem he encountered was related to PXE boots during build using OSD.
His PXE Distribution point is configured on Windows 2008R2 server. PXE boots were failing intermittently to the PXE server.

I inquired about any configuration issues such as dedicated boundary group or other possible network issues which may have prevented clients from attaching to the PXE server.

There did not seem to be any issues related to configuration. So, the next step was to review the logs. We looked at both SCCM logs as well as Windows system logs. The only error consistently reported was the following Windows Application Log error:

Log Name: Application
Source: WDSServer
Event ID: 512
Task Category: WDSServer
Description: An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will continue.

As well as this event in the system log:

System Log: The Windows Deployment Services Server service terminated unexpectedly:
An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will continue. Error Information: 0xC1030136

After researching the problem I found the following two articles related to these errors.

There seems to be fixes for the problem. However the following registry hack is suggests as a work around. This comes from the support link:

Configure the Configuration Manager WDS provider to be single-threaded instead of multithreaded. This will limit WDS processing of PXE requests to one at a time and will prevent the second, duplicate PXE request from conflicting with the original request. To configure the Configuration Manager WDS provider for single-threading, create the NumberOfThreadsregistry key with a DWORD value of 1 in the following location:

Configuration Manager 2007 32bit WDS server:HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\PXE
Configuration Manager 2007 64bit WDS server: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS\PXE

Doing this does not typically affect server performance for PXE requests except in environments where a large number of PXE requests are performed on a consistent basis. In these environments, we recommend that you use the first workaround.