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

Fixed warnings

Browse Source
This commit is contained in:
Benzy Dharmanayagam
2021-11-26 11:52:38 +05:30
parent 4530dd0f30
commit 5a8d872f89
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/usmt/usmt-return-codes.md
View File

@ -119,7 +119,7 @@ The following table lists each return code by numeric value, along with the asso
|||The store save location is read-only or does not support a requested storage option|Make sure that the store path is accessible and that the proper permission levels are set.||
|28|USMT_UNABLE_GET_SCRIPTFILES|Script file is invalid for /i|Check all specified migration .xml files for errors. This is a common error when using /i to load the Config.xml file.|Setup and Initialization|
|||Unable to find a script file specified by /i|Verify the location of your script files, and ensure that the command-line options are correct.||
|29|USMT_FAILED_MIGSTARTUP|A minimum of 250 MB of free space is required for temporary files|Verify that the system meets the minimum temporary disk space requirement of 250 MB. As a workaround, you can set the environment variable USMT_WORKING_DIR=<path> to redirect the temporary files working directory.|Setup and Initialization|
|29|USMT_FAILED_MIGSTARTUP|A minimum of 250 MB of free space is required for temporary files|Verify that the system meets the minimum temporary disk space requirement of 250 MB. As a workaround, you can set the environment variable USMT_WORKING_DIR=&lt;path&gt; to redirect the temporary files working directory.|Setup and Initialization|
|||Another process is preventing migration; only one migration tool can run at a time|Check the ScanState log file for migration .xml file errors.||
|||Failed to start main processing, look in log for system errors or check the installation|Check the ScanState log file for migration .xml file errors.||
|||Migration failed because of an XML error; look in the log for specific details|Check the ScanState log file for migration .xml file errors.||
@ -146,7 +146,7 @@ The following table lists each return code by numeric value, along with the asso
|41|USMT_PREFLIGHT_FILE_CREATION_FAILED|Can't overwrite existing file|The Progress log could not be created. Verify that the location is valid and that you have write access.|Setup and Initialization|
|||Invalid space estimate path. Check the parameters and/or file system permissions|Review ScanState log or LoadState log for details about command-line errors.||
|42|USMT_ERROR_CORRUPTED_STORE|The store contains one or more corrupted files|Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md).||
|61|USMT_MIGRATION_STOPPED_NONFATAL|Processing stopped due to an I/O error|USMT exited but can continue with the /c command-line option, with the optional configurable <ErrorControl> section or by using the /vsc command-line option.|Non-fatal Errors|
|61|USMT_MIGRATION_STOPPED_NONFATAL|Processing stopped due to an I/O error|USMT exited but can continue with the /c command-line option, with the optional configurable &lt;ErrorControl&gt; section or by using the /vsc command-line option.|Non-fatal Errors|
|71|USMT_INIT_OPERATING_ENVIRONMENT_FAILED|A Windows Win32 API error occurred|Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details.|Fatal Errors|
|||An error occurred when attempting to initialize the diagnostic mechanisms such as the log|Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details.||
|||Failed to record diagnostic information|Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details.||

4
windows/deployment/usmt/usmt-scanstate-syntax.md
View File

@ -231,10 +231,10 @@ The following table indicates which command-line options are not compatible with
|/**ui**|||X|X|
|/**ue**|||X|X|
|/**uel**|||X|X|
|/**efs**:*<option>*|||X||
|/**efs**:*&lt;option&gt;*|||X||
|/**genconfig**|||N/A||
|/**config**|||X||
|*<StorePath>*|||X||
|*&lt;StorePath&gt;*|||X||
> [!NOTE]
> You must specify either the /**key** or /**keyfile** option with the /**encrypt** option.

2
windows/deployment/usmt/usmt-xml-elements-library.md
View File

@ -1997,7 +1997,7 @@ These functions return either a string or a pattern.
|Setting|Required?|Value|
|--- |--- |--- |
| *ObjectType* | Yes | The type of object. Can be Registry or Ini (for an .ini file). |
| *EncodedLocationPattern* | Yes | <ul><li>If type of object is Registry, EncodedLocationPattern must be a valid registry path. For example, HKLM\SOFTWARE\MyKey[].</li><li>If the type of object is Ini, then EncodedLocationPattern must be in the following format: <br/>IniFilePath|SectionName[SettingName]</li></ul> |
| *EncodedLocationPattern* | Yes | <ul><li>If type of object is Registry, EncodedLocationPattern must be a valid registry path. For example, HKLM\SOFTWARE\MyKey[].</li><li>If the type of object is Ini, then EncodedLocationPattern must be in the following format: <br/>IniFilePath&#124;SectionName[SettingName]</li></ul> |
| *ExpandContent* | No (default=TRUE) | Can be TRUE or FALSE. If FALSE, then the given location will not be expanded before it is returned. |
~~~