Archive: SCCM 2012 R2/ADK 8.1 does not support OS migration from WinXP

BrandLogoWindowsFor those who are considering the upgrade to SCCM 2012 R2, make sure that you have already upgraded your workstations Windows XP to Windows 7! Configuration Manager 2012 R2 requires the WIndows 8.1 ADK (formerly WAIK) which does not natively support migration from Windows XP (or even Vista) using USMT6 or WinPE. You will receive a 0x800700C1 error message during your task sequence while your WinPE boot image is staging. There is a workaround available, but it’s not officially supported by Microsoft. I’d recommend following this thread for more information on the workaround and a potential fix from Microsoft.

I will be using SCCM 2012 R2 to migrate a large client base from WinXP to Win7 in the coming months, with or without official Microsoft support, so stay tuned!

UPDATE 2013/11/14:

Here’s a blog post by the ConfigMgr team on how to upgrade from WinXP to Windows 8.1 using SCCM 2012 R2.

It’s also rumored that Cumulative Update 1 for SCCM 2012 R2 will bring back this support.

UPDATE 2013/12/3:

Some of you probably already know this, but the easiest fix for this currently is probably just to split your task sequences into two parts, where the “reboot into Windows PE” would normally be. Your first task sequence runs the user state capture and stores the data on the State Migration Point, and the second task sequence runs the OS install and user state restore. This side-steps the bug. Just be sure to initiate the second task sequence from PXE or USB boot media (and make the deployment available to boot media, also).

UPDATE 2014/2/3:

A hotfix has been released to correct this issue.

6 thoughts on “Archive: SCCM 2012 R2/ADK 8.1 does not support OS migration from WinXP”

  1. One other thing not mentioned here: the srndcoaey sites in your hierarchy must be running SQL 2012 Express SP1 (SCCM 2012 installs the non-SP1 version by default), or you’ll end up with a prerequisite check failure when attempting to upgrade the site from the console. The error will be something about either not having admin to the SQL instance, or that the instance couldn’t be contacted.Hope that helps someone!

  2. Thanks for the post Kevin. We are trying to follow the System Center blog about creating a USMT 5.0 package from ADK 8.0. Our Windows 7 to Windows 7 migrations run just fine. When we run the scan state step on a Windows XP box for either side by side or in place migration, the data successfully uploads to our SMP. However, the user state data doesn’t get downloaded correctly. The logs error out with an USMT Error 14 but the only has to do with a local admin that we are not migrating. Any suggestions?

Comments are closed.