Do not do OSD in ConfigMgr 2012 R2 without this hotfix

For those of you doing OSD Deployment with ConfigMgr 2012 R2, you quickly learned that the RTM code was badly broken. PXE didn’t work on the site server, and deployment was just dead slow. Luckily Microsoft produced, in record time, a hotfix that address both issues. That hotfix was KB 2905002.

Update 2014-04-08: The CU1 uppdate contains this hotfix and should be used instead….

Install the new hotfix – KB 2910552

Then, a few weeks back, a new hotfix was released. A hotfix with the title “You cannot stage a Windows PE 3.1 boot image to a Windows XP-based computer in System Center 2012 R2 Configuration Manager”. By reading the title you might think, well I don’t do that, so this hotfix is not for me… Far from it, this new hotfix not only address the WinPE 3.1 boot image thing, it also fixes the other stuff.

Shorthand: The KB 2910552 hotfix replaces KB 2905002 (fixing the same stuff) as well as fixes the WinPE 3.1 boot image thing. So instead of installing KB 2905002, instead install the new KB 2910552. This is info is actually hidden well within the posts, if you read every line like three times… But guess what, most people don’t 🙂

image
Installing the new KB 2910552 hotfix.

Interesting note…

The new hotfix is updating the task sequence component to version 5.00.7958.1104…  The old KB (2905002) only to 5.00.7958.1101, wonder if something else was changed as well 🙂

image To  image

/ Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
5 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Admin
Admin
8 years ago

Indeed, thanks for the note Yan,

/ Johan

Yan
Yan
8 years ago

You can disregard CU1 is out.

Yan
Yan
8 years ago

Hello Johan I have used bootsect.exe from ADK 8.0 as a workarround to referesh XP machines. If I apply this hotfix 2910552 will I have to revert back to WinPE 3.1 boot images or I can keep using WinPE 5.0 boot images? thank you
Yan
I have a single TS for XP and Win7 refresh scenarios and would like to keep using WinPE 5.0

Admin
Admin
8 years ago

Corrected the typo, thanks 🙂

/ Johan

perazzi97
perazzi97
8 years ago

Johan, it looks like you have a typo for the new task sequence component version. You have in bold 5.00.7958.1004 and it should be .1104. Thanks for the great article we will be sure to apply this update instead of the old one when we do our R2 upgrade.


>