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

Remove troubleshooting articles from USMT and BitLocker 2

Browse Source
This commit is contained in:
Frank Rojas
2022-11-28 20:49:19 -05:00
parent c3125585f2
commit 7a115a04df
7 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/TOC.yml
View File

@ -538,13 +538,13 @@
items:
- name: USMT Troubleshooting
href: usmt/usmt-troubleshooting.md
- name: Common Issues
- name: USMT Common Issues
href: /troubleshoot/windows-client/deployment/usmt-common-issues
- name: Frequently Asked Questions
- name: USMT Frequently Asked Questions
href: usmt/usmt-faq.yml
- name: Log Files
- name: USMT Log Files
href: usmt/usmt-log-files.md
- name: Return Codes
- name: USMT Return Codes
href: /troubleshoot/windows-client/deployment/usmt-return-codes
- name: USMT Resources
href: usmt/usmt-resources.md

4
windows/deployment/usmt/usmt-extract-files-from-a-compressed-migration-store.md
View File

@ -25,7 +25,7 @@ Options used with the `/extract` option can specify:
In addition, you can specify the file patterns that you want to extract by using the `/i` option to include file patterns or the `/e` option to exclude file patterns. When both the `/i` option and the `/e` option are used in the same command, include patterns take precedence over exclude patterns. Note that this is different from the include and exclude rules used in the **ScanState** and **LoadState** tools.
### To run the UsmtUtils tool with the /extract option
## To run the UsmtUtils tool with the /extract option
To extract files from the compressed migration store onto the destination computer, use the following UsmtUtils syntax:
@ -93,6 +93,6 @@ In this example, if there is a myProject.exe file, it will also be extracted bec
[UsmtUtils syntax](usmt-utilities.md)
[Return codes](usmt-return-codes.md)
[Return codes](/troubleshoot/windows-client/deployment/usmt-return-codes)
[Verify the condition of a compressed migration store](verify-the-condition-of-a-compressed-migration-store.md)

2
windows/deployment/usmt/usmt-test-your-migration.md
View File

@ -17,7 +17,7 @@ Always test your migration plan in a controlled laboratory setting before you de
After you've thoroughly tested the entire migration process on a single computer running each of your source operating systems, conduct a pilot migration with a small group of users. After migrating a few typical user states to the intermediate store, note the space required and adjust your initial calculations accordingly. For details about estimating the space needed for your migration, see [Estimate migration store size](usmt-estimate-migration-store-size.md). You might also need to adjust the registry-setting and file-location information in your migration-rule files. If you make changes, test the migration again. Then verify that all data and settings have migrated as expected. A pilot migration also gives you an opportunity to test your space estimates for the intermediate store.
If your test migration encounters any errors, examine the **ScanState** and **LoadState** logs to obtain the exact User State Migration Tool (USMT) 10.0 return code and associated error messages or Windows application programming interface (API) error message. For more information about USMT return codes and error messages, see [Return codes](usmt-return-codes.md). You can obtain more information about any listed **Windows** system error codes by typing in a command prompt window `net.exe helpmsg <error_number>` where *<error_number>* is the error code number generated by the error message. For more information about System Error Codes, see [System Error Codes (0-499)](/windows/win32/debug/system-error-codes--0-499-).
If your test migration encounters any errors, examine the **ScanState** and **LoadState** logs to obtain the exact User State Migration Tool (USMT) 10.0 return code and associated error messages or Windows application programming interface (API) error message. For more information about USMT return codes and error messages, see [Return codes](/troubleshoot/windows-client/deployment/usmt-return-codes). You can obtain more information about any listed **Windows** system error codes by typing in a command prompt window `net.exe helpmsg <error_number>` where *<error_number>* is the error code number generated by the error message. For more information about System Error Codes, see [System Error Codes (0-499)](/windows/win32/debug/system-error-codes--0-499-).
In most cases, the **ScanState** and **LoadState** logs indicate why a USMT migration is failing. We recommend that you use the `/v:5` option when testing your migration. This verbosity level can be adjusted in a production migration. Reducing the verbosity level might make it more difficult to diagnose failures that are encountered during production migrations. You can use a higher verbosity level if you want the log files output to go to a debugger.

4
windows/deployment/usmt/usmt-troubleshooting.md
View File

@ -19,10 +19,10 @@ The following table describes articles that address common User State Migration
| Link | Description |
|--- |--- |
|[Common Issues](usmt-common-issues.md)|Find troubleshooting solutions for common problems in USMT.|
|[Common Issues](/troubleshoot/windows-client/deployment/usmt-common-issues)|Find troubleshooting solutions for common problems in USMT.|
|[Frequently Asked Questions](usmt-faq.yml)|Find answers to questions about how to use USMT.|
|[Log Files](usmt-log-files.md)|Learn how to enable logging to help you troubleshoot issues in USMT.|
|[Return Codes](usmt-return-codes.md)|Learn how to use return codes to identify problems in USMT.|
|[Return Codes](/troubleshoot/windows-client/deployment/usmt-return-codes)|Learn how to use return codes to identify problems in USMT.|
|[USMT Resources](usmt-resources.md)|Find more information and support for using USMT.|
## Related articles

2
windows/deployment/usmt/usmt-utilities.md
View File

@ -97,4 +97,4 @@ Some examples of `/extract` commands:
[User State Migration Tool (USMT) command-line syntax](usmt-command-line-syntax.md)
[Return codes](usmt-return-codes.md)
[Return codes](/troubleshoot/windows-client/deployment/usmt-return-codes)

6
windows/deployment/usmt/usmt-what-does-usmt-migrate.md
View File

@ -53,7 +53,7 @@ This section describes the user data that USMT migrates by default, using the `M
- Favorites
> [!IMPORTANT]
> Starting in Windows 10, version 1607 the USMT does not migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](./usmt-common-issues.md#usmt-doesnt-migrate-the-start-layout).
> Starting in Windows 10, version 1607 the USMT does not migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](/troubleshoot/windows-client/deployment/usmt-common-issues#usmt-doesnt-migrate-the-start-layout).
- **Folders from the All Users and Public profiles.** When you specify the `MigUser.xml` file, USMT also migrates the following from the **Public** profile in Windows Vista, Windows 7, Windows 8, or Windows 10:
@ -209,7 +209,7 @@ When you specify the `MigApp.xml` file, USMT migrates the settings for the follo
## What USMT doesn't migrate
The following items are settings that USMT doesn't migrate. If you're having a problem that isn't listed here, see [Common issues](usmt-common-issues.md).
The following items are settings that USMT doesn't migrate. If you're having a problem that isn't listed here, see [Common issues](/troubleshoot/windows-client/deployment/usmt-common-issues).
### Application settings
@ -247,7 +247,7 @@ You should also note the following items:
### Start menu layout
Starting in Windows 10, version 1607 the USMT doesn't migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](./usmt-common-issues.md#usmt-doesnt-migrate-the-start-layout).
Starting in Windows 10, version 1607 the USMT doesn't migrate the Start menu layout. To migrate a user's Start menu, you must export and then import settings using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](/troubleshoot/windows-client/deployment/usmt-common-issues#usmt-doesnt-migrate-the-start-layout).
### User profiles from Active Directory to Azure Active Directory

2
windows/deployment/usmt/verify-the-condition-of-a-compressed-migration-store.md
View File

@ -101,4 +101,4 @@ If the `/verify` option indicates that there are corrupted files in the migratio
[UsmtUtils syntax](usmt-utilities.md)
[Return codes](usmt-return-codes.md)
[Return codes](/troubleshoot/windows-client/deployment/usmt-return-codes)