Last Friday Microsoft released the ‘not-so-long-but-even-more’-awaited hotfix for two issues that came with Microsoft System Center 2012 R2 Configuration Manager.
That download is available here: http://support.microsoft.com/kb/2905002
It fixes the following two issues: (source Support.microsoft.com)
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 behavior when the target client is running Windows PE or a full Windows operating system.
Background Information on these issues
Fellow MVP Johan Arwidmark (www.deploymentresearch.com ) wrote a nice guide on how to Upgrade from ConfigMgr 2012 SP1 to R2 and also highlighted those two issues and some workarounds.
Please go to his site for more information.
I already installed that hotfix in my Lab and it went without an issue. Up until now I have only seen one feedback mail by another MVP who was affected by Issue No. 2 and that hotfix dramatically increased his download speed from 55MB/s to 1,2GB/s!
Now is the time to do your backups again, test them and then upgrade your Labs and see if all goes well.
New Update Packages
With this hotfix KB2905002 come 4 new update packages that need to be deployed in your environment:
Take special care deploying those Client updates during Task Sequences. I usually use this technique: http://deploymentramblings.wordpress.com/2013/08/22/installing-configmgr-2012-sp1-cu2-during-osd/