In this 22 Minute video we walk through the process of upgrading a machine from Windows XP to Windows 7. There is no direct upgrade path from XP to Windows 7 so we are using the User State Migration Tool to migrate user data and settings. Note that this USMT example does not migrate OS or Applications. You will have to install the operating system and the applications on the destination computer. Some applications do not have to be installed on the destination computer. For details on what applications are covered in the MigApp.xml file check out the USMT Application blog post: Upgrading Windows XP to Windows 7 and Migrate Microsoft Office and Other Applications Using The User State Migration Tool (USMT)
You can find the downloadable files at the following URLs on Edge:
Right-Click, Save As below links…
Lite-Touch, High-Volume Deployment. This strategy requires limited interaction during deployment. Interaction occurs at the beginning of installation, but the remainder of the process can be automated. Microsoft recommends this strategy to organizations with a dedicated IT staff that have managed networks with 200–500 client computers. Prior deployment experience is not required but is beneficial for using this strategy. Personally, I would use this method for almost all size organizations. Maybe not to upgrade Gramma’s computer but certainly would for even small companies.
This step-by-step guide to Windows migration for IT pros provides a basic example of how to migrate files and settings from Windows XP to Windows 7 using USMT 4.0. (You can also migrate files and settings from a computer running Windows Vista®.) At the end of this process, you will have used the ScanState and LoadState tools to complete an end-to-end migration.
You can also customize your migration by editing configuration files used by these tools. For a comprehensive description of all of the tools and configuration files, see the User State Migration Tool (USMT) 4.0 User's Guide (Usmt.chm) downloaded with the Windows Automated Installation Kit (Windows AIK) or this Microsoft Web site.
In this example, you gather data from a source computer running Windows XP, create a migration store using the default settings in ScanState, install Windows 7 on a new or newly repartitioned computer, and then apply data from the migration store.
This process includes:
Step 1: Gather data using the Scan State toolStep 2: Install Windows 7Step 3: Apply data using the LoadState tool
Step By Step Detail…
Step 1: Gather data using the Scan State tool – From your XP or Windows Vista (SOURCE) computer…
cd \<USMTpath> <ENTER>
scanstate <USMTStorePath> /o /c /i:miguser.xml /i:migdocs.xml
Step 2: Install Windows 7
You can use an unattended answer file to customize your Windows 7 deployment. For more information, see Step-by-Step: Basic Windows Deployment for IT Professionals or the Windows Automated Installation Kit for Windows 7 RC
It is a pretty easy process even if you want to do it manually…
1. Insert Windows 7 DVD
2. Restart WindowsXP-to-7
3. BOOT TO DVD - WAIT
4. SHOW ENGLISH, click NEXT
5. Click Install Now.
6. Check Accept License Agreement
7. Click Custom (advanced).
8. Select DISK 0 Partition 1
9. Select Drive Options button
10. FORMAT, OK
Step 3: Apply data using the LoadState tool
Net Use G: <USMTpath>
loadstate <StorePath> /c /lac /lae /i:miguser.xml /i:migdocs.xml
If you want additional information on what applications can be migrated check out this blog post…
Upgrading Windows XP to Windows 7 and Migrate Microsoft Office and Other Applications Using The User State Migration Tool (USMT)
User State Migration Tool 4.0Windows Automated Installation Kit for Windows 7 RCStep-by-Step: Windows 7 Upgrade and Migration
Applies To: Windows 7, Windows Vista
This topic describes new features as well as changes in command-line options in Microsoft® Windows® User State Migration Tool (USMT) 4.0.
USMT 4.0 contains new ScanState command-line options. In addition, some command-line options have changed.
The following table lists new command-line options for the ScanState command.
/listfiles: "path to a file"
Generates a text file listing all the files included in the migration.
/p: "path to a file"
When an optional file location is specified, the /p option indicates that the new space-estimate algorithms are used. If you do not specify the optional file location, the /p option's functionality is the same as in USMT 3.0. These include an estimation of the disk space that is needed to create and build the migration store, as well as the space needed to host the migration-store contents. These estimates are provided in an .xml file at the location specified on the command line.
If the /nocompress option is also specified, the estimate will be for an uncompressed migration store. If the /nocompress option is not specified, the estimate will be for a compressed migration store.
Enables the creation of a hard-link migration store at the specified location. The /nocompress option must be specified with the /hardlink option. Additionally, the <HardLinkStoreControl> element can be used in the Config.xml file to change how the ScanState command creates hard-links to files that are locked by another application.
This option enables the volume shadow copy service to migrate files that are locked or in use by another application.
This option can be used only with the ScanState executable file and cannot be combined with the /hardlink option.
/auto: "path to script files"
This option enables you to specify the location of the default .xml files and then launch your migration. If no path is specified, USMT will reference the directory where the USMT binaries are located. The /auto option includes the following options /i:MigDocs.xml /i:MigApp.xml /v:13.
/offline: "path to an offline.xml file"
This option is used to define a path to an offline .xml file that specifies offline migration options; for example, an offline Windows directory to capture user state from, as well as remapping on drive letters and mount points.
/genmigxml: "path to a file"
This option specifies that the ScanState command should use the document finder to create and export an .xml file that defines how to migrate all of the files found on the computer on which the ScanState command is running. The document finder, or MigXmlHelper.GenerateDocPatterns helper function, can be used to automatically find user documents on a computer without authoring extensive custom migration .xml files.
/offlinewindir: "path to a windows directory"
This option specifies the offline Windows directory that the ScanState command gathers user state from. The offline directory can be Windows.old when you run the ScanState command in Windows or a Windows directory when you run the ScanState command in Windows PE. This option is incompatible with the /offline option.
/offlinewinold <Windows.old directory>
This command-line option enables the offline migration mode and starts the migration from the location specified. It is only intended to be used in Windows.old migration scenarios, where the migration is occurring from a Windows.old directory.
Creates a hard-link to the EFS file instead of copying it. Use only with the /hardlink and /nocompress options.
The following ScanState command-line options have changed in USMT 4.0.
Option in USMT 3.0Explanation for change in USMT 4.0
The /p option estimates the space needed to contain the compressed or uncompressed migration store. When an optional file location is specified, the /p:"path to a file" command-line option uses the new space-estimation algorithms.
/encrypt: "encryption strength"
You can specify a parameter to define the desired encryption strength for the migration store.
The /genconfig option now generates sample <ErrorControl> and <ProfileControl> sections in the Config.xml file that enable the new error control and local group migration behavior.
The /o option is now is required to overwrite both the migration store and the Config.xml file.
USMT 4.0 contains new LoadState command-line options. In addition, some command-line options have changed.
The following table lists new LoadState command-line options.
Enables user state data to be restored from a hard-link migration store. The /nocompress option must be specified with the /hardlink option.
This option enables you to specify the location of the default .xml files and then launch your migration. If no path is specified, USMT will reference the directory where the USMT binaries are located. The /auto option include the following options /i:MigDocs.xml /i:MigApp.xml /v:13.
The following LoadState command-line options have changed in USMT 4.0.
/decrypt: "encryption strength"
The /decrypt option now accepts a command-line parameter to define the encryption strength specified for the migration store encryption.
The /targetxp command-line option is no longer valid in USMT 4.0 because Windows XP is not supported on a destination computer.
The MigSys.xml file is no longer valid. This file was used only in Windows XP migrations where Windows XP was the operating system on the destination computer.
The /q option is no longer supported, because both the ScanState and LoadState commands require administrator privileges to run.
The following table lists all new Usmtutils.exe command-line options in USMT 4.0.
New option in USMT 4.0Description
This option returns a list of supported cryptographic algorithms (AlgIDs) on the current system.
Removes the directory path specified by the <storeDir> argument on all of the fixed drives. This command is useful for deleting hard-link stores that cannot otherwise be deleted due to a sharing lock. For example: usmtutils /rd D:\MyHardLinkStore
usmtutils /rd D:\MyHardLinkStore
I have had many questions about this post in regards to domains and staging machines. The answer has been System Center Configuration Manager. Yes, I was using USMT 4. Yes, USMT allows you to work in a domain with domain accounts. However, you have much more capability if you use System Center Configuration Manager which allows you to configure/stage and then execute machines on a schedule.
Kevin Remde has done a series of video’s on the topic…
I think the most relevant to you will be part 5 … edge.technet.com/.../Automating-Windows-7-Deployment-with-SCCM-2007-R2-SP2-Part-5-of-5
Where do you download the USMT program? And what version is needed? Do you have to make the folder a share? What do you you suggest if your desktop is joined with a domain and not by workgroup?
And later on in Win 7, Why do you have to map it to a G: drive instead into the C:?
Dan: do you have any feel for how many desks have been migrated to Win7 using USMT? Can you suggested any commercial tools? thx /cliff
Great Mr. Dan,
I hope your day is going well. However, i sent this (the below) to expert exchange and they directed me to your site.
Great day all,
I have a government agency that is planning to move from XP to Windows 7. Presently they are using 2003 servers and planning in the future to upgrade them to server 2008 before Microsoft discontinues phone support. Nevertheless, I was tasked to build the image for windows 7 and build a container or OU’s that mirrored the 2003 Active directory structure and create new GPO’s that would meet the USGCB standard setting and apply them to the new test mirrored Active directory structure for the new windows 7 roll out. I am glade to say that I have finished the GPO’s and applied them to Test OU’ and it works well with the exception of it not applying the roaming profile from the 2003 server.
The quandary I am having is why it would not apply my profile from the server on its own. Therefore, as test I copied my desktop from my XP to my window 7 by using the run \\mymachine\c$. After which I logged on to a different widows 7 machine and my desktop showed up but without my background. Once that test was complete I create another test user account with roaming a profile. Logged with the account, created some folders on the desktop and background logged off and on to make sure the profile was uploaded. I then logged on to a Windows 7 machine and nothing showed up. Then finally made some changes to the GPO’s --- Computer Configuration > Policies > Administrative Templates > System > User Profiles, Enabled- and type then \\server\users\%usersname%\sytem\profile and \\server\%username%\system\profile.
I have ran what you have on your site but i am geting usmt status 1030 <undefined_option): An error occured processijng the command line undefined or incomplete command line option.
this is what i enter in the cmd c:\usmt>scanstate \\server-to01\data\users\joe.black\usmt\migration\mystore o/ /c /i:migapp.xml /i:miggocs.xml and
c:\usmt>scanstate \\server-to01\users\joe.black\usmt\migration\mystore o/ /c /i:migapp.xml /i:miggocs.xml
So can you show me where i went wrong?
I would like to just migrate Windows 2003 TS roaming profile to Windows 2008 RDS user roaming profile. Can I use this tool to do?
Just use USMT GUI for the user migration.
The ©USMT 5 utilities package is, by courtesy from ©Microsoft, included with the USMT GUI installer.
To view or extract files from .MIG files please see Mike Morawski's Mig Recovery and Viewer Utility
USMT is some of the best technology. Need that for SharePoint upgrade/migration.