Jouu

http://support.microsoft.com/kb/958808 says that you need to use a different location other then %_SMSTSUserStatePath%. I understand your saying that it is straight forward and that may be so, however, I'm still attempting to figure this out and only getting more confused because the example just doesn't seem to be working properly for me. I also read http://technet.microsoft.com/en-us/library/bb680631.aspx and this essentially says that _SMSTSUserStatePath is a variable of its own, is that true? Operating System Image 1.Deletes all content on the target volume except files under the folder specified by the _SMSTSUserStatePath task sequence variable. 2.Extracts the contents of the specified .wim file to the specified destination partition. 3.Prepares the answer file: A.Creates a new default Windows Setup answer file (sysprep.inf or unattend.xml) for the operating system that is being applied. B.Merges any values from the user-supplied answer file. 4.Copies Windows boot loaders into the active partition. 5.Sets up the boot.ini or the Boot Configuration Database (BCD) to reference the newly installed operating system.

Double post

I have a task setup with an (OSDStateStorePath)variable. The original value was %_SMSTSUserStatePath% I tried it with this value then I also tried changing it to c:\MigrateData. Again the folder is showing up before the operating system is applied, but is wiped out when windows 7 does its wiping of data on the drive the image is being placed on. From reading other issues on the Technet forums this is something that configmgr will always do. I'm wondering what the solution to this is, is there something the locks the folder and prevents it from being wiped, or is there some script or something that is moving this folder to the X:\ drive and back during the applicatin of the image. I've read as much as I can on the Technet forums as I can regaurding hardlinking and its still a bit of a mystery.

I am trying to put a Task sequence together that saves the user data locally and migrates it in to Windows 7 from XP. I have been successful saving the data and creating a USMT folder with hardlink files in it. The problem is when the sequence continues the APPLY OS task does a "wiping" and I lose that folder. What are the ways I keep that folder intact for doing a load state later? Or, will the load state information pick up on what used to be there and pull it? Any help reguarding this would be great, I've been trying to figure this out in spare time for about 2 weeks now. Could someone please explain what takes place, and what it is I might be missing from the hardlinking example above.