User State migration tool (USMT) 2.6 integration with SMS 2003 OS Deployment Feature pack
I blogged about the SMS 2003 OS deployment feature pack the other week, and how good the support for USMT 2.6 was. I've finally got around to having a play with migrating some data to my spare machine. It's fantastic! As long as the USMT installation folder is accessible through a UNC path, and you've specified where to store the user state data, then it works like a dream. I grabbed it from the download centre and had a play with Scanstate and Loadstate command line tools. Scanstate captures an intermediate store like a server or CD drive, with the user files and settings from the source computer. Loadstate restores these files and settings to the destination computer. Here is the syntax for both commands:
scanstate <MigrationPath> [/i <InfFile> [/i <InfFile> [...]]] [/l <LogFile>] [/v <number value>] [/f] [/u] [/x] [/c]
loadstate <MigrationPath> [/i <InfFile> [/i <InfFile> [...]]] [/l <LogFile>] [/v <number value>] [/f] [/u] [/x]
By default, the OS Deployment Feature Pack saves the user state data locally on the destination computer, which is the most secure location as it doesn't impact the network.
Very useful indeed, and so easy to use...