At recent TechNet events, I had questions about migrating applications using the User State Migration Tool (USMT). As I suspected, there is support for migrating some applications including Microsoft Office. In fact, for Microsoft Office it can even migrate settings from an older version of office on the source machine to a newer version of office on the destination machine. In case you need to know more about running the USMT tools, check out this post: Migrate Windows XP to Windows 7 Using USMT (User State Migration Tool) [Upgrade XP or Vista] Step By Step. Here are the full details on what applications can be migrated (without customization) using the migapp.xml configuration file…
Applies To: Windows 7, Windows Vista
Microsoft® Windows® User State Migration Tool (USMT) 4.0 is designed so that an IT engineer can precisely define migrations using the USMT .xml scripting language. USMT provides the following sample scripts:
This section describes the user data that USMT migrates by default, using the MigUser.xml file. It also defines how to migrate access control lists (ACLs).
Note The asterisk (*) stands for zero or more characters.
Important To migrate ACLs, you must specify the directory to migrate in the MigUser.xml file. Using file patterns like *.doc will not migrate a directory. The source ACL information is migrated only when you explicitly specify the directory. For example, <pattern type=”File”>c:\test docs</pattern>.
<pattern type=”File”>c:\test docs</pattern>
USMT migrates operating-system components to a destination computer running Windows 7 from computers running Windows XP, Windows Vista, or Windows 7.
Note: If you are using USMT 4.0 to migrate a user state to Windows Vista instead of to Windows 7, use the /targetvista option with the ScanState tool. Without the /targetvista command-line option, some operating-system settings can be lost during the migration. For more information, see ScanState Syntax.
The following components are migrated by default using the manifest files:
* These settings are not available for an offline migration. For more information, see Offline Migration.
Important: This list may not be complete. There may be additional components that are migrated.
Some settings, such as fonts, are not applied by the LoadState tool until after the destination computer has been restarted. For this reason, restart the destination computer after you run the LoadState tool.
Although it is not required for all applications, it is good practice to install all applications on the destination computer before restoring the user state. This ensures that migrated settings are preserved..
Note: The versions of installed applications must match on the source and destination computers. USMT does not support migrating the settings of an earlier version of an application to a later version, except for Microsoft Office.
Note USMT migrates only the settings that have been used or modified by the user. If there is an application setting on the source computer that was not touched by the user, the setting may not migrate.
The following is a list of the settings that USMT does not migrate. If you are having a problem that is not listed here, see Common Issues.
USMT 4.0 does not migrate the following application settings:
USMT 4.0 does not migrate the following operating-system settings.
I've been reading technet RE: USMT 4.0, googled around and stumbled upon your video on youtube which is very very helpful.
I've used 2.6 and 3.0 before and used inf instead of the xml to migration from XP to XP.
I'm really interested in HardLink, but I'm not sure if it's the best solution to what I will be using.
We are a IT consulting company a gold partner of Microsoft and I'm just wondering if you don't mind answering some of my questions...
But before that let me describe of what we would like to be able to do.
Our clients are mixed between XP and Vista and some of them are already on Windows 7.
I'm just trying to find what would be the best USMT solution to migration between:
- XP to win 7
- Vista to Win 7
- Win 7 to Win 7
As you know that the latest USMT is version 4.0
My Questions are:
1. I can't seems to find loadstate & scanstate for the latest version. is version 4 USMT consists of version 3 loadstate & scanstate plus xmls of version 4?
2. for our scenarios, will lite touch be adequate or hardlink will be the better bet?
USMT 4 will cover all of your scenario's. The requirement for USMT 4 is that the Destination (Loadstate) has to be on either Vista or Windows 7. You can download the USMT it is in the AIK (Automated Installation Kit). When you install the AIK, you will see USMT under the Tools folder. On my installation (which I think I took defaults) it is C:\Program Files\Windows AIK\Tools\USMT Under that folder select either amd64 or x86 folder. In my installation the ScanState.exe shows a version of 6.1.7600. You can download the Windows Automated Installation Kit for Windows 7 from http://technet.microsoft.com/en-us/library/dd349343(WS.10).aspx
I have used Win7 to Win7 already and it works great. It is the perfect tool to go from 32bit to 64bit or going from Eval to Production
The HardLink switch is for an UPGRADE on the same physical box where you will not be formatting or changing partition sizes. If you are using the same box and not formatting for any reason, you can use Hardlink. If you want to format or change disks, move to a different computer, etc. you would need to use Lite Touch without the Hardlink switch.
Hope I answered your questions completely. If not, please let me know
That hardlink reply made me wonder about something. One of the scenarios that my company will be dealing with will be upgrade in place, and then running SCANSTATE against the Windows.OLD and then running LOADSTATE, specifying the output of Scanstate. Would HARDLINK still be used in that scenario?
This is NOT the way the ScanState was designed. I am not familiar with any switches to be able to do that. Sure you could select folders from the Windows.OLD but then on the destination they would be put back to the same folder structure (windows.old) and you would have to move them manually. The AWESOME Part of the USMT is that it automatically puts stuff where it goes (desktop to desktop, favorites to favorites, docs to docs, etc). Since these locations all moved with the new rev (from \Docs and Settings to \Users that would be a manual process to do it the way you suggest.
I am looking to implement USMT 4.0 with hardlink migration but I'm a bit new to this. I am using MDT for my deployment and I would like to kick off USMT to automate the migration. We would be reimaging XP, Vista, and Windows 7 all with Windows 7.
Hi Bryan, Sorry, Is there something in particular that you need help with? All of this is possible with USMT/MDT. In fact, that is exactly what it was designed for.
When doing hardlink migration,What is the fail safe or recovery process if the process fails
if you are concerned about a hard drive crash, you should NOT use hardlink migration. There is no safety net with hardlink.
I need help. We are trying to use USMT Hardlink migration using SCCM. What is the back out process if the hard drive crash. Does any one experience this ?
Hey, I was wondering how would I upgrade my microsoft word 2003 to microsoft word 2007...
You may consider to use WET (windows easy transfer) and PickMeApp: two free solutions to migrate from XP to Windows 7. WET may transfer your XP settings to Win 7 while portable PickMeApp tool may transfer programs from XP to Windows 7. PickMeApp claims to support unlimited number of programs.