Next USMT release

I wanted to take a moment here on the blog to let everyone know that we are continuing to invest in USMT and have aligned the next USMT release to coincide with the next release of Windows.  Please be assured that all of you will be the first to know when we have more information…



Thanks for all of your suggestions in the comments on the post "What do you want to see here? Any ideas?" that went live on July 3rd.  I am working on a post to address some of the questions in the comments regarding the config.xml file.  Hopefully I will be able to get this up…


What version of USMT can be installed on Windows Server 2003 or 2008?

Unfortunately, there isn’t a version of USMT that can be installed or executed on Windows Server 2003 or 2008.  As noted on the download page and in the user documentation, USMT is only supported on client versions of Windows.


What do you want to see here? Any ideas?

Is anyone out there?  Is there anything you’d like to see a blog post about?  I can’t guarantee that we will answer your question but I can promise that we will try.  Drop a comment and let us know.


Increasing MigXML efficiency

Increasing the efficiency of MigXML is all about making each individual include or exclude pattern as specific as possible and ensuring that the component operates in the proper context.  For example, the following component is extremely expensive to include in a migration: <component type=”Documents” context=”UserAndSystem”>   <displayName _locID=”All Word Documents”>User Data</displayName>   <role role=”Data”>    …


Why you need to be careful with /c

Scanstate and Loadstate both allow the /c switch to be used to skip non-fatal errors.  However, due to the impact that using it can have on a migration, great caution must be used when deploying Scanstate and Loadstate with /c.  To get started, here is what the help content has to say: When specified, ScanState…


About context in MigXML

If you have written a fair amount of migration MigXML you have probably noticed that there are a number of elements that take a context parameter.  Do you understand what this parameter controls?  Do you understand the impact that it can have on your migration?  We will work through a couple of examples here to…


Why Scanstate and Loadstate require a top level directory path to a migration store

If you have played around with USMT a bit you may have noticed that both Scanstate and Loadstate require that StorePath (the path provided on the command line to where you’d like the migration store placed) be simply a path.  However, when creating a compressed migration store (the default behavior) Scanstate places the .mig migration…


Why you want (and need) to run USMT as a local administrator

UPDATE: an updated post is available here. I’m leaving this post up to preserve the post history as well as comments. Although there are a limited number of scenarios in which USMT can be run without local administrator privileges, doing so ends up not being the most ideal situation.  There are a couple of reasons why:…