SCCM 2012: PXE not working because WDS service not starting

Summary

How to fix WDS crashing on a vanilla SCCM 2012 R2 installation

Issue:

This issue had been driving me mad when i was creating a new dev instance of my SCCM 2012 lab.

No matter what i tried i was unable to get my machines to PXE boot!.

The symptom was:
PXE-E53: No boot filename received
PXE-M0F: Existing Intel PXE ROM

SCCM_WDSFail_20150626

Exhausting the usual avenues, which are highlighted in a great article by Chip Hornbeck

http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

Finding the WDS service would not start our symptom was the following errors in EventLog

SCCM_WDSFail_Error1_20150626 SCCM_WDSFail_Error2_20150626 SCCM_WDSFail_Error3_20150626

Resolution:

So doing a quick search on the offending module (msvcr100.dll) revealed that it is a known issue with a available hotfix

Issue 1

After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Note This problem affects only distribution points that are installed on site servers.

Issue 2

When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.

For additional details and a link to a ConfigMgr 2012 R2 hotfix that resolves these issues please see the following:

KB2905002 – An update is available for the “Operating System Deployment” feature of System Center 2012 R2 Configuration Manager (http://support.microsoft.com/kb/2905002)

Source: http://blogs.technet.com/b/configurationmgr/archive/2013/12/05/hotfix-an-update-is-available-for-the-quot-operating-system-deployment-quot-feature-of-system-center-2012-r2-configuration-manager.aspx

While the hot-fix is available here:

http://support.microsoft.com/kb/2905002

I would suggest instead installing CU1 or CU2 which have the hot-fix included.

Advertisements

3 responses to “SCCM 2012: PXE not working because WDS service not starting

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s