mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 12:23:37 +00:00
Metadata update deployment/usmt 10
This commit is contained in:
Frank Rojas
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Identify Applications Settings (Windows 10)
|
||||
description: Identify which applications and settings you want to migrate before using the User State Migration Tool (USMT).
|
||||
description: Identify which applications and settings you want to migrate before using the User State Migration Tool (USMT).
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
@ -11,50 +11,36 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Identify Applications Settings
|
||||
# Identify applications settings
|
||||
|
||||
|
||||
When planning for your migration, you should identify which applications and settings you want to migrate. For more information about how to create a custom .xml file to migrate the settings of another application, see [Customize USMT XML Files](usmt-customize-xml-files.md).
|
||||
When planning for your migration, you should identify which applications and settings you want to migrate. For more information about how to create a custom .xml file to migrate the settings of another application, see [Customize USMT XML files](usmt-customize-xml-files.md).
|
||||
|
||||
## Applications
|
||||
|
||||
First, create and prioritize a list of applications that need to be migrated. It may be helpful to review the application lists and decide which applications will be redeployed and which applications will be retired. Often, what applications are migrated are prioritized based on a combination of how widely the application is used and how complex the application is.
|
||||
|
||||
First, create and prioritize a list of applications that to be migrated. It may be helpful to review the application lists and decide which applications will be redeployed and which applications will be retired. Often, the applications are prioritized based on a combination of how widely the application is used and how complex the application is.
|
||||
Next, identify an application owner to be in charge of each application. Application ownership identification is necessary because the developers won't be experts on all of the applications in the organization. The application owner should have the most experience with an application. The application owner provides insight into how the organization installs, configures, and uses the application.
|
||||
|
||||
Next, identify an application owner to be in charge of each application. This is necessary because the developers will not be experts on all of the applications in the organization. The application owner should have the most experience with an application. The application owner provides insight into how the organization installs, configures, and uses the application.
|
||||
## Application settings
|
||||
|
||||
## Application Settings
|
||||
Next, determine and locate the application settings to be migrated. You can acquire much of the information that you need for this step when you're testing the new applications for compatibility with the new operating system.
|
||||
|
||||
After completing the list of applications to be migrated, review the list, and work with each application owner on a list of settings to be migrated. For each setting, determine whether it needs to be migrated or if the default settings are adequate. Then, determine where the setting is located; for example, in the registry or in an .ini file. Next, consider the following questions to determine what needs to be done to migrate the setting successfully:
|
||||
|
||||
Next, determine and locate the application settings to be migrated. You can acquire much of the information that you need for this step when you are testing the new applications for compatibility with the new operating system.
|
||||
- Is the destination version of the application newer than the source version?
|
||||
|
||||
After completing the list of applications to be migrated, review the list and work with each application owner on a list of settings to be migrated. For each setting, determine whether it needs to be migrated or if the default settings are adequate. Then, determine where the setting is located; for example, in the registry or in an .ini file. Next, consider the following questions to determine what needs to be done to migrate the setting successfully:
|
||||
- Do these settings work with the new version?
|
||||
|
||||
- Is the destination version of the application newer than the source version?
|
||||
- Do the settings need to be moved or altered?
|
||||
|
||||
- Do these settings work with the new version?
|
||||
|
||||
- Do the settings need to be moved or altered?
|
||||
|
||||
- Can the first-run process force the application to appear as if it had run already? If so, does this work correctly, or does it break the application?
|
||||
- Can the first-run process force the application to appear as if it had run already? If so, does this work correctly, or does it break the application?
|
||||
|
||||
After answering these questions, create a custom .xml file to migrate settings. Work with the application owner to develop test cases and to determine the file types that need to be migrated for the application.
|
||||
|
||||
## Locating Where Settings Are Stored
|
||||
|
||||
|
||||
See [Migrate Application Settings](migrate-application-settings.md) and follow the directions.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Determine What to Migrate](usmt-determine-what-to-migrate.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Locating where settings are stored
|
||||
|
||||
See [Migrate application settings](migrate-application-settings.md) and follow the directions.
|
||||
|
||||
## Related articles
|
||||
|
||||
[Determine what to migrate](usmt-determine-what-to-migrate.md)
|
||||
|
||||
@ -11,39 +11,31 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Identify File Types, Files, and Folders
|
||||
# Identify file types, files, and folders
|
||||
|
||||
When planning for your migration, if not using MigDocs.xml, you should identify the file types, files, folders, and settings that you want to migrate. First, you should determine the standard file locations on each computer, such as **My Documents** , `C:\Data` , and company-specified locations, such as `\\EngineeringDrafts`. Next, you should determine and locate the non-standard locations. For non-standard locations, consider the following items:
|
||||
|
||||
When planning for your migration, if not using MigDocs.xml, you should identify the file types, files, folders, and settings that you want to migrate. First, you should determine the standard file locations on each computer, such as **My Documents.** , **C:\\Data** , and company-specified locations, such as **\\EngineeringDrafts**. Next, you should determine and locate the non-standard locations. For non-standard locations, consider the following:
|
||||
- **File types**. Consider which file types need to be included and excluded from the migration. You can create this list based on common applications used in your organization. Applications normally use specific file name extensions. For example, Microsoft Office Word primarily uses `.doc`, `.docx` and `.dotx` file name extension. However, it also uses other file types, such as templates (`.dot` files), on a less frequent basis.
|
||||
|
||||
- **File types**. Consider which file types need to be included and excluded from the migration. You can create this list based on common applications used in your organization. Applications normally use specific file name extensions. For example, Microsoft Office Word primarily uses .doc, .docx and .dotx file name extension. However, it also uses other file types, such as templates (.dot files), on a less frequent basis.
|
||||
- **Excluded locations**. Consider the locations on the computer that should be excluded from the migration (for example, `%WINDIR%` and **Program Files**).
|
||||
|
||||
- **Excluded locations**. Consider the locations on the computer that should be excluded from the migration (for example, %WINDIR% and Program Files).
|
||||
- **New locations**. Decide where files should be migrated to on the destination computer, such as **My Documents**, a designated folder, or a folder matching the files' name and location on the source computer. For example, you might have shared data on source machine or you might wish to clean up documents outside the user profiles on the source system. Identify any data that needs to be redirected to a new location in the apply phase. Redirection can be accomplished with location modify rules.
|
||||
|
||||
- **New locations**. Decide where files should be migrated to on the destination computer for example, \\My Documents, a designated folder, or a folder matching the files' name and location on the source computer. For example, you might have shared data on source machine or you might wish to clean up documents outside the user profiles on the source system. Identify any data that needs to be redirected to a new location in the apply phase. This can be accomplished with location modify rules.
|
||||
Once you've verified which files and file types that the end users work with regularly, you'll need to locate them. Files may be saved to a single folder or scattered across a drive. A good starting point for finding files types to include is to look at the registered file types on the computer.
|
||||
|
||||
Once you have verified which files and file types that the end users work with regularly, you will need to locate them. Files may be saved to a single folder or scattered across a drive. A good starting point for finding files types to include is to look at the registered file types on the computer.
|
||||
To find the registered file types on a computer running Windows 7, Windows 8, Windows 10, or Windows 11:
|
||||
|
||||
**To find the registered file types on a computer running Windows 7 or Windows 8**
|
||||
1. Open **Control Panel**
|
||||
2. Make sure **View by:** is set to **Category** and then select **Programs**.
|
||||
|
||||
1. Click **Start**. Open **Control Panel**, click **Control Panel Home**, and click **Programs**.
|
||||
|
||||
2. Click **Default Programs**, and click **Associate a file type or protocol with a program**.
|
||||
|
||||
3. On this screen, the registered file types are displayed.
|
||||
|
||||
For more information about how to change the file types, files, and folders that are migrated when you specify the MigUser.xml file, see [User State Migration Tool (USMT) How-to topics](usmt-how-to.md).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Determine What to Migrate](usmt-determine-what-to-migrate.md)
|
||||
|
||||
|
||||
|
||||
|
||||
3. Select **Default Programs**
|
||||
|
||||
4. select **Associate a file type or protocol with a program**.
|
||||
|
||||
5. On this screen, the registered file types are displayed.
|
||||
|
||||
For more information about how to change the file types, files, and folders that are migrated when you specify the MigUser.xml file, see [User State Migration Tool (USMT) how-to topics](usmt-how-to.md).
|
||||
|
||||
## Related articles
|
||||
|
||||
[Determine what to migrate](usmt-determine-what-to-migrate.md)
|
||||
|
||||
@ -11,48 +11,35 @@ ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Identify Operating System Settings
|
||||
# Identify operating system settings
|
||||
|
||||
When planning for your migration, you should identify which operating system settings you want to migrate and to what extent you want to create a new standard environment on each of the computers. User State Migration Tool (USMT) 10.0 enables you to migrate select settings and keep the default values for all others. The operating system settings include the following parameters:
|
||||
|
||||
When planning for your migration, you should identify which operating system settings you want to migrate and to what extent you want to create a new standard environment on each of the computers. User State Migration Tool (USMT) 10.0 enables you to migrate select settings and keep the default values for all others. The operating system settings include the following parameters:
|
||||
|
||||
- **Appearance.**
|
||||
- **Appearance**
|
||||
|
||||
The appearance factor includes items such as wallpaper, colors, sounds, and the location of the taskbar.
|
||||
|
||||
- **Action.**
|
||||
- **Action**
|
||||
|
||||
The action factor includes items such as the key-repeat rate, whether double-clicking a folder opens it in a new window or the same window, and whether you need to single-click or double-click an item to open it.
|
||||
|
||||
- **Internet.**
|
||||
- **Internet**
|
||||
|
||||
The Internet factor includes the settings that let you connect to the Internet and control how your browser operates. The settings include items such as your home page URL, favorites, bookmarks, cookies, security settings, dial-up connections, and proxy settings.
|
||||
|
||||
- **Mail.**
|
||||
- **Mail**
|
||||
|
||||
The mail factor includes the information that you need to connect to your mail server, your signature file, views, mail rules, local mail, and contacts.
|
||||
|
||||
To help you decide which settings to migrate, you should consider any previous migration experiences and the results of any surveys and tests that you have conducted. You should also consider the number of help-desk calls related to operating-system settings that you have had in the past, and are able to handle in the future. Also decide how much of the new operating-system functionality you want to take advantage of.
|
||||
To help you decide which settings to migrate, you should consider any previous migration experiences and the results of any surveys and tests that you've conducted. You should also consider the number of help-desk calls related to operating-system settings that you've had in the past, and are able to handle in the future. Also decide how much of the new operating-system functionality you want to take advantage of.
|
||||
|
||||
You should migrate any settings that users need to get their jobs done, those settings that make the work environment comfortable, and those settings that will reduce help-desk calls after the migration. Although it is easy to dismiss migrating user preferences, you should consider the factor of users spending a significant amount of time restoring items such as wallpaper, screen savers, and other customizable user-interface features. Most users do not remember how these settings were applied. Although these items are not critical to migration success, migrating these items increases user productivity and overall satisfaction of the migration process.
|
||||
You should migrate any settings that users need to get their jobs done, those settings that make the work environment comfortable, and those settings that will reduce help-desk calls after the migration. Although it's easy to dismiss migrating user preferences, you should consider the factor of users spending a significant amount of time restoring items such as wallpaper, screen savers, and other customizable user-interface features. Most users don't remember how these settings were applied. Although these items aren't critical to migration success, migrating these items increases user productivity and overall satisfaction of the migration process.
|
||||
|
||||
**Note**
|
||||
For more information about how to change the operating-system settings that are migrated, see [User State Migration Tool (USMT) How-to topics](usmt-how-to.md).
|
||||
> [!NOTE]
|
||||
> For more information about how to change the operating-system settings that are migrated, see [User State Migration Tool (USMT) how-to topics](usmt-how-to.md).
|
||||
|
||||
For information about the operating-system settings that USMT migrates, see [What Does USMT Migrate?](usmt-what-does-usmt-migrate.md)
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
For information about the operating-system settings that USMT migrates, see [What does USMT migrate?](usmt-what-does-usmt-migrate.md)
|
||||
|
||||
## Related articles
|
||||
|
||||
[Determine What to Migrate](usmt-determine-what-to-migrate.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Identify Users (Windows 10)
|
||||
description: Learn how to identify users you plan to migrate, as well as how to migrate local accounts and domain accounts.
|
||||
description: Learn how to identify users you plan to migrate, and how to migrate local accounts and domain accounts.
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
@ -12,53 +12,56 @@ ms.technology: itpro-deploy
|
||||
ms.date: 11/01/2022
|
||||
---
|
||||
|
||||
# Identify Users
|
||||
# Identify users
|
||||
|
||||
It is important to carefully consider how you plan to migrate users. By default, all users are migrated by User State Migration Tool (USMT) 5.0. You must specify which users to include by using the command line. You cannot specify users in the .xml files. For instructions on how to migrate users, see [Migrate User Accounts](usmt-migrate-user-accounts.md).
|
||||
It's important to carefully consider how you plan to migrate users. By default, all users are migrated by User State Migration Tool (USMT) 5.0. You must specify which users to include by using the command line. You can't specify users in the .xml files. For instructions on how to migrate users, see [Migrate user accounts](usmt-migrate-user-accounts.md).
|
||||
|
||||
## In this topic
|
||||
|
||||
- [Migrating Local Accounts](#bkmk-8)
|
||||
- [Migrating Domain Accounts](#bkmk-9)
|
||||
- [Command-Line Options](#bkmk-7)
|
||||
- [Identify users](#identify-users)
|
||||
- [In this topic](#in-this-topic)
|
||||
- [Migrating local accounts](#migrating-local-accounts)
|
||||
- [Migrating domain accounts](#migrating-domain-accounts)
|
||||
- [Command-line options](#command-line-options)
|
||||
- [Related articles](#related-articles)
|
||||
|
||||
## <a href="" id="bkmk-8"></a>Migrating Local Accounts
|
||||
## Migrating local accounts
|
||||
|
||||
Before migrating local accounts, note the following:
|
||||
Before migrating local accounts, be aware of the following items:
|
||||
|
||||
- [You must explicitly specify that local accounts that are not on the destination computer should be migrated.](#bkmk-8) If you are migrating local accounts and the local account does not exist on the destination computer, you must use the **/lac** option when using the LoadState command. If the **/lac** option is not specified, no local user accounts will be migrated.
|
||||
- **You must explicitly specify that local accounts that are not on the destination computer should be migrated**. If you're migrating local accounts and the local account doesn't exist on the destination computer, you must use the `/lac` option when using the `LoadState.exe` command. If the `/lac` option isn't specified, no local user accounts will be migrated.
|
||||
|
||||
- [Consider whether to enable user accounts that are new to the destination computer.](#bkmk-8) The **/lae** option enables the account that was created with the **/lac** option. However, if you create a disabled local account by using only the **/lac** option, a local administrator must enable the account on the destination computer.
|
||||
- **Consider whether to enable user accounts that are new to the destination computer.** The `/lae` option enables the account that was created with the `/lac` option. However, if you create a disabled local account by using only the `/lac` option, a local administrator must enable the account on the destination computer.
|
||||
|
||||
- [Be careful when specifying a password for local accounts.](#bkmk-8) If you create the local account with a blank password, anyone could log on to that account on the destination computer. If you create the local account with a password, the password is available to anyone with access to the USMT command-line tools.
|
||||
- **Be careful when specifying a password for local accounts.** If you create the local account with a blank password, anyone could sign in that account on the destination computer. If you create the local account with a password, the password is available to anyone with access to the USMT command-line tools.
|
||||
|
||||
>[!NOTE]
|
||||
>If there are multiple users on a computer, and you specify a password with the **/lac** option, all migrated users will have the same password.
|
||||
> [!NOTE]
|
||||
> If there are multiple users on a computer, and you specify a password with the `/lac` option, all migrated users will have the same password.
|
||||
|
||||
## <a href="" id="bkmk-9"></a>Migrating Domain Accounts
|
||||
## Migrating domain accounts
|
||||
|
||||
The source and destination computers do not need to be connected to the domain for domain user profiles to be migrated.
|
||||
The source and destination computers don't need to be connected to the domain for domain user profiles to be migrated.
|
||||
|
||||
## <a href="" id="bkmk-7"></a>Command-Line Options
|
||||
## Command-line options
|
||||
|
||||
USMT provides several options to migrate multiple users on a single computer. The following command-line options specify which users to migrate.
|
||||
|
||||
- [Specifying users.](#bkmk-8) You can specify which users to migrate with the **/all**, **/ui**, **/uel**, and **/ue** options with both the ScanState and LoadState command-line tools.
|
||||
- **Specifying users.** You can specify which users to migrate with the `/all`, `/ui`, `/uel`, and `/ue` options with both the **ScanState** and **LoadState** command-line tools.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The **/uel** option excludes users based on the **LastModified** date of the Ntuser.dat file. The **/uel** option is not valid in offline migrations.
|
||||
> [!IMPORTANT]
|
||||
> The `/uel` option excludes users based on the **LastModified** date of the `Ntuser.dat` file. The `/uel` option is not valid in offline migrations.
|
||||
|
||||
- [Moving users to another domain.](#bkmk-8) You can move user accounts to another domain using the **/md** option with the LoadState command-line tool.
|
||||
- **Moving users to another domain.** You can move user accounts to another domain using the `/md` option with the **LoadState** command-line tool.
|
||||
|
||||
- [Creating local accounts.](#bkmk-8) You can create and enable local accounts using the **/lac** and **/lae** options with the LoadState command-line tool.
|
||||
- **Creating local accounts.** You can create and enable local accounts using the `/lac` and `/lae` options with the **LoadState** command-line tool.
|
||||
|
||||
- [Renaming user accounts.](#bkmk-8) You can rename user accounts using the **/mu** option.
|
||||
- **Renaming user accounts.** You can rename user accounts using the `/mu` option.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>By default, if a user name is not specified in any of the command-line options, the user will be migrated.
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
[Determine What to Migrate](usmt-determine-what-to-migrate.md)<br>
|
||||
[ScanState Syntax](usmt-scanstate-syntax.md)<br>
|
||||
[LoadState Syntax](usmt-loadstate-syntax.md)
|
||||
- [Determine what to migrate](usmt-determine-what-to-migrate.md)
|
||||
- [ScanState syntax](usmt-scanstate-syntax.md)
|
||||
- [LoadState syntax](usmt-loadstate-syntax.md)
|
||||
|
||||
Reference in New Issue
Block a user