Metadata update deployment/usmt 19

2025-06-18 03:43:39 +00:00 · 2022-11-04 16:06:43 -04:00
parent dcb4956e19
commit 34b0f37930
2 changed files with 283 additions and 318 deletions
--- a/windows/deployment/usmt/usmt-what-does-usmt-migrate.md
+++ b/windows/deployment/usmt/usmt-what-does-usmt-migrate.md
@ -150,8 +150,10 @@ The following components are migrated by default using the manifest files:
 Even though it's not required for all applications, it's good practice to install all applications on the destination computer before restoring the user state. Installing applications before migrating settings helps to ensure that migrated settings aren't overwritten by the application installers.
 > [!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.
+> 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.
-> - 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.
+
 > [!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.
 When you specify the `MigApp.xml` file, USMT migrates the settings for the following applications:
--- a/windows/deployment/usmt/usmt-xml-elements-library.md
+++ b/windows/deployment/usmt/usmt-xml-elements-library.md
@ -15,21 +15,9 @@ ms.technology: itpro-deploy
 This topic describes the XML elements and helper functions that you can employ to author migration .xml files to use with User State Migration Tool (USMT). It is assumed that you understand the basics of XML.
-## In this topic
+In addition to XML elements and helper functions, this article describes how to specify encoded locations and locations patterns, functions that are for internal USMT use only, and the version tags that you can use with helper functions.
-In addition to XML elements and helper functions, this topic describes how to specify encoded locations and locations patterns, functions that are for internal USMT use only, and the version tags that you can use with helper functions.
+## Elements and helper functions
 -   [Elements and helper functions](#elements)
 -   [Appendix](#appendix)
    -   [Specifying locations](#locations)
    -   [Internal USMT functions](#internalusmtfunctions)
    -   [Valid version tags](#allowed)
 ## <a href="" id="elements"></a>Elements and Helper Functions
 The following table describes the XML elements and helper functions you can use with USMT.
@ -37,7 +25,7 @@ The following table describes the XML elements and helper functions you can use
 |-----|----|-----|
 | [&lt;addObjects&gt;](#addobjects) <br/>[&lt;attributes&gt;](#attribute) <br/>[&lt;bytes&gt;](#bytes) <br/>[&lt;commandLine&gt;](#commandline) <br/>[&lt;component&gt;](#component) <br/>[&lt;condition&gt;](#condition) <br/>[&lt;conditions&gt;](#conditions) <br/>[&lt;content&gt;](#content) <br/>[&lt;contentModify&gt;](#contentmodify) <br/>[&lt;description&gt;](#description) <br/>[&lt;destinationCleanup&gt;](#destinationcleanup) <br/>[&lt;detect&gt;](#detect) <br/>[&lt;detects&gt;](#detects) <br/>[&lt;detection&gt;](#detection) <br/>[&lt;displayName&gt;](#displayname) <br/>[&lt;environment&gt;](#bkmk-environment) <br/>[&lt;exclude&gt;](#exclude) <br/>[&lt;excludeAttributes&gt;](#excludeattributes) <br/>[&lt;extensions&gt;](#extensions) <br/>[&lt;extension&gt;](#extension) <br/>[&lt;externalProcess&gt;](#externalprocess) <br/>[&lt;icon&gt;](#icon) <br/>[&lt;include&gt;](#include) <br/>[&lt;includeAttribute&gt;](#includeattributes) | [&lt;library&gt;](#library) <br/>[&lt;location&gt;](#location) <br/>[&lt;locationModify&gt;](#locationmodify) <br/>[&lt;_locDefinition&gt;](#locdefinition) <br/>[&lt;manufacturer&gt;](#manufacturer) <br/>[&lt;merge&gt;](#merge) <br/>[&lt;migration&gt;](#migration) <br/>[&lt;namedElements&gt;](#namedelements) <br/>[&lt;object&gt;](#object) <br/>[&lt;objectSet&gt;](#objectset) <br/>[&lt;path&gt;](#path) <br/>[&lt;paths&gt;](#paths) <br/>[&lt;pattern&gt;](#pattern) <br/>[&lt;processing&gt;](#processing) <br/>[&lt;plugin&gt;](#plugin) <br/>[&lt;role&gt;](#role) <br/>[&lt;rules&gt;](#rules) <br/>[&lt;script&gt;](#script) <br/>[&lt;text&gt;](#text) <br/>[&lt;unconditionalExclude&gt;](#unconditionalexclude) <br/>[&lt;variable&gt;](#variable) <br/>[&lt;version&gt;](#version) <br/>[&lt;windowsObjects&gt;](#windowsobjects) | [&lt;condition&gt; functions](#conditionfunctions) <br/>[&lt;content&gt; functions](#contentfunctions) <br/>[&lt;contentModify&gt; functions](#contentmodifyfunctions) <br/>[&lt;include&gt; and &lt;exclude&gt; filter functions](#persistfilterfunctions) <br/>[&lt;locationModify&gt; functions](#locationmodifyfunctions) <br/>[&lt;merge&gt; functions](#mergefunctions) <br/>[&lt;script&gt; functions](#scriptfunctions) <br/>[Internal USMT functions](#internalusmtfunctions) |
-## <a href="" id="addobjects"></a>&lt;addObjects&gt;
+## &lt;addObjects&gt;
 The &lt;addObjects&gt; element emulates the existence of one or more objects on the source computer. The child &lt;object&gt; elements provide the details of the emulated objects. If the content is a &lt;script&gt; element, the result of the invocation will be an array of objects.
@ -73,7 +61,7 @@ The following example is from the MigApp.xml file:
 </addObjects>
 ```
-## <a href="" id="attribute"></a>&lt;attributes&gt;
+## &lt;attributes&gt;
 The &lt;attributes&gt; element defines the attributes for a registry key or file.
@ -103,7 +91,7 @@ The following example is from the MigApp.xml file:
 </object> 
 ```
-## <a href="" id="bytes"></a>&lt;bytes&gt;
+## &lt;bytes&gt;
 You must specify the &lt;bytes&gt; element only for files because, if &lt;location&gt; corresponds to a registry key or a directory, then &lt;bytes&gt; will be ignored.
@ -135,8 +123,7 @@ The following example is from the MigApp.xml file:
 </object> 
 ```
-## <a href="" id="commandline"></a>&lt;commandLine&gt;
+## &lt;commandLine&gt;
 You might want to use the &lt;commandLine&gt; element if you want to start or stop a service or application before or after you run the ScanState and LoadState tools.
@ -156,7 +143,7 @@ Syntax:
 |--- |--- |--- |
 |*CommandLineString*|Yes|A valid command line.|
-## <a href="" id="component"></a>&lt;component&gt;
+## &lt;component&gt;
 The &lt;component&gt; element is required in a custom .xml file. This element defines the most basic construct of a migration .xml file. For example, in the MigApp.xml file, "Microsoft&reg; Office 2003" is a component that contains another component, "Microsoft Office Access&reg; 2003". You can use the child elements to define the component.
@ -187,7 +174,7 @@ hidden="Yes|No">
 For an example, see any of the default migration .xml files.
-## <a href="" id="condition"></a>&lt;condition&gt;
+## &lt;condition&gt;
 Although the &lt;condition&gt; element under the &lt;detect&gt;, &lt;objectSet&gt;, and &lt;addObjects&gt; elements is supported, we recommend that you do not use it. This element might be deprecated in future versions of USMT, requiring you to rewrite your scripts. We recommend that, if you need to use a condition within the &lt;objectSet&gt; and &lt;addObjects&gt; elements, you use the more powerful [&lt;conditions&gt;](#conditions) element, which allows you to formulate complex Boolean statements.
@ -238,15 +225,15 @@ However, in the code sample below, the &lt;condition&gt; elements, A and B, are
 </detection>
 ```
-### <a href="" id="conditionfunctions"></a>&lt;condition&gt; functions
+### &lt;condition&gt; functions
 The &lt;condition&gt; functions return a Boolean value. You can use these elements in &lt;addObjects&gt; conditions.
-   [Operating system version functions](#operatingsystemfunctions)
+- [Operating system version functions](#operating-system-version-functions)
-   [Object content functions](#objectcontentfunctions)
+- [Object content functions](#object-content-functions)
-### <a href="" id="operatingsystemfunctions"></a>Operating system version functions
+### Operating system version functions
 - **DoesOSMatch**
@ -297,8 +284,7 @@ The &lt;condition&gt; functions return a Boolean value. You can use these elemen
    |*OSType*|Yes|Can be **9x** or **NT**. If *OSType* does not match the type of the current operating system, then it returns FALSE. For example, if the current operating system is Windows NT-based and *OSType* is "9x" the result will be FALSE.|
    |*OSVersion*|Yes|The major version, minor version, build number, and corrected service diskette version separated by periods. For example, `5.0.2600.Service Pack 1`. You can also specify partial specification of the version but no pattern is allowed. For example, `5.0`. <br/><br/>The IsOSEarlierThan function returns TRUE if the current operating system is earlier than *OSVersion*.|
-
+### Object content functions
 ### <a href="" id="objectcontentfunctions"></a>Object content functions
 - **DoesObjectExist**
@ -436,7 +422,7 @@ The &lt;condition&gt; functions return a Boolean value. You can use these elemen
    |*ObjectType2*|Yes|Defines the type of the second object. Can be File or Registry.|
    |*EncodedLocation2*|Yes|The [encoded location](#locations) for the second object. You can specify environment variables.|
-## <a href="" id="conditions"></a>&lt;conditions&gt;
+## &lt;conditions&gt;
 The &lt;conditions&gt; element returns a Boolean result that is used to specify the conditions in which the parent element is evaluated. USMT evaluates the child elements, and then joins their results using the operators AND or OR according to the **operation** parameter.
@ -470,7 +456,7 @@ The following example is from the MigApp.xml file:
 </environment>
 ```
-## <a href="" id="content"></a>&lt;content&gt;
+## &lt;content&gt;
 You can use the &lt;content&gt; element to specify a list of object patterns to obtain an object set from the source computer. Each &lt;objectSet&gt; within a &lt;content&gt; element is evaluated. For each resulting object pattern list, the objects that match it are enumerated and their content is filtered by the filter parameter. The resulting string array is the output for the &lt;content&gt; element. The filter script returns an array of locations. The parent &lt;objectSet&gt; element can contain multiple child &lt;content&gt; elements.
@ -493,7 +479,7 @@ Syntax:
 |--- |--- |--- |
 |filter|Yes|A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example, `MyScripts.AScript ("Arg1","Arg2")`. <br/>The script is called for each object that is enumerated by the object sets in the &lt;include&gt; rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated.|
-### <a href="" id="contentfunctions"></a>&lt;content&gt; functions
+### &lt;content&gt; functions
 The following functions generate patterns out of the content of an object. These functions are called for every object that the parent &lt;ObjectSet&gt; element is enumerating.
@ -557,7 +543,7 @@ The following functions generate patterns out of the content of an object. These
  </objectSet>
  ```
-## <a href="" id="contentmodify"></a>&lt;contentModify&gt;
+## &lt;contentModify&gt;
 The &lt;contentModify&gt; element modifies the content of an object before it is written to the destination computer. For each &lt;contentModify&gt; element there can be multiple &lt;objectSet&gt; elements. This element returns the new content of the object that is being processed.
@ -580,7 +566,7 @@ Syntax:
 |--- |--- |--- |
 |script|Yes|A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example, `MyScripts.AScript ("Arg1","Arg2").` <br/><br/>The script will be called for each object that is enumerated by the object sets in the include rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated.|
-### <a href="" id="contentmodifyfunctions"></a>&lt;contentModify&gt; functions
+### &lt;contentModify&gt; functions
 The following functions change the content of objects as they are migrated. These functions are called for every object that the parent &lt;ObjectSet&gt; element is enumerating.
@ -675,7 +661,7 @@ The following functions change the content of objects as they are migrated. Thes
    | *Instruction* | Yes | Can one of the following: <ul><li>**Add.** Adds *String* to the resulting MULTI-SZ if it is not already there.</li><li>**Remove.** Removes *String* from the resulting MULTI-SZ.</li></ul> |
    | *String* | Yes | The string to be added or removed. |
-## <a href="" id="description"></a>&lt;description&gt;
+## &lt;description&gt;
 The &lt;description&gt; element defines a description for the component but does not affect the migration.
@ -701,15 +687,13 @@ The following code sample shows how the &lt;description&gt; element defines the
 <description>My custom component<description>
 ```
-## <a href="" id="destinationcleanup"></a>&lt;destinationCleanup&gt;
+## &lt;destinationCleanup&gt;
 The &lt;destinationCleanup&gt; element deletes objects, such as files and registry keys, from the destination computer before applying the objects from the source computer. This element is evaluated only when the LoadState tool is run on the destination computer. That is, this element is ignored by the ScanState tool.
 > [!IMPORTANT]
 > Use this option with extreme caution because it will delete objects from the destination computer.
 For each &lt;destinationCleanup&gt; element there can be multiple &lt;objectSet&gt; elements. A common use for this element is if there is a missing registry key on the source computer and you want to ensure that a component is migrated. In this case, you can delete all of the component's registry keys before migrating the source registry keys. This will ensure that if there is a missing key on the source computer, it will also be missing on the destination computer.
 - **Number of occurrences:** Unlimited
@ -740,7 +724,7 @@ For example:
 </destinationCleanup>
 ```
-## <a href="" id="detect"></a>&lt;detect&gt;
+## &lt;detect&gt;
 Although the &lt;detect&gt; element is still supported, we do not recommend using it because it may be deprecated in future versions of USMT. In that case, you would have to rewrite your scripts. Instead, we recommend that you use the [&lt;detection&gt;](#detection)**element.**
@ -770,7 +754,7 @@ Syntax:
 For examples, see the examples for [&lt;detection&gt;](#detection).
-## <a href="" id="detects"></a>&lt;detects&gt;
+## &lt;detects&gt;
 Although the &lt;detects&gt; element is still supported, we recommend that you do not use it because it may be deprecated in future versions of USMT, which would require you to rewrite your scripts. Instead, we recommend that you use the [&lt;detection&gt;](#detection) element if the parent element is &lt;role&gt; or &lt;namedElements&gt;, and we recommend that you use the &lt;conditions&gt; element if the parent element is &lt;rules&gt;. Using &lt;detection&gt; allows you to more clearly formulate complex Boolean statements.
@ -807,8 +791,7 @@ The following example is from the MigApp.xml file.
 </detects>
 ```
-## <a href="" id="detection"></a>&lt;detection&gt;
+## &lt;detection&gt;
 The &lt;detection&gt; element is a container for one &lt;conditions&gt; element. The result of the child &lt;condition&gt; elements, located underneath the &lt;conditions&gt; element, determines the result of this element. For example, if all of the child &lt;conditions&gt; elements within the &lt;detection&gt; element resolve to TRUE, then the &lt;detection&gt; element resolves to TRUE. If any of the child &lt;conditions&gt; elements resolve to FALSE, then the &lt;detection&gt; element resolves to FALSE.
@ -857,8 +840,7 @@ and
   </detection>
 ```
-## <a href="" id="displayname"></a>&lt;displayName&gt;
+## &lt;displayName&gt;
 The &lt;displayName&gt; element is a required field within each &lt;component&gt; element.
@ -885,9 +867,9 @@ For example:
 <displayName>Command Prompt settings</displayName>
 ```
-## <a href="" id="bkmk-environment"></a>&lt;environment&gt;
+## &lt;environment&gt;
-The &lt;environment&gt; element is a container for &lt;variable&gt; elements in which you can define variables to use in your .xml file. All environment variables defined this way will be private. That is, they will be available only for their child components and the component in which they were defined. For two example scenarios, see [Examples](#envex).
+The &lt;environment&gt; element is a container for &lt;variable&gt; elements in which you can define variables to use in your .xml file. All environment variables defined this way will be private. That is, they will be available only for their child components and the component in which they were defined. For two example scenarios, see [Examples](#examples).
 - **Number of occurrences:** unlimited
@ -909,7 +891,7 @@ Syntax:
 | name | Yes, when &lt;environment&gt; is a child of &lt;namedElements&gt; <br/>No, when &lt;environment&gt; is a child of &lt;role&gt; or &lt;component&gt; | When declared as a child of the &lt;role&gt; or &lt;component&gt; elements, if *ID* is declared, USMT ignores the content of the &lt;environment&gt; element and the content of the &lt;environment&gt; element with the same name declared in the &lt;namedElements&gt; element is processed. |
 | context | No <br/>(default = UserAndSystem) | Defines the scope of this parameter: whether to process this component in the context of the specific user, across the entire operating system, or both. <br/>The largest possible scope is set by the &lt;component&gt; element. For example, if a &lt;component&gt; element has a context of User and a &lt;rules&gt; element had a context of UserAndSystem, then the &lt;rules&gt; element would act as though it had a context of User. If the &lt;rules&gt; element had a context of System, it would act as though &lt;rules&gt; were not there. <ul><li>**User.** Evaluates the variables for each user.</li><li>**System.** Evaluates the variables only once for the system.</li><li>**UserAndSystem.** Evaluates the variables for the entire operating system and each user.</li></ul> |
-## <a href="" id="envex"></a>
+## Examples
 ### Example scenario 1
@ -989,8 +971,7 @@ Then, you can specify the variable in an &lt;include&gt; rule as follows:
 </include>
 ```
-## <a href="" id="exclude"></a>&lt;exclude&gt;
+## &lt;exclude&gt;
 The &lt;exclude&gt; element determines what objects will not be migrated, unless there is a more specific &lt;include&gt; element that migrates an object. If there is an &lt;include&gt; and &lt;exclude&gt; element for the same object, the object will be included. For each &lt;exclude&gt; element there can be multiple child &lt;objectSet&gt; elements.
@ -1013,7 +994,6 @@ Syntax:
 |--- |--- |--- |
 |filter|No <br/>(default = No)|A script followed by any number of string arguments that are separated by a comma and enclosed in parenthesis. For example, `MyScripts.AScript ("Arg1","Arg2")`. <br/><br/>The script will be called for each object that is enumerated by the object sets in the include rule. The filter script returns a Boolean value. If the return value is TRUE, the object will be migrated. If it is FALSE, it will not be migrated.|
 For example, from the MigUser.xml file:
 ```xml
@ -1026,8 +1006,7 @@ For example, from the MigUser.xml file:
 </exclude>
 ```
-## <a href="" id="excludeattributes"></a>&lt;excludeAttributes&gt;
+## &lt;excludeAttributes&gt;
 You can use the &lt;excludeAttributes&gt; element to determine which parameters associated with an object will not be migrated. If there are conflicts between the &lt;includeAttributes&gt; and &lt;excludeAttributes&gt; elements, the most specific pattern determines the patterns that will not be migrated. If an object does not have an &lt;includeAttributes&gt; or &lt;excludeAttributes&gt; element, then all of its parameters will be migrated.
@ -1099,8 +1078,7 @@ Example:
 </migration>
 ```
-## <a href="" id="extensions"></a>&lt;extensions&gt;
+## &lt;extensions&gt;
 The &lt;extensions&gt; element is a container for one or more &lt;extension&gt; elements.
@ -1117,8 +1095,7 @@ Syntax:
 </extensions>
 ```
-## <a href="" id="extension"></a>&lt;extension&gt;
+## &lt;extension&gt;
 You can use the &lt;extension&gt; element to specify documents of a specific extension.
@ -1158,8 +1135,7 @@ is the same as specifying the following code below the &lt;rules&gt; element:
 For another example of how to use the &lt;extension&gt; element, see the example for [&lt;excludeAttributes&gt;](#excludeattributes).
-## <a href="" id="externalprocess"></a>&lt;externalProcess&gt;
+## &lt;externalProcess&gt;
 You can use the &lt;externalProcess&gt; element to run a command line during the migration process. For example, you may want to run a command after the LoadState process completes.
@ -1182,11 +1158,11 @@ Syntax:
 For an example of how to use the &lt;externalProcess&gt; element, see the example for [&lt;excludeAttributes&gt;](#excludeattributes).
-## <a href="" id="icon"></a>&lt;icon&gt;
+## &lt;icon&gt;
 This is an internal USMT element. Do not use this element.
-## <a href="" id="include"></a>&lt;include&gt;
+## &lt;include&gt;
 The &lt;include&gt; element determines what to migrate, unless there is a more specific [&lt;exclude&gt;](#exclude) rule. You can specify a script to be more specific to extend the definition of what you want to collect. For each &lt;include&gt; element there can be multiple &lt;objectSet&gt; elements.
@ -1239,7 +1215,7 @@ The following example is from the MigUser.xml file:
    </component>
 ```
-### <a href="" id="persistfilterfunctions"></a>&lt;include&gt; and &lt;exclude&gt; filter functions
+### &lt;include&gt; and &lt;exclude&gt; filter functions
 The following functions return a Boolean value. You can use them to migrate certain objects based on when certain conditions are met.
@ -1290,8 +1266,7 @@ The following functions return a Boolean value. You can use them to migrate cert
    </include>
    ```
-## <a href="" id="includeattributes"></a>&lt;includeAttributes&gt;
+## &lt;includeAttributes&gt;
 You can use the &lt;includeAttributes&gt; element to determine whether certain parameters associated with an object will be migrated along with the object itself. If there are conflicts between the &lt;includeAttributes&gt; and &lt;excludeAttributes&gt; elements, the most specific pattern will determine which parameters will be migrated. If an object does not have an &lt;includeAttributes&gt; or &lt;excludeAttributes&gt; element, then all of its parameters will be migrated.
@ -1314,11 +1289,11 @@ Syntax:
 For an example of how to use the &lt;includeAttributes&gt; element, see the example for [&lt;excludeAttributes&gt;](#excludeattributes).
-## <a href="" id="library"></a>&lt;library&gt;
+## &lt;library&gt;
 This is an internal USMT element. Do not use this element.
-## <a href="" id="location"></a>&lt;location&gt;
+## &lt;location&gt;
 The &lt;location&gt; element defines the location of the &lt;object&gt; element.
@ -1356,7 +1331,7 @@ The following example is from the MigApp.xml file:
 </addObjects>
 ```
-## <a href="" id="locationmodify"></a>&lt;locationModify&gt;
+## &lt;locationModify&gt;
 You can use the &lt;locationModify&gt; element to change the location and name of an object before it is migrated to the destination computer. The &lt;locationModify&gt; element is processed only when the LoadState tool is run on the destination computer. In other words, this element is ignored by the ScanState tool. The &lt;locationModify&gt; element will create the appropriate folder on the destination computer if it does not already exist.
@ -1389,7 +1364,7 @@ The following example is from the MigApp.xml file:
 </locationModify>
 ```
-### <a href="" id="locationmodifyfunctions"></a>&lt;locationModify&gt; functions
+### &lt;locationModify&gt; functions
 The following functions change the location of objects as they are migrated when using the &lt;locationModify&gt; element. These functions are called for every object that the parent &lt;ObjectSet&gt; element is enumerating. The &lt;locationModify&gt; element will create the appropriate folder on the destination computer if it does not already exist.
@ -1449,13 +1424,11 @@ For example:
 </locationModify>
 ```
-## <a href="" id="locdefinition"></a>&lt;\_locDefinition&gt;
+## &lt;\_locDefinition&gt;
 This is an internal USMT element. Do not use this element.
-## <a href="" id="manufacturer"></a>&lt;manufacturer&gt;
+## &lt;manufacturer&gt;
 The &lt;manufacturer&gt; element defines the manufacturer for the component, but does not affect the migration.
@ -1475,7 +1448,7 @@ Syntax:
 |--- |--- |--- |
 |*Name*|Yes|The name of the manufacturer for the component.|
-## <a href="" id="merge"></a>&lt;merge&gt;
+## &lt;merge&gt;
 The &lt;merge&gt; element determines what will happen when a collision occurs. A collision is when an object that is migrated is already present on the destination computer. If you do not specify this element, the default behavior for the registry is for the source object to overwrite the destination object. The default behavior for files is for the source file to be renamed to "OriginalFileName(1).OriginalExtension". This element specifies only what should be done when a collision occurs. It does not include objects. Therefore, for your objects to migrate, you must specify &lt;include&gt; rules along with the &lt;merge&gt; element. When an object is processed and a collision is detected, USMT will select the most specific merge rule and apply it to resolve the conflict. For example, if you have a &lt;merge&gt; rule C:\\\* \[\*\] set to &lt;sourcePriority&gt; and a &lt;merge&gt; rule C:\\subfolder\\\* \[\*\] set to &lt;destinationPriority&gt;, then USMT would use the &lt;destinationPriority&gt; rule because it is the more specific.
@ -1517,7 +1490,7 @@ The following example is from the MigUser.xml file:
 </rules>
 ```
-### <a href="" id="mergefunctions"></a>&lt;merge&gt; functions
+### &lt;merge&gt; functions
 These functions control how collisions are resolved.
@ -1581,7 +1554,7 @@ These functions control how collisions are resolved.
    </merge>
    ```
-## <a href="" id="migration"></a>&lt;migration&gt;
+## &lt;migration&gt;
 The &lt;migration&gt; element is the single root element of a migration .xml file and is required. Each .xml file must have a unique migration urlid. The urlid of each file that you specify on the command line must be unique. This is because USMT uses the urlid to define the components within the file. For example, you must specify the following at the beginning of each file: &lt;CustomFileName&gt; is the name of the file; for example, "CustomApp".
@ -1638,7 +1611,7 @@ This filter helper function can be used to filter the migration of files based o
 </component>
 ```
-## <a href="" id="namedelements"></a>&lt;namedElements&gt;
+## &lt;namedElements&gt;
 You can use the **&lt;namedElements&gt;** element to define named elements. You can use these elements in any component throughout your .xml file. For an example of how to use this element, see the MigApp.xml file.
@ -1657,7 +1630,7 @@ Syntax:
 For an example of this element, see the MigApp.xml file.
-## <a href="" id="object"></a>&lt;object&gt;
+## &lt;object&gt;
 The &lt;object&gt; element represents a file or registry key.
@ -1693,8 +1666,7 @@ The following example is from the MigApp.xml file:
 </addObjects>
 ```
-## <a href="" id="objectset"></a>&lt;objectSet&gt;
+## &lt;objectSet&gt;
 The &lt;objectSet&gt; element contains a list of object patterns ; for example, file paths, registry locations, and so on. Any child &lt;conditions&gt; elements will be evaluated first. If all child &lt;conditions&gt; elements return FALSE, the &lt;objectSet&gt; element will evaluate to an empty set. For each parent element, there can be only multiple &lt;objectSet&gt; elements.
@ -1743,19 +1715,16 @@ The following example is from the MigUser.xml file:
 </component>
 ```
-## <a href="" id="path"></a>&lt;path&gt;
+## &lt;path&gt;
 This is an internal USMT element. Do not use this element.
-## <a href="" id="paths"></a>&lt;paths&gt;
+## &lt;paths&gt;
 This is an internal USMT element. Do not use this element.
 ## &lt;pattern&gt;
 You can use this element to specify multiple objects. You can specify multiple &lt;pattern&gt; elements for each &lt;objectSet&gt; element and they will be combined. If you are specifying files, you may want to use GenerateDrivePatterns with &lt;script&gt; instead. GenerateDrivePatterns is basically the same as a &lt;pattern&gt; rule, without the drive letter specification. For example, the following two lines of code are similar:
 ```xml
@ -1812,7 +1781,7 @@ For example:
 - For more examples of how to use this element, see [Exclude Files and Settings](usmt-exclude-files-and-settings.md), [Reroute Files and Settings](usmt-reroute-files-and-settings.md), [Include Files and Settings](usmt-include-files-and-settings.md), and [Custom XML Examples](usmt-custom-xml-examples.md).
-## <a href="" id="processing"></a>&lt;processing&gt;
+## &lt;processing&gt;
 You can use this element to run a script during a specific point within the migration process. Return values are not expected from the scripts that you specify, and if there are return values, they will be ignored.
@ -1833,11 +1802,11 @@ Syntax:
 |--- |--- |--- |
 | when | Yes | Indicates when the script should be run. This value can be one of the following: <ul><li>**pre-scan** means before the scanning process begins.</li><li>**scan-success** means after the scanning process has finished successfully.</li><li>**post-scan** means after the scanning process has finished, whether it was successful or not.</li><li>**pre-apply** means before the apply process begins.</li><li>**apply-success** means after the apply process has finished successfully.</li><li>**post-apply** means after the apply process has finished, whether it was successful or not.</li></ul> |
-## <a href="" id="plugin"></a>&lt;plugin&gt;
+## &lt;plugin&gt;
 This is an internal USMT element. Do not use this element.
-## <a href="" id="role"></a>&lt;role&gt;
+## &lt;role&gt;
 The &lt;role&gt; element is required in a custom .xml file. By specifying the &lt;role&gt; element, you can create a concrete component. The component will be defined by the parameters specified at the &lt;component&gt; level, and with the role that you specify here.
@ -1891,8 +1860,7 @@ The following example is from the MigUser.xml file. For more examples, see the M
 </component>
 ```
-## <a href="" id="rules"></a>&lt;rules&gt;
+## &lt;rules&gt;
 The &lt;rules&gt; element is required in a custom .xml file. This element contains rules that will run during the migration if the parent &lt;component&gt; element is selected, unless the child &lt;conditions&gt; element, if present, evaluates to FALSE. For each &lt;rules&gt; element there can be multiple child &lt;rules&gt; elements.
@ -1946,8 +1914,7 @@ The following example is from the MigUser.xml file:
 </component>
 ```
-## <a href="" id="script"></a>&lt;script&gt;
+## &lt;script&gt;
 The return value that is required by &lt;script&gt; depends on the parent element.
@ -1999,7 +1966,7 @@ To migrate the Sample.doc file from any drive on the source computer, use &lt;sc
 For more examples of how to use this element, see [Exclude Files and Settings](usmt-exclude-files-and-settings.md), [Reroute Files and Settings](usmt-reroute-files-and-settings.md), and [Custom XML Examples](usmt-custom-xml-examples.md).
-### <a href="" id="scriptfunctions"></a>&lt;script&gt; functions
+### &lt;script&gt; functions
 You can use the following functions with the &lt;script&gt; element
@ -2007,7 +1974,7 @@ You can use the following functions with the &lt;script&gt; element
 - [Simple executing scripts](#simple)
-### <a href="" id="stringgeneratingfunctions"></a>String and pattern generating functions
+### String and pattern generating functions
 These functions return either a string or a pattern.
@ -2126,7 +2093,7 @@ This helper function invokes the document finder to scan the system for all file
  </component>
 ```
-### <a href="" id="simple"></a>Simple executing scripts
+### Simple executing scripts
 The following scripts have no return value. You can use the following errors with &lt;script&gt; elements that are within &lt;processing&gt; elements
@ -2172,8 +2139,7 @@ The following scripts have no return value. You can use the following errors wit
 - **SyncSCM(ServiceShortName).** Reads the Start type value from the registry (HKLM\\System\\CurrentControlSet\\Services\\ServiceShortName \[Start\]) after it is changed by the migration engine, and then synchronizes Service Control Manager (SCM) with the new value.
-## <a href="" id="text"></a>&lt;text&gt;
+## &lt;text&gt;
 You can use the &lt;text&gt; element to set a value for any environment variables that are inside one of the migration .xml files.
@ -2201,8 +2167,7 @@ For example:
 </variable>
 ```
-## <a href="" id="unconditionalexclude"></a>&lt;unconditionalExclude&gt;
+## &lt;unconditionalExclude&gt;
 The &lt;unconditionalExclude&gt; element excludes the specified files and registry values from the migration, regardless of the other include rules in any of the migration .xml files or in the Config.xml file. The objects declared here will not be migrated because this element takes precedence over all other rules. For example, even if there are explicit &lt;include&gt; rules to include .mp3 files, if you specify to exclude them with this option, then they will not be migrated.
@ -2239,8 +2204,7 @@ The following .xml file excludes all .mp3 files from migration. For additional e
 </migration>
 ```
-## <a href="" id="variable"></a>&lt;variable&gt;
+## &lt;variable&gt;
 The &lt;variable&gt; element is required in an &lt;environment&gt; element. For each &lt;variable&gt; element there must be one &lt;objectSet&gt;, &lt;script&gt;, or &lt;text&gt; element. The content of the &lt;variable&gt; element assigns a text value to the environment variable. This element has the following three options:
@ -2281,8 +2245,7 @@ The following example is from the MigApp.xml file:
 </environment>
 ```
-## <a href="" id="version"></a>&lt;version&gt;
+## &lt;version&gt;
 The &lt;version&gt; element defines the version for the component, but does not affect the migration.
@ -2308,13 +2271,13 @@ For example:
 <version>4.*</version>
 ```
-## <a href="" id="windowsobjects"></a>&lt;windowsObjects&gt;
+## &lt;windowsObjects&gt;
 The &lt;windowsObjects&gt; element is for USMT internal use only. Do not use this element.
 ## Appendix
-### <a href="" id="locations"></a>Specifying locations
+### Specifying locations
 - **Specifying encoded locations**. The encoded location used in all of the helper functions is an unambiguous string representation for the name of an object. It is composed of the node part, optionally followed by the leaf enclosed in square brackets. This makes a clear distinction between nodes and leaves.
@ -2326,7 +2289,7 @@ The &lt;windowsObjects&gt; element is for USMT internal use only. Do not use thi
    For example, the pattern `c:\Windows\*` will match the Windows directory and all subdirectories. But it will not match any of the files in those directories. To match the files as well, you must specify `c:\Windows\*[*]`.
-### <a href="" id="internalusmtfunctions"></a>Internal USMT functions
+### Internal USMT functions
 The following functions are for internal USMT use only. Do not use them in an .xml file.
@ -2356,7 +2319,7 @@ The following functions are for internal USMT use only. Do not use them in an .x
 - SetPstPathInMapiStruc
-### <a href="" id="allowed"></a>Valid version tags
+### Valid version tags
 You can use the following version tags with various helper functions:
@ -2382,6 +2345,6 @@ The following version tags contain values that can be compared:
 - "ProductVersion"
-## Related topics
+## Related articles
-[USMT XML Reference](usmt-xml-reference.md)
+[USMT XML reference](usmt-xml-reference.md)