Configuring XML/USMT for only collecting 14 items (Best Practices)

Question

I am using the USM GUI tool for doing singular migrations.

I only have to capture the following items. (see list below)

I know how to combine the MigUsers and MigApps, to create the config.xml.

I have tried to edit that config.xml to say no to everything except what I "Think" I need. It has been frustrating to configure what I think I need with the cryptic naming in the confix.xml.

Question #1.

Is there any definitive reference to what the config.xml handles? (Translates the "Display Name" item to the actual components they handle?) I found some outdated ones from back in the XP days. not sure how current they are.

Question #2.

Is there any solid "best practices" for making such a limited capture?

Question #3

Will reducing the MigUsers and or MigApps broad scope be frowned upon?

Question #4

The inventor of USM tool has sent me an XML file that captures the registry and file locations of the below items. Standard .xml, not the "Config.xml" style. Is there a way to just capture that or integrate that into the only thing I capture. (Currently using .bat files to capture the settings below, he converted that to .xml) (see list below the items needed list)

ITEMS NEEDED:

Office Settings: Dictionary

Templates

StickeyNotes

OneNote

Outlook Signatures

Input Settings:

Mouse

Keyboard

Accessibility

Cursors

OS Config: Mapped Drives

Wallpaper

ODBC

Network Printers

Quick Access Links

Favorites:

Edge

Chrome

Here is the .xml representation of what I want to capture.

XML Created by owner of USM tool:

<?xml version="1.0" encoding="UTF-8"?>

<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/MigrateFoldersAndRegs">

<component type="Application" context="UserAndSystem">

<displayName>Additional files</displayName>
```   <role role="Settings">

```xml
<rules context="UserAndSystem">

 <include>

  <objectSet>

  	<!-- Themes - Files -->

		<pattern type="File">%CSIDL_APPDATA%\microsoft\windows\Themes\* [*]</pattern>

	<!-- Quick Access Links - Files -->

		<pattern type="File">%CSIDL_APPDATA%\microsoft\recent\automaticdestinations\* [*]</pattern>

	<!-- Office - Files -->

	<pattern type="File">%CSIDL_APPDATA%\microsoft\UProof\* [*]</pattern>

	<pattern type="File">%CSIDL_APPDATA%\microsoft\Templates\* [*]</pattern>			

	<pattern type="File">%CSIDL_APPDATA%\microsoft\Signatures\* [*]</pattern>


	

	<pattern type="File">%CSIDL_Local_APPDATA%\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\* [*]</pattern>

	<pattern type="File">%CSIDL_Local_APPDATA%\Packages\Microsoft.Office.OneNote_8wekyb3d8bbwe\* [*]</pattern>


	

	<!-- %CSIDL_APPDATA% is migrated users "Appdata\Roaming". %CSIDL_Local_APPDATA% is "Appdata\Local" -->

	<!-- Other example: -->

	<!-- <pattern type="File">%CSIDL_COMMON_APPDATA%\"some folder"\* ["Specific file*"]</pattern> -->

	<!-- %CSIDL_COMMON_APPDATA% is "C:\Programdata"-->

   </objectSet>

</include>
```   </rules>

  </role>

</component>

<component type="System">

  <displayName>Additional Registry keys</displayName>

  <role role="Settings">

   <rules context="UserAndSystem">

```xml
 <include>

  <objectSet>

  <!-- ODBC - Registry -->

      <pattern type="Registry">HKCU\SOFTWARE\ODBC\* [*]</pattern>

      <pattern type="Registry">HKLM\SOFTWARE\ODBC\* [*]</pattern>

	  <pattern type="Registry">HKLM\SOFTWARE\WOW6432Node\ODBC\* [*]</pattern>

  <!-- Mouse - Registry -->		  

	  <pattern type="Registry">HKCU\Control Panel\Mouse\* [*]</pattern>

  <!-- Keyboard - Registry -->		  

      <pattern type="Registry">HKCU\Control Panel\Keyboard\* [*]</pattern>

  <!-- Acecessibility - Registry -->

      <pattern type="Registry">HKCU\Control Panel\Accessibility\* [*]</pattern>

  <!-- Cursers - Registry -->

      <pattern type="Registry">HKCU\Control Panel\Cursors\* [*]</pattern>	  

	 <!-- <pattern type="Registry">HKCU\SOFTWARE\JavaSoft\Prefs\com\partnersoft\* [*]</pattern>

      <pattern type="Registry">HKLM\SOFTWARE\Canon Electronics Inc.\* [*]</pattern> -->

  </objectSet>

 </include>
```   </rules>

  </role>

 </component> 

</migration>

Answer 1

Hi, @Johnston, Roman

Thank you for posting in Microsoft Q&A forum.

Question #1:

The Config.xml file is the configuration file created by the /genconfig option of the ScanState tool. It can be used to modify which operating-system components USMT migrates. For more information about the Config.xml file, see Customize USMT XML Files and Config.xml File.

Question #2:

Microsoft recommends creating a separate .xml file instead of adding .xml code to one of the existing migration .xml files. Custom .xml files shouldn't be created to alter the operating system settings that are migrated. Manifest files determine what settings are migrated. Manifest files can't be modified. Since manifest files can't be modified, to exclude certain operating system settings from the migration, create and modify a Config.xml file instead. For more information on best practices, see USMT Best Practices.

Question #3:

Reducing the scope of MigUsers and MigApps is acceptable and can be done by creating a custom Config.xml file. For more information, see USMT Exclude Files and Settings.

Question #4:

The inventor of the USM tool has sent an XML file that captures the registry and file locations of specific items. This XML file can be integrated into the Config.xml file by adding the appropriate rules. For more information on creating custom XML files, see Creating and Editing a Custom XML File.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".