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

Metadata update deployment/usmt 13

Browse Source
This commit is contained in:
Frank Rojas
2022-11-03 19:53:26 -04:00
parent 1d844f73bf
commit f0bab1bb78
5 changed files with 36 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
windows/deployment/upgrade/log-files.md
View File

@ -13,16 +13,16 @@ ms.technology: itpro-deploy
ms.date: 10/28/2022
---
# Log files
# Windows upgrade log files
**Applies to**
- Windows 10
> [!NOTE]
> This is a 400 level topic (advanced).<br>
> See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is **setupact.log**. The log files are located in a different folder depending on the Windows Setup phase. Recall that you can determine the phase from the extend code.
> [!NOTE]
@ -62,7 +62,6 @@ See the following example:
|------|------------|------------|------------|
|2016-09-08 09:23:50,| Warning | MIG | Couldn't replace object C:\Users\name\Cookies. Target Object can't be removed.|
## Analyze log files
The following instructions are meant for IT professionals. Also see the [Upgrade error codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json) section in this guide to familiarize yourself with [result codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes) and [extend codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes).
@ -90,8 +89,8 @@ To analyze Windows Setup log files:
7. Search for the following important text strings:
* **Shell application requested abort**
* **Abandoning apply due to error for object**
- `Shell application requested abort`
- `Abandoning apply due to error for object`
8. Decode Win32 errors that appear in this section.
@ -101,8 +100,9 @@ To analyze Windows Setup log files:
For example, assume that the error code for an error is 0x8007042B - 0x2000D. Searching for "8007042B" reveals the following content from the setuperr.log file:
> [!Note]
> [!NOTE]
> Some lines in the text below are shortened to enhance readability. For example
>
> - The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds
> - The certificate file name, which is a long text string, is shortened to just "CN."

2
windows/deployment/usmt/usmt-loadstate-syntax.md
View File

@ -1,4 +1,4 @@
---This
---
title: LoadState Syntax (Windows 10)
description: Learn about the syntax and usage of the command-line options available when you use the LoadState command.
ms.reviewer:

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

@ -11,7 +11,7 @@ ms.topic: article
ms.technology: itpro-deploy
---
# Log files
# USMT log files
You can use User State Migration Tool (USMT) 10.0 logs to monitor your migration and to troubleshoot errors and failed migrations. This article describes the available command-line options to enable USMT logs, and new XML elements that configure which types of errors are fatal and should halt the migration, which types are non-fatal and should be skipped so that the migration can continue.

2
windows/deployment/usmt/usmt-migrate-efs-files-and-certificates.md
View File

@ -13,7 +13,7 @@ ms.technology: itpro-deploy
# Migrate EFS files and certificates
This article describes how to migrate Encrypting File System (EFS) certificates. For more information about the `/efs` option, see [Encrypted file options](#encrypted-file-options) in [ScanState syntax](usmt-scanstate-syntax.md).
This article describes how to migrate Encrypting File System (EFS) certificates. For more information about the `/efs` option, see [Encrypted file options](usmt-scanstate-syntax.md#encrypted-file-options) in [ScanState syntax](usmt-scanstate-syntax.md).
## To migrate EFS files and certificates

3
windows/deployment/usmt/usmt-requirements.md
View File

@ -34,7 +34,7 @@ The following table lists the operating systems supported in USMT.
## Unsupported scenarios
- USMT doesn't support any of the Windows Server® operating systems.
- USMT for Windows 10 shouldn't be used for migrating between previous versions of Windows. USMT for Windows 10 is only meant to migrate to Windows 10 or between Windows 10 versions. For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](/previous-versions/windows/server/dd560801(v=ws.10)).
- USMT for Windows 10 shouldn't be used for migrating between previous versions of Windows. USMT for Windows 10 is only meant to migrate to Windows 10 or between Windows 10 versions. For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User's Guide](/previous-versions/windows/server/dd560801(v=ws.10)).
## Windows PE
@ -55,6 +55,7 @@ To open an elevated command prompt:
> [!IMPORTANT]
> You must run USMT using an account with full administrative permissions, including the following privileges:
>
> - SeBackupPrivilege (Back up files and directories)
> - SeDebugPrivilege (Debug programs)
> - SeRestorePrivilege (Restore files and directories)