Hi All, I have been trying to do a client refresh scenario using sccm task with mdt 2010 integration. I am aware that by default, the mdt 2010 task sequence for capture/restore user state will set the store path locally. I have no issues on doing this on capturing a single partition source, then restoring to a single partition. My issue is with capturing a double (or multi) partition source machine, and restoring to a double partition setup. I am also aware that this involves USMT creating a main store, and a distributed store. No errors in scanstate.log, the problem is during loadstate, which in effect, does not restore user settings and files. The exact error in loadstate.log is the following: HARDLINK: cannot find distributed store for c - 17ec6a71-5b97-47d6-9cc6-85ab3db1d9b6[gle=0x00000003] [0x0802e3] SelectTransport: OpenDevice failed with Exception: Win32Exception: HARDLINK: cannot find all distributed stores. Unable to open store at D:\_SMSTaskSequence\StateStore\USMT[gle=0x00000003] [0x000000] Leaving MigOpenHardLinkStore method [0x000000] Failed to select store. Path: D:\_SMSTaskSequence\StateStore[gle=0x00000003] [0x000000] Internal error 23 was translated to a default error [0x000000] Failed.[gle=0x00000006] [0x000000] An error occurred during store access[gle=0x00000006] I can confirm that both state stores in drives C (main store) and D (distributed store) are present during loadstate. Any help would be appreciated. Thanks. Edit: I am also sure that I am using USMT 4 binaries.

is the distributed store, D:\_SMSTaskSequence\StateStore present ? or is it getting wiped (or on another drive) My step by step SCCM Guides I'm on Twitter > ncbrady

Im pretty sure nothing is getting wiped, since this is a refresh scenario (no format and partitions in TS). On a side note however, I have noticed that all of the Task sequence files _SMSTaskSequence are initially being placed in my D: drive (I assume that it goes to which partition has more space). Does this change anything?

if they are all on d: then you have no distributed store, the main 'store' will be on c:\_SMS.... the distributed 'store' will be on d:\_SMS... the actual task sequence step called apply operating system image will take care of the wiping for you, watch what it says next time you do a deployment can you verify if the c:\ drive is used at all for temp files during osd My step by step SCCM Guides I'm on Twitter > ncbrady

There is both C:\_SMSTaskSequence\StateStore\USMT and a D:\_SMSTaskSequence\StateStore\USMT, all the temp files for OSD are located in D:\SMSTasskSequence\ (Logs, Packages, and tsenv.dat). The Apply Operating System Image task does wipe my C:, but not my D: I'm pretty sure that both statestores are intact. By the way, thanks alot for the fast response and help. Also appreciate the guides you put up in windows-noob.com

This issue has bugged me for the longest time already, but not that big of an issue. I just wanted to leverage MDT 2010 for this scenario as it is very handy with the CustomSettings.ini customizability and MDT database integration.. I guess I'll have to stick with the hardcore offline + hardlinking at least for the state migration parts.. Using the offline + hardlinking task sequence everything is working fine in any scenario.. Just wished MDT is as properly documented as USMT.. On a different note, do you have any guides on how to do user state migration using SMP? Or does the out of the box task sequence from sccm work fine?