deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 03:43:39 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

CI Update

Browse Source
This commit is contained in:
VSC-Service-Account
2019-06-04 22:13:57 +00:00
parent 13bd3bfe64
commit 858476cf2f
1820 changed files with 28427 additions and 28190 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
windows/deployment/usmt/usmt-configxml-file.md
View File

@ -30,7 +30,7 @@ For more information about using the Config.xml file with other migration files,
**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.
 
## In This Topic
@ -110,7 +110,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.
 
### <a href="" id="bkmk-fatal"></a>&lt;fatal&gt;
@ -146,7 +146,7 @@ Syntax: `<fatal errorCode="any">`*&lt;pattern&gt;*`</fatal>`
</tbody>
</table>
 
You use the **&lt;fatal&gt;** element to specify that errors matching a specific pattern should cause USMT to halt the migration.
@ -200,14 +200,14 @@ Syntax: `<nonfatal errorCode="any">`*&lt;pattern&gt;*`</nonFatal>`
</tbody>
</table>
 
You use the **&lt;nonFatal&gt;** element to specify that errors matching a specific pattern should not cause USMT to halt the migration.
## <a href="" id="bkmk-registryerror"></a>&lt;registryError&gt;
The **&lt;registryError&gt;**element is not required.
The <strong>&lt;registryError&gt;</strong>element is not required.
- **Number of occurrences**: Once for each component
@ -239,7 +239,7 @@ Syntax: `<registryError></registryError>`
</tbody>
</table>
 
You use the **&lt;registryError&gt;** element to specify that errors matching a specific pattern should not cause USMT to halt the migration.
@ -263,7 +263,7 @@ The **&lt;HardLinkStoreControl&gt;** sample code below specifies that hard links
**Important**  
The **&lt;ErrorControl&gt;** section can be configured to conditionally ignore file access errors, based on the file’s location.
 
``` syntax
<Policy>
@ -358,7 +358,7 @@ This element describes the source and destination groups for a local group membe
</tbody>
</table>
 
The valid and required children of **&lt;changeGroup&gt;** are **&lt;include&gt;** and **&lt;exclude&gt;**. Although both can be children at the same time, only one is required.
@ -579,9 +579,9 @@ Refer to the following sample Config.xml file for additional details about items
[USMT XML Reference](usmt-xml-reference.md)