From f783aa8982a5f89153669b8221ce39e09386dd21 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Wed, 6 Dec 2023 16:16:20 -0500 Subject: [PATCH] Freshness 04-12-2023 9 --- .../deployment/usmt/usmt-configxml-file.md | 27 ++++++++++--------- 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/windows/deployment/usmt/usmt-configxml-file.md b/windows/deployment/usmt/usmt-configxml-file.md index 22bde617dc..bf2cec70b9 100644 --- a/windows/deployment/usmt/usmt-configxml-file.md +++ b/windows/deployment/usmt/usmt-configxml-file.md @@ -21,7 +21,8 @@ The `Config.xml` file has a different format than the other migration **.xml** f For more information about using the `Config.xml` file with other migration files, such as the `MigDocs.xml` and `MigApps.xml` files, see [Understanding Migration XML Files](understanding-migration-xml-files.md). > [!NOTE] -> To exclude a component from the `Config.xml` file, set the **migrate** value to **no**. Deleting the XML tag for the component from the `Config.xml` file will not exclude the component from your migration. +> +> To exclude a component from the `Config.xml` file, set the **migrate** value to **no**. Deleting the XML tag for the component from the `Config.xml` file doesn't exclude the component from your migration. ## Migration Policies @@ -61,7 +62,7 @@ Additionally, the order in the **<ErrorControl>** section implies priority * [*] - C:\Users\* [*] + C:\Users\* [*] HKCU\SOFTWARE\Microsoft\* [*] @@ -70,6 +71,7 @@ Additionally, the order in the **<ErrorControl>** section implies priority ``` > [!IMPORTANT] +> > The configurable **<ErrorControl>** rules support only the environment variables for the operating system that is running and the currently logged-on user. As a workaround, you can specify a path using the (\*) wildcard character. ### <fatal> @@ -85,12 +87,12 @@ The **<fatal>** element isn't required. Syntax: ```xml - + ``` |Parameter|Required|Value| |--- |--- |--- | -|errorCode|No|*Specify system error message here*| +|errorCode|No|"any" or "*specify system error message here*"| You use the **<fatal>** element to specify that errors matching a specific pattern should cause USMT to halt the migration. @@ -125,12 +127,12 @@ The **<nonFatal>** element isn't required. Syntax: ```xml - + ``` |Parameter|Required|Value| |--- |--- |--- | -|**<errorCode>**|No|*Specify system error message here*. If system error messages aren't specified, the default behavior applies the parameter to all system error messages.| +|**<errorCode>**|No|"any" or "*specify system error message*". If system error messages aren't specified, the default behavior applies the parameter to all system error messages.| You use the **<nonFatal>** element to specify that errors matching a specific pattern shouldn't cause USMT to halt the migration. @@ -147,12 +149,12 @@ The **<registryError>** element isn't required. Syntax: ```xml - + ``` |Parameter|Required|Value| |--- |--- |--- | -|**<errorCode>**|No|*Specify system error message here*. If system error messages aren't specified, the default behavior applies the parameter to all system error messages.| +|**<errorCode>**|No|"any" or "*specify system error message here*". If system error messages aren't specified, the default behavior applies the parameter to all system error messages.| You use the **<registryError>** element to specify that errors matching a specific pattern shouldn't cause USMT to halt the migration. @@ -181,6 +183,7 @@ Syntax: The following **<HardLinkStoreControl>** sample code specifies that hard links can be created to locked files only if the locked file resides somewhere under C:\\Users\\. Otherwise, a file-access error occurs when a locked file is encountered that can't be copied, even though is technically possible for the link to be created. > [!IMPORTANT] +> > The **<ErrorControl>** section can be configured to conditionally ignore file access errors, based on the file's location. ```xml @@ -214,7 +217,7 @@ The **<createHardLink>** element defines a standard MigXML pattern that de Syntax: ```xml - + ``` ### <errorHardLink> @@ -224,7 +227,7 @@ The **<errorHardLink>** element defines a standard MigXML pattern that des Syntax: ```xml - + ``` ### <ProfileControl> @@ -234,7 +237,7 @@ This element is used to contain other elements that establish rules for migratin Syntax: ```xml -` ` + ``` ### <localGroups> @@ -457,7 +460,7 @@ The following sample `Config.xml` file contains detailed examples about items yo * [*] - C:\Users\* [*] + C:\Users\* [*] * [*]