Jump to content


How does USMT store user state

No replies to this topic

#1 t-zwck



  • Super Moderators
  • 759 posts
  • 9828 thanks

Posted 10 July 2009 - 08:07 AM

How does USMT store user state?

Although there are a few different formats that one can choose from, we call all of them a "migration store."

The different formats are as follows:

Uncompressed migration store: choosing this format produces a containing a .dat file containing all files selected for the migration. Settings and other information are stored in an additional .mig file.

Compressed migration store: choosing this format produces a directory containing a single compressed file containing all files and settings included in the migration. This file has a .mig extension and cannot be opened without USMT.

Compressed and encrypted migration store: choosing this format results in the same experience as the compressed migration store, however the file is also encrypted with the provided key string.

Below are the Scanstate command line options needed to select the above Migration Stores.

Storage options


Indicates a folder where to save the files and settings (for example, StorePath cannot be c:). You must specify StorePath on the ScanState command line except when using the /genconfig option. You cannot specify more than one StorePath.

Overwrites any existing data in the store. If not specified, ScanState will fail if the store already contains data. You cannot specify this option more than once on a command line.

/encrypt /key:KeyString


/encrypt /key:"Key String"


/encrypt /keyfile:[Path]FileName
Encrypts the store with the specified key (password). Encryption is disabled by default. With this option, you will need to specify the encryption key with one of the following ways:

/key:KeyString specifies the encryption key. If there is a space in KeyString, you will need to surround it in quotes.

/keyfile:FilePathAndName specifies a .txt file that contains the encryption key

We recommend that KeyString be at least 8 characters long, but it cannot exceed 256 characters. /key and /keyfile cannot be used on the same command line. /encrypt and /nocompress cannot be used on the same command line.

You should use extreme caution with this option because anyone that has access to the ScanState command line script will also have access to the encryption key.

For example:

scanstate /i:miguser.xml /i:migapp.xml fileservermigrationmystore /encrypt /key:mykey

Disables compression of data and saves the files to a hidden folder named "File" at StorePathUSMT3. Compression is enabled by default. You can use the uncompressed store to view what USMT stored, troubleshoot a problem or you can run an antivirus utility against the files. You should only use this option in testing environments because we recommend that you use a compressed store during your actual migration. /nocompress and /encrypt can not be used on the same command line. However, if you do choose to migrate an uncompressed store, LoadState will migrate each file directly from the store to the correct location on the destination computer — without a temporary location.

For example:

scanstate /i:miguser.xml /i:migapp.xml fileservermigrationmystore /nocompress

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users




Test Providers

Site Info

Go to top