The Hotfix in this article has been superseded by the hotfix that is available in KB 2910552. Please install the current version of the hotfix. To obtain the current fix and for more information, see the following Microsoft Knowledge Base article:
2910552 You cannot stage a Windows PE 3.1 boot image to a Windows XP-based computer after you upgrade to System Center 2012 R2 Configuration Manager
Summary
This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.
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: 0x5215dfe3Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034aException code: 0xc0000005Fault offset: 0x000000000005f61aFaulting process id: 0xae4Faulting application start time: 0x01cec5d767184634Faulting application path: C:\Windows\system32\svchost.exeFaulting 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 you download operating system image files to Configuration Manager 2012 R2 clients, the process takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior if the target client is running Windows PE or a full Windows operating system.
More Information
Update information
A supported update is available from Microsoft Support. However, this update is intended to correct only the problem that is described in this article. Apply this update only to systems that are experiencing the problem described in this article. This update might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this update.If this update is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain this update. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the update is available. If you do not see your language, it is because an update is not available for that language.
Installation information
This update applies to Central Administration sites, primary sites, administrator consoles, and clients. After you apply this update to a site server, you can create client update packages.After the update is installed on site servers, any operating system boot images should be updated. To update boot images after the hotfix is applied, follow these steps:
-
In the Configuration Manager console, click Software Library.
-
In the Software Library workspace, expand Operating Systems, and then click Boot Images.
-
Select the boot image that you want to update.
-
Right-click and then select the Update Distribution Points action.Note This action updates all distribution points and may have an adverse effect on an environment that contains many distribution points.
-
Repeat steps 3 and 4 for all boot images that have previously been distributed.
Notes
-
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.
-
For more information about how to update boot images, see the How to Manage Boot Images in Configuration Manager topic on the Microsoft TechNet website.
Prerequisites
To apply this update, you must have Microsoft System Center 2012 R2 Configuration Manager installed.
Restart information
You do not have to restart the computer after you apply this update.Note We recommend that you close the Configuration Manager Administration Console before you apply this update package.
Hotfix replacement information
This update does not replace any previously released update.
File information
The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Configmgr2012ac-r2-kb2905002-x64.msp |
Not Applicable |
1,015,808 |
02-Nov-2013 |
02:09 |
Not Applicable |
|
Createtsmediaadm.dll |
5.0.7958.1101 |
2,034,864 |
01-Oct-2013 |
01:05 |
x64 |
|
Mcs.msi |
Not Applicable |
9,641,472 |
01-Oct-2013 |
01:05 |
Not Applicable |
|
Tscore.dll |
5.0.7958.1101 |
2,449,072 |
01-Oct-2013 |
01:05 |
x64 |
|
Configmgr2012ac-r2-kb2905002-i386.msp |
Not Applicable |
846,336 |
02-Nov-2013 |
02:09 |
Not Applicable |
|
Configmgr2012adminui-r2-kb2905002-i386.msp |
Not Applicable |
2,166,272 |
02-Nov-2013 |
02:09 |
Not Applicable |
|
Createtsmediaadm.dll |
5.0.7958.1101 |
1,619,632 |
01-Oct-2013 |
01:05 |
x86 |
|
Tscore.dll |
5.0.7958.1101 |
1,821,872 |
01-Oct-2013 |
01:05 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
