Hi All, We are achieving ZTI by using MDT w Database Configured and integrated with SCCM, everything is working fine along with OS Deployment, PXE, Refresh and New Scenario, Software Deployment, Updates, Drivers etc. only the issue which we are facing is with User State Migration, that is when we upgrade windows xp machine to windows 7 by advertising the TS, it gets the TS and start capturing the user state, we have SMP configured as well but since local disk has enough free space thats why it's selecting local store, saves the state and restart in to WinPE...now the problem is when it comes to applying OS Image, by default it wipes the partition which contains Hard Link Store and User State and apply the image, then it applies all required drivers, updates and software but when it comes to restoring the user state it doesnt find USMT path where it stored the User State previously hence user data lost and TS stopped with error...be informed that there is no customization in TS, its a default MDT Integrated Task Sequence. how can we overcome this situation? any best practice and recommendations? secondly can we define D drive for hard link if TS selects store as local? we want this to be dynamic like if there is space available locally it should save in D Drive and there is no space then SMP. Soonest response, best practices and suggestions would highly be appreciated.

I assume you have USMT 4.0. If you're using /hardlink for hardlink migration, Windows XP not supported as a source machine to capture user state. Not sure but I think, either you can use local store or remote (SMP). Yes, You can use D drive too for hardlink migration store, see http://technet.microsoft.com/en-us/library/dd560753(WS.10).aspx#BKMK_LocationModify Regards,

That not true, XP totally supports hardlinking, as long as you restore to win7.. I set up that exact scenario a couple of weeks ago at a customer.. I kind of ran into the same problems that you experience, and it turned out to be a problem with USMT actually placing the hardlink store on the D partition rather than C which makes the restore fail. The workaround is to create a fixed OSDstatestorpath, as i describe here http://blog.coretech.dk/mip/personal-notes-nr-1-usmt-4-0-with-multiple-partitions/ MichaelMichael Petersen http://blog.coretech.dk/mip/

Hi Michael, thank you for the prompt response :) That's exactly i was saying and got the solution but was wondering in which step should i add that variable? just want to clarify, you have specified that "Add a TS variable OSDStateStorePath = %SystemDrive%\StateStore, just after the “Determine Local or Remote UserState” Step." which means that variable would be added in "Request State Store" or "Capture User State" ??? please clarify. and i can add D:\StateStore ?? and it will create the statestore folder itself? i also want to add one more variable that all local users should automatically be created in windows 7 and their state should be restored. looking forward for the soonest response. Regards MYM

reading below link: http://technet.microsoft.com/en-us/library/bb680924.aspx found that variable is supported by all tasks related to User State Migration therefore i think it would be better to use the variable with Capture and Restore Tasks. what do you suggest?

The Determine Local or Remote UserState Step will set the hardlink settings, which means that the Request State Store will not run (check options on the step). The OSDStateStorePath must point to the partition where th OS will be installed or the restore process will fail (at least according to the KB). If you want to use the D drive you should not use the MDT scripts, but create your own steps to use local store (which will do file copy and be slower) and have that point to the D drive. Michael Petersen http://blog.coretech.dk/mip/

that means i will have to set c:\statestore path as OSDStateStorePath, so would it not be wiped again when whole C drive would be wiped by Setup? and secondly according to KB Article, that path should exist...what is your experience? would setup create the folder automatically or we'll have to create the folder using TS or some other mechanism. and will have to configure OSDStateStorePath in Capture State and Restore State.

if you want an example of storing userstate elsewhere than the default, using the OSDSTateStore path for both scanstate and loadstate tasks then checkout the windows-noob.com FrontEnd HTA v1.0, it's got that and a lot more (eg: do offline scanstate, xcopy the store to a network share (not SMP) then restore same later using a drop down menu Introducing the windows-noob.com FrontEnd HTA version 1.0 Multipurpose HTA My step by step SCCM Guides I'm on Twitter > ncbrady

If you use hardlink, there will be an option on the diskpart step, not to run. That means the apply os step will clean the disk, leaving that statestor Dir intact, as well as the d drive. you must configure OSDStatestorPath in a separate "add Task Sequence variable" step, before the capture state step. once set, it will carry trough the entire TS, so no need to worry about the restore part!Michael Petersen http://blog.coretech.dk/mip/

Hi Michael, I tested the variable its working fine :) thank you so much for your prompt support, much appreciated. I have another challenge here, no matters whichever scenario i am deploying i.e. Refresh Scenario or New Computer, both works fine but OS gets installed on D Drive and C Drive becomes the data drive however i have specified in my TS if new computer then create two partitions of same size in which 1st one would be OSDisk and Second would be the data disk and same applies to Refresh Scenario with no repartitioning, i.e. an XP machine which has OS installed on C Drive, it successfully migrates to windows 7 but then D Drive becomes the OS Disk while C becomes Data Disk. I think it only changes the Drive Letter. any idea why it is happening? and how to fix it? Regards

Hi Michael, any idea why OS Disk becomes D Drive and Data Disk becomes C Drive? it is not changing the partition but only changes the Drive Letter i.e. OS Disk is still Disk 0 and Partition 0 however drive letter is changed to D Drive Only. your soonest response would highly be appreciated. Thanks

your soonest response would highly be appreciated. You should call Microsoft support if you need immediate assistance. I guess you are using the .wim file from the DVD instead of a captured reference computer. See http://blogs.technet.com/b/inside_osd/archive/2007/08/08/why-does-vista-end-up-on-the-d-drive.aspx for details.Torsten Meringer | http://www.mssccmfaq.de

thank you Torsten for the prompt support and this is what i call soonest response :) and the link contains exactly same piece of information i was looking for. much appreciated.