Home > Windows 7 > USMT & Config.xml

USMT & Config.xml


When using the User State Migration Tool (USMT) you can exclude items from migrating such as gadgets or a theme you can create "Config.xml".  To do this you need to run the following command*:
 
scanstate.exe /genconfig:yourconfig.xml
 
Then you can edit the XML file to exclude these items.  For example if I do not want gadgets to migrate I would change the following line to say "No" instead of "Yes".  Then you need to use the "/config:yourconfig.xml" while using Scanstate to capture the settings.
 
<WindowsComponents>
    <component displayname="gadgets" migrate="yes" ID="gadgets">
 
* You need to run this on the source OS.  For example if you are using USMT to capture files from Windows XP to Windows 7 you should create the XML on a Windows XP device.  This will ensure that Scanstate will not capture
Advertisements
Categories: Windows 7
  1. Sadiq
    April 19, 2011 at 12:58 pm

    How to create the custom.XML , Do we need to use the default migapps.xml and miguser.xml with custom.XML ? How can we specify it in the customsettings.ini?

  2. Sadiq
    April 19, 2011 at 9:52 am

    Thanks, My D is fixed drive. Will this script “D:\*'[*.*] +++” will exclude even the folders and subdolfers in D Drive? You recomment using custom.XML or config.xml, Also how the USMT settings in CS.ini? if config.xml , will it work only with this script as shown? or i need the complete xml file created by genconfig ? in this case where can i put this script?

    Test

    d:\*[*]

    </migration

    • April 19, 2011 at 12:08 pm

      I suggest always going with custom.xml for any modifications to the process such as this. As far as the script goes I would suggest trying it and see what happens. I have not done this in production myself.

  3. Sadiq
    April 18, 2011 at 9:15 am

    I want to exclude my entire D drive from the USMT, how can i do that…I dont see anything called “Data backup=d drive migrate =no”. Please let me know

    • April 18, 2011 at 10:33 am

      I guess the answer is that it depends on how you are trying to approach the SCANSTATE. If your “D:\” drive is not a fixed drive (i.e. not USB or network drive) you can use “/localonly” with SCANSTATE.EXE. But, if your “D:\” drive is fixed you can try:

      http://technet.microsoft.com/en-us/library/cc722303(WS.10).aspx

      D:\* [*.*]

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: