MS Update for SCCM 2012 R2 (OSD, PXE, WDS)
Don’t miss this update for SCCM 2012 R2 if you use OSD feature with PXE-enabled DPs. As it might be your saviour for your WDS or slow transfer problems.
Excerpt from the article.
This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.
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.
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 behaviour when the target client is running Windows PE or a full Windows operating system.
This update applies to Central Administration sites, primary sites, administrator consoles, and clients. Applying this update to a site server will let you create client update packages.
After the update is installed on site servers, any operating system boot images should be updated.
- All existing media (such as stand-alone, boot, or prestaged) that use existing boot images (default or custom) will have to be re-created.
- To fully fix the problem in Issue 2, the client side .msp file has to be installed during the “Setup Windows and ConfigMgr task by using the PATCH= command.
Full article can be reached at http://support.microsoft.com/kb/2905002