mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Applied correct style to alerts
This commit is contained in:
parent
076f6df683
commit
65decbe44c
@ -101,8 +101,8 @@ Additionally, the order in the **<ErrorControl>** section implies priority
|
|||||||
</ErrorControl>
|
</ErrorControl>
|
||||||
```
|
```
|
||||||
|
|
||||||
**Important**
|
> [!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.
|
> 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><fatal>
|
### <a href="" id="bkmk-fatal"></a><fatal>
|
||||||
|
|
||||||
@ -188,8 +188,8 @@ Syntax: `<HardLinkStoreControl></HardLinkStoreControl>`
|
|||||||
|
|
||||||
The **<HardLinkStoreControl>** 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 **<HardLinkStoreControl>** 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 **<ErrorControl>** section can be configured to conditionally ignore file access errors, based on the file’s location.
|
> The **<ErrorControl>** section can be configured to conditionally ignore file access errors, based on the file’s location.
|
||||||
|
|
||||||
``` xml
|
``` xml
|
||||||
<Policy>
|
<Policy>
|
||||||
|
@ -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
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user