I am encountering a problem with USMT 5, used in a ConfigMgr 2012 task sequence, that I have some trouble understanding. When collecting the data with scanstate (for Win7 to Win7 computer backup/restore, with migapp.xml, miguser.xml and a custom xml), scanstate abruptly stops, and the log jumps directly to 100%. Then the Task sequences throws a 80070003 error. The same also happens when using the default settings for capture in ConfigMgr.
Has anyone ever encountered this ? Any hep would be welcome.
I stored the smsts and scanstate logs and custom XML here for reference : http://sdrv.ms/14KnzkK
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.
Hello
I am encountering a problem with USMT 5, used in a ConfigMgr 2012 task sequence, that I have some trouble understanding. When collecting the data with scanstate (for Win7 to Win7 computer backup/restore, with migapp.xml, miguser.xml and a custom xml), scanstate abruptly stops, and the log jumps directly to 100%. Then the Task sequences throws a 80070003 error. The same also happens when using the default settings for capture in ConfigMgr.
Has anyone ever encountered this ? Any hep would be welcome.
I stored the smsts and scanstate logs and custom XML here for reference : http://sdrv.ms/14KnzkK
Share this post
Link to post
Share on other sites