Jump to content


Config Mangler

Critical problem with SCCM 2012 R2 - OSD from Software Center

Recommended Posts

Hope this isn't a repost. Watch out for this if you are doing an in-place upgrade using the SCCM Software Centre on XP.

 

This has stopped our XP -> Win 7 rollout in its tracks and I would advise not upgrading to R2 until this is fixed.

 

When you do an OSD it copies down the boot.wim and you get error 800700C1

 

Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR

 

Since R2, bootsect.exe is not compatible with XP. To make matters worse, when you reboot the XP machine you get NTLDR not found and the machine is a brick.

 

There is a relatively easy workaround which is replacing the bootsect.exe in the boot.wim with an older one, but it's not supported and I don't know what else is affected. I'll try this in my lab but have logged a MS premier call for advice.

 

It's supposed to be fixed in SCCM 2012 R2 CU1

 

http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd

 

 

 

 

 

Share this post


Link to post
Share on other sites

Microsoft has released a hotfix for this KB2910552 to address the issue. It is supposed to be addressed in CU1 as well. For more information on the hot fix see:

http://davejaskie.wordpress.com/2014/03/30/system-center-configuration-manager-sccm-2012-r2-and-xp-migrations-require-hotfix-2910552-to-ensure-no-ntldr-missing-error/

Share this post


Link to post
Share on other sites

I just applied the x86 client update from R2 CU1 to an XP machine and I still get the same error when using Software Center to do OSD. Going to try downloading the KB it self and try that, (maybe it's not been included in CU1???)

 

Phil

Share this post


Link to post
Share on other sites

I updated my post. Phil, I believe the issue that you are encountering is a result of using an ADK 8.1 based image instead of the ADK 8.0 image. You can determine this by checking OS version on your boot images. The supported boot image will state 6.2.9200.x instead of 6.2.9600 .x

 

Information of how to use an older PE to support XP Migrations:

http://davejaskie.wordpress.com/2014/04/03/installing-a-legacy-boot-image-in-sccm-to-support-xp-migrations

 

Updated Blog Post:

http://davejaskie.wordpress.com/2014/03/30/system-center-configuration-manager-sccm-2012-r2-and-xp-migrations-require-hotfix-2910552-to-ensure-no-ntldr-missing-error/

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.