deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Applied valid types to code blocks

Browse Source
This commit is contained in:
Gary Moore 2021-12-01 21:42:23 -08:00
parent d13b41eedc
commit 076f6df683
2 changed files with 13 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/usmt/understanding-migration-xml-files.md
View File

@ -186,7 +186,7 @@ You can use multiple XML files with the ScanState and LoadState tools. Each of t
For example, you can use all of the XML migration file types for a single migration, as in the following example: For example, you can use all of the XML migration file types for a single migration, as in the following example:
```cmd ```console
Scanstate <store> /config:c:\myFolder\config.xml /i:migapps.xml /i:migdocs.xml /i:customrules.xml Scanstate <store> /config:c:\myFolder\config.xml /i:migapps.xml /i:migdocs.xml /i:customrules.xml
``` ```
@ -214,14 +214,14 @@ To generate the XML migration rules file for a source computer:
3. At the command prompt, type: 3. At the command prompt, type:
```cmd ```console
cd /d <USMTpath> cd /d <USMTpath>
scanstate.exe /genmigxml: <filepath.xml> scanstate.exe /genmigxml: <filepath.xml>
``` ```
Where *&lt;USMTpath&gt;* is the location on your source computer where you have saved the USMT files and tools, and *&lt;filepath.xml&gt;* is the full path to a file where you can save the report. For example, type: Where *&lt;USMTpath&gt;* is the location on your source computer where you have saved the USMT files and tools, and *&lt;filepath.xml&gt;* is the full path to a file where you can save the report. For example, type:
```cmd ```console
cd /d c:\USMT cd /d c:\USMT
scanstate.exe /genmigxml:"C:\Documents and Settings\USMT Tester\Desktop\genMig.xml" scanstate.exe /genmigxml:"C:\Documents and Settings\USMT Tester\Desktop\genMig.xml"
``` ```
@ -250,7 +250,7 @@ The MigDocs.xml file calls the **GenerateDocPatterns** function, which takes thr
**Usage:** **Usage:**
```cmd ```console
MigXmlHelper.GenerateDocPatterns ("<ScanProgramFiles>", "<IncludePatterns>", "<SystemDrive>") MigXmlHelper.GenerateDocPatterns ("<ScanProgramFiles>", "<IncludePatterns>", "<SystemDrive>")
``` ```

26
windows/deployment/usmt/usmt-log-files.md
View File

@ -107,7 +107,7 @@ The following examples describe common scenarios in which you can use the diagno
Let's imagine that we have the following directory structure and that we want the "data" directory to be included in the migration along with the "New Text Document.txt" file in the "New Folder." The directory of **C:\\data** contains: Let's imagine that we have the following directory structure and that we want the "data" directory to be included in the migration along with the "New Text Document.txt" file in the "New Folder." The directory of **C:\\data** contains:
``` ```console
01/21/2009 10:08 PM <DIR> . 01/21/2009 10:08 PM <DIR> .
01/21/2009 10:08 PM <DIR> .. 01/21/2009 10:08 PM <DIR> ..
01/21/2009 10:08 PM <DIR> New Folder 01/21/2009 10:08 PM <DIR> New Folder
@ -118,7 +118,7 @@ Let's imagine that we have the following directory structure and that we want th
The directory of **C:\\data\\New Folder** contains: The directory of **C:\\data\\New Folder** contains:
``` ```console
01/21/2009 10:08 PM <DIR> . 01/21/2009 10:08 PM <DIR> .
01/21/2009 10:08 PM <DIR> .. 01/21/2009 10:08 PM <DIR> ..
01/21/2009 10:08 PM 0 New Text Document.txt 01/21/2009 10:08 PM 0 New Text Document.txt
@ -149,7 +149,7 @@ To migrate these files you author the following migration XML:
However, upon testing the migration you notice that the "New Text Document.txt" file isn't included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable MIG\_ENABLE\_DIAG set such that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered: However, upon testing the migration you notice that the "New Text Document.txt" file isn't included in the migration. To troubleshoot this failure, the migration can be repeated with the environment variable MIG\_ENABLE\_DIAG set such that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered:
``` xml ```xml
<MigUnitList> <MigUnitList>
<MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true"> <MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true">
<Patterns Type="Include"> <Patterns Type="Include">
@ -170,13 +170,13 @@ Analysis of this XML section reveals the migunit that was created when the migra
An analysis of the XML elements reference topic reveals that the &lt;pattern&gt; tag needs to be modified as follows: An analysis of the XML elements reference topic reveals that the &lt;pattern&gt; tag needs to be modified as follows:
``` xml ```xml
<pattern type="File">c:\data\* [*]</pattern> <pattern type="File">c:\data\* [*]</pattern>
``` ```
When the migration is preformed again with the modified tag, the diagnostic log reveals the following: When the migration is preformed again with the modified tag, the diagnostic log reveals the following:
``` xml ```xml
<MigUnitList> <MigUnitList>
<MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true"> <MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true">
<Patterns Type="Include"> <Patterns Type="Include">
@ -201,7 +201,7 @@ This diagnostic log confirms that the modified &lt;pattern&gt; value enables the
In this scenario, you have the following directory structure and you want all files in the "data" directory to migrate, except for text files. The **C:\\Data** folder contains: In this scenario, you have the following directory structure and you want all files in the "data" directory to migrate, except for text files. The **C:\\Data** folder contains:
``` ```console
Directory of C:\Data Directory of C:\Data
01/21/2009 10:08 PM <DIR> . 01/21/2009 10:08 PM <DIR> .
@ -214,7 +214,7 @@ Directory of C:\Data
The **C:\\Data\\New Folder\\** contains: The **C:\\Data\\New Folder\\** contains:
``` ```console
01/21/2009 10:08 PM <DIR> . 01/21/2009 10:08 PM <DIR> .
01/21/2009 10:08 PM <DIR> .. 01/21/2009 10:08 PM <DIR> ..
01/21/2009 10:08 PM 0 New Text Document.txt 01/21/2009 10:08 PM 0 New Text Document.txt
@ -251,7 +251,7 @@ You author the following migration XML:
However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable MIG\_ENABLE\_DIAG set so that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered: However, upon testing the migration you notice that all the text files are still included in the migration. In order to troubleshoot this issue, the migration can be performed with the environment variable MIG\_ENABLE\_DIAG set so that the diagnostic log is generated. Upon searching the diagnostic log for the component "DATA1", the following XML section is discovered:
``` xml ```xml
<MigUnitList> <MigUnitList>
<MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true"> <MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true">
<Patterns Type="Include"> <Patterns Type="Include">
@ -308,7 +308,7 @@ Upon reviewing the diagnostic log, you confirm that the files are still migratin
Your revised migration XML script excludes the files from migrating, as confirmed in the diagnostic log: Your revised migration XML script excludes the files from migrating, as confirmed in the diagnostic log:
``` xml ```xml
<MigUnitList> <MigUnitList>
<MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true"> <MigUnit Name="&lt;System&gt;\DATA1 (CMXEAgent)" Context="System" ConfidenceLevel="100" Group="Applications" Role="UserData" Agent="CMXEAgent" Selected="true" Supported="true">
<Patterns Type="Include"> <Patterns Type="Include">
@ -338,11 +338,3 @@ Your revised migration XML script excludes the files from migrating, as confirme
[LoadState Syntax](usmt-loadstate-syntax.md) [LoadState Syntax](usmt-loadstate-syntax.md)