Windows 7 / Getting Started

Loadstate.exe

You use LoadState to restore user state from the data store. By default, this program restores user state to the location from which ScanState originally saved it-unless one of the migration .xml files redirects it. You must specify the same migration .xml files to LoadState that you did to ScanState. The following describes an abbreviated syntax of LoadState, and Table below describes each command-line option.

Loadstate.exe [Store][/i:[path\]filename] [/hardlink /nocompress]

Loadstate.exe Command-Line Options

OptionDescription
StoreSpecifies a path to the data store.
/i:[path\]filenameIdentifies a migration .xml file to use when restoring user state data. You can use this option multiple times.
/config:[path\]fileSpecifies a Config.xml file. (See the section titled "Developing Migration Files" later in this tutorial for more information.)
/hardlinkEnables the creation of a hard-link migration store at the location specified by Store. You must specify the /nocompress option when using this option.
/nocompressDisables data compression. Use this option only with the /hardlink option or when testing in a lab environment.

Note LoadState supports many other command-line options. For a complete list of these options, see the USMT.chm help file in the Windows AIK.

Migration Files

Both ScanState and LoadState use three migration .xml files to control migrations. In addition to these three files, you can specify one or more custom .xml files to migrate custom applications or customize the standard migrations. The following section, "Developing Migration Files," describes the .xml files that come with USMT and how to build custom migration files.

[Previous] [Contents] [Next]