HOTFIX is available for the "Operating System Deployment" feature of System Center 2012 R2 Configuration Manager

November 9, 2013 at 7:16 am in CM12 R2, OSD, PXE, sccm 2012 R2 by Kenny Buntinx [MVP]

All,

KB 2905002 has been posted to the hotfix servers to address two post-R2 issues:

This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.

Issue 1

After you enable the PXE Service Point role

(http://msdn.microsoft.com/en-us/library/jj217832.aspx)

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

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.

Please see the KB for details here : http://support.microsoft.com/kb/2905002

Hope it Helps ,

Kenny Buntinx

MVP enterprise Client Management