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”>    …

2

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…

2

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…

1

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…

0