Fixing the Computer Replace uberbug in MDT 2012 Update 1 (With ConfigMgr)

When integrating MDT 2012 Update 1 with ConfigMgr 2007/2012 the Computer Replace scenario is unfortunately badly broken. How the test team could miss testing one of the core three deployment scenarios I don't know, but I know how to fix the bug.

Uberbug info

When using the Computer Replace scenario in ConfigMgr, unlike the Computer Refresh scenario, the state migration point is being used. To access content in the state migration store, the Request State Store action is used. In the standard client task sequence in MDT 2012 Update 1, that action is missing, leading to that the backup from the old computer is never restored.

In the smsts.log file you find the line: The action (Restore User State) has been skipped because the condition is evaluated to be false. Here is a sample smsts.log file.

The reason for the above is that the OSDStateStorePath property is never set (by the Request State Store action). When opening the task sequence you can clearly see that it's missing that action in the State Restore phase. The fix is to add a Request State Store action before Connect to State action, and set a condition so it's only used during a computer replace (and not during a computer refresh). You also need to add a Release State Store action after the restore has been completed, meaning after the Restore User State action.

Adding the Request State Store action before Connect to State action (also set the Restore state from another computer option, and select the If computer account fails to connect to state store, use the Network Access account):

Set a condition to the added Request State Store, to only be used during a computer replace, add a task sequence variable condition, the condition is USMTLOCAL not equals True (see below), also configure the action to Continue on error:

Then add a Release State Store action after the Restore User State action, and set the same condition. Also configure the action to Continue on error. Now you have a task sequence that looks like this:

You now have a working computer replace scenario in ConfigMgr 2012 integrated with MDT 2012 Update 1!

Here is a smsts.log file from a successful computer replace:

Happy deployment, Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Notify of
Oldest Most Voted
Inline Feedbacks
View all comments
10 years ago

Hi Johan,

I followed your steps but am noticing that after the pc images and comes up to ctl alt del screen that it actually did not finish. The _SmsTaskSequence folder is this still there and never deletes but the OS seems done. This only does this if a create a task with MDT combined with SCCM. If i run the straight SCCM deploy task it deletes it no problem. I am not seeing anything that stands out it logs. Any ideas or can i send the logs to you?


11 years ago

Yes, I have seen that too. Simply change another step (like change the name or description), and the Gather changes will be saved.

/ Johan

11 years ago

Hi Johan,

Great info as always.

Another question. I'm not sure if I'm the only one that has this issue regarding MDT 2012 Update 1 and ConfigMgr 2012 SP1.
I'm not able to change an MDT integrated step in my Task Sequence. E.g. If I try to change a "Gather" step to use another package, the "Apply" button is grayed out. And if presseing "OK" the package does not change.