Applied correct style to alerts

This commit is contained in:
Gary Moore 2021-12-01 21:45:05 -08:00
parent 076f6df683
commit 65decbe44c
2 changed files with 6 additions and 6 deletions

View File

@ -101,8 +101,8 @@ Additionally, the order in the **<ErrorControl>** section implies priority
</ErrorControl> </ErrorControl>
``` ```
**Important**   > [!IMPORTANT]
The configurable **&lt;ErrorControl&gt;** 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. > The configurable **&lt;ErrorControl&gt;** 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; ### <a href="" id="bkmk-fatal"></a>&lt;fatal&gt;
@ -188,8 +188,8 @@ Syntax: `<HardLinkStoreControl></HardLinkStoreControl>`
The **&lt;HardLinkStoreControl&gt;** sample code below 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 cannot be copied, even though is technically possible for the link to be created. The **&lt;HardLinkStoreControl&gt;** sample code below 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 cannot be copied, even though is technically possible for the link to be created.
**Important**   > [!IMPORTANT]
The **&lt;ErrorControl&gt;** section can be configured to conditionally ignore file access errors, based on the files location. > The **&lt;ErrorControl&gt;** section can be configured to conditionally ignore file access errors, based on the files location.
``` xml ``` xml
<Policy> <Policy>

View File

@ -40,8 +40,8 @@ The following table describes each command-line option related to logs, and it p
|**/listfiles** *[Path]FileName*|Specifies the path and file name of the Listfiles log.|Provides a list of the files that were migrated.| |**/listfiles** *[Path]FileName*|Specifies the path and file name of the Listfiles log.|Provides a list of the files that were migrated.|
|Set the environment variable MIG_ENABLE_DIAG to a path to an XML file.|USMTDiag.xml|The diagnostic log contains detailed system environment information, user environment information, and information about the migration units (migunits) being gathered and their contents.| |Set the environment variable MIG_ENABLE_DIAG to a path to an XML file.|USMTDiag.xml|The diagnostic log contains detailed system environment information, user environment information, and information about the migration units (migunits) being gathered and their contents.|
**Note**   > [!NOTE]
You cannot store any of the log files in *StorePath*. If you do, the log will be overwritten when USMT is run. > You cannot store any of the log files in *StorePath*. If you do, the log will be overwritten when USMT is run.
## <a href="" id="bkmk-scanloadstatelogs"></a>ScanState and LoadState Logs ## <a href="" id="bkmk-scanloadstatelogs"></a>ScanState and LoadState Logs