Hi, I have created a ts that deploys windows 7. I migrate user state using the hardlink option. I have created a config.xml file that I want to use with the capture of user state. I testet this config.xml with the command: scanstate.exe j:\%computername% /nocompress /c /i:migapp.xml /i:miguser.xml /config:config.xml /o The above migrate exactly what I defined in the config.xml. But how should this be implemented in my ts? I created the OSDStateStorePath (%SystemDrive%\UserState), OSDMigrateAdditionalCaptureOptions (/hardlink /nocompress) and in capture user state I have added the migapp.xml, miguser.xml and config.xml. When I run the ts nothing is captured (the capture task runs but the USMT folder is empty) I tried removing the config.xml entry and instead I added /config:config.xml. The restult was the same as above. I also tried running the ts without config.xml anywhere. The result was still the same. Finally I tried to run the task "capture user state" task just with default options. Now everything is captured - but I really need to limit what is captured so I need the config.xml. I hope somebody can help.

in your task sequence before the capture user state step, add a new Set Task Sequence Variable step called Set Hard-link Scan Parameters which has the following: (and include any other changes you want included, this is just an example of how to add it) OSDMigrateAdditionalCaptureOptions set the values to /hardlink /nocompress /config:config.xml does it work then ? you can verify what scanstate.exe uses by looking at your scanstate.log file after it's done, by the way you'll need to use a similar line in your Restore State step, except rename it to: Set Hard-link Load Parameters with OSDMigrateAdditionalRestoreOptions as the variable cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

HI Niall, it is already there. But in the scanstate.log I could see that scanstate.exe simply could not find the config.xml file. I entered the full path to this file instead ( /config:C:\_SMSTaskSequence\Packages\TKD00007\x86\config.xml) and it works now. Entering the full path is fine, but I really do not understand why that is nessacery. Did I configure something incorrect? Anyway thanks for your clue regarding scanstate.log. I was not aware of this log file.