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

Metadata update deployment/usmt 3

Browse Source
This commit is contained in:
Frank Rojas 2022-11-01 11:54:10 -04:00
parent 7bb8adb4d1
commit d602eaecfb
7 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
windows/deployment/usmt/getting-started-with-the-user-state-migration-tool.md
View File

@ -14,7 +14,8 @@ ms.date: 11/01/2022
# Getting Started with the User State Migration Tool (USMT)
This article outlines the general process that you should follow to migrate files and settings.
## In this article
## In this topic
- [Step 1: Plan Your Migration](#step-1-plan-your-migration)
- [Step 2: Collect files and settings from the source computer](#step-2-collect-files-and-settings-from-the-source-computer)

2
windows/deployment/usmt/migrate-application-settings.md
View File

@ -19,7 +19,7 @@ This article defines how to author a custom migration .xml file that migrates th
This article doesn't contain information about how to migrate applications that store settings in an application-specific store, only the applications that store the information in files or in the registry. It also doesn't contain information about how to migrate the data that users create using the application. For example, if the application creates .doc files using a specific template, this article doesn't discuss how to migrate the .doc files and templates themselves.
## <a href="" id="createxmlmigappsettings"></a>In this article
## In this topic
- [Before You Begin](#bkmk-beforebegin)

3
windows/deployment/usmt/migration-store-types-overview.md
View File

@ -15,7 +15,7 @@ ms.technology: itpro-deploy
When planning your migration, you should determine which migration store type best meets your needs. As part of these considerations, determine how much space is required to run the User State Migration Tool (USMT) 10.0 components on your source and destination computers. You should also determine the space needed to create and host the migration store, whether you're using a local share, network share, or storage device.
## In this article
## In this topic
[Migration Store Types](#bkmk-types)
@ -47,7 +47,6 @@ The following flowchart illustrates the procedural differences between a local m
## <a href="" id="bkmk-localvremote"></a>Local Store vs. Remote Store
If you have enough space and you're migrating the user state back to the same computer, storing data on a local device is normally the best option to reduce server storage costs and network performance issues. You can store the data locally either on a different partition or on a removable device such as a USB flash drive (UFD). Also, depending on the imaging technology that you're using, you might be able to store the data on the partition that is being re-imaged, if the data will be protected from deletion during the process. To increase performance, store the data on high-speed drives that use a high-speed network connection. It's also good practice to ensure that the migration is the only task the server is performing.
If there isn't enough local disk space, or if you're moving the user state to another computer, then you must store the data remotely. For example, you can store it in on a shared folder, on removable media such as a UFD drive, or you can store it directly on the destination computer. For example, create and share C:\\store on the destination computer. Then run the ScanState command on the source computer and save the files and settings to \\\\*DestinationComputerName*\\store. Then, run the **LoadState** command on the destination computer and specify **C:\\Store** as the store location. By doing this process, you don't need to save the files to a server.

2
windows/deployment/usmt/offline-migration-reference.md
View File

@ -27,7 +27,7 @@ When you use User State Migration Tool (USMT) 10.0 to gather and restore user s
- **New recovery scenario.** In scenarios where a machine no longer restarts properly, it might be possible to gather user state with the ScanState tool from within WinPE.
## In This topic
## In this topic
- [What Will Migrate Offline?](#bkmk-whatwillmigrate)

2
windows/deployment/usmt/understanding-migration-xml-files.md
View File

@ -17,7 +17,7 @@ You can modify the behavior of a basic User State Migration Tool (USMT) 10.0 mig
This topic provides an overview of the default and custom migration XML files and includes guidelines for creating and editing a customized version of the MigDocs.xml file. The MigDocs.xml file uses the new **GenerateDocPatterns** function available in USMT to automatically find user documents on a source computer.
## In This topic
## In this topic
[Overview of the Config.xml file](#bkmk-config)

2
windows/deployment/usmt/usmt-common-issues.md
View File

@ -16,7 +16,7 @@ ms.technology: itpro-deploy
The following sections discuss common issues that you might see when you run the User State Migration Tool (USMT) 10.0 tools. USMT produces log files that describe in further detail any errors that occurred during the migration process. These logs can be used to troubleshoot migration failures.
## In This Topic
## In this topic
[User Account Problems](#user)

2
windows/deployment/usmt/usmt-common-migration-scenarios.md
View File

@ -18,7 +18,7 @@ You use the User State Migration Tool (USMT) 10.0 when hardware and/or operatin
One common scenario when only the operating system, and not the hardware, is being upgraded is referred to as *PC refresh*. A second common scenario is known as *PC replacement*, where one piece of hardware is being replaced, typically by newer hardware and a newer operating system.
## In this topic
**In this article:**
[PC Refresh](#bkmk-pcrefresh)