SCCM OSD "Wipe and Load"

Is there a way to utilize the State Migration Point during a wipe and load Task Sequence so that the User State is stored remotely and the disk can be re-formatted, and the user State restored to the Same Machine.  Right now OSD and USMT are working and we are able to create associations for NEW machines, but not to reload existing ones.

Any help would be appreciated.

Thanks

MeridianBio
MeridianBioAsked:
Who is Participating?
 
HayesJupeCommented:
what you've described is typically referred to as a "refresh" in OSD terms.
The standard client task sequence, when imported from the available MDT sequences, does this by default. Just disable or remove the "determine state store" step, which will force the user state to always use the state migration point.
0
 
MeridianBioAuthor Commented:
During the Restore sequence Step, How does the Client know to restore the State back to itself?
0
 
HayesJupeCommented:
sccm takes care of that... basically because you are backing up and restoring user state to/from a machine with the same details.
During the state restore step, SCCM will always check if there is any user state stored against that machine ID.... and, when the machine ID is the same as before, there is.
0
 
MeridianBioAuthor Commented:
Thank you for the assistance.  I am still having problems getting the client to accept and start the Task Sequence but You have answered my question.  Thank you again.

MeridianBio
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.