mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
USMT and other deploy articles refresh 2024-08
This commit is contained in:
Frank Rojas
parent
17ec7ace94
commit
2282f15a76
Binary file not shown.
|
Before Width: | Height: | Size: 38 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 94 KiB |
@ -1,70 +1,70 @@
|
||||
---
|
||||
title: Windows Upgrade and Migration Considerations (Windows 10)
|
||||
description: Discover the Microsoft tools you can use to move files and settings between installations including special considerations for performing an upgrade or migration.
|
||||
title: Windows Upgrade and Migration Considerations
|
||||
description: Discover the Microsoft tools that can be used to move files and settings between installations including special considerations for performing an upgrade or migration.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 08/09/2023
|
||||
ms.date: 08/28/2024
|
||||
---
|
||||
|
||||
# Windows upgrade and migration considerations
|
||||
Files and application settings can be migrated to new hardware running the Windows® operating system, or they can be maintained during an operating system upgrade on the same computer. This topic summarizes the Microsoft® tools you can use to move files and settings between installations in addition to special considerations for performing an upgrade or migration.
|
||||
|
||||
Files and application settings can be migrated to new hardware running the Windows operating system, or they can be maintained during an operating system upgrade on the same computer. This article summarizes the Microsoft tools that can be used to move files and settings between installations in addition to special considerations for performing an upgrade or migration.
|
||||
|
||||
## Upgrade from a previous version of Windows
|
||||
You can upgrade from an earlier version of Windows, which means you can install the new version of Windows and retain your applications, files, and settings as they were in your previous version of Windows. If you decide to perform a custom installation of Windows instead of an upgrade, your applications and settings won't be maintained. Your personal files, and all Windows files and directories, will be moved to a Windows.old folder. You can access your data in the Windows.old folder after Windows Setup is complete.
|
||||
|
||||
Earlier versions of Windows can be upgraded to later versions. As part of the upgrade experience, the newer version of Windows can be installed while retaining applications, files, and settings as they were in the previous version of Windows. If a custom installation of Windows is performed instead of an upgrade, applications and settings aren't maintained. Personal files and all Windows files and directories are moved to a **Windows.old** folder. The data can be accessed in the **Windows.old** folder after Windows Setup is complete.
|
||||
|
||||
## Migrate files and settings
|
||||
Migration tools are available to transfer settings from one computer that is running Windows to another. These tools transfer only the program settings, not the programs themselves.
|
||||
|
||||
For more information about application compatibility, see the [Application Compatibility Toolkit (ACT)](/previous-versions/windows/server/cc722055(v=ws.10)).
|
||||
The [User State Migration Tool (USMT)](../usmt/usmt-overview.md) is available to transfer settings:
|
||||
|
||||
The User State Migration Tool (USMT) 10.0 is an application intended for administrators who are performing large-scale automated deployments. For deployment to a few computers or for individually customized deployments, you can use Windows Easy Transfer.
|
||||
- Between two computers running Windows, also known as a *side-by-side* migration.
|
||||
- On a single computer upgrading the version of Windows when not using an in-place upgrade, also known as a *wipe-and-load* or *refresh* migration.
|
||||
|
||||
### Migrate with Windows Easy Transfer
|
||||
Windows Easy Transfer is a software wizard for transferring files and settings from one computer that is running Windows to another. It helps you select what to move to your new computer, enables you to set which migration method to use, and then performs the transfer. When the transfer has completed, Windows Easy Transfer Reports shows you what was transferred and provides a list of programs you might want to install on your new computer, in addition to links to other programs you might want to download.
|
||||
|
||||
With Windows Easy Transfer, files and settings can be transferred using a network share, a USB flash drive (UFD), or the Easy Transfer cable. However, you can't use a regular universal serial bus (USB) cable to transfer files and settings with Windows Easy Transfer. An Easy Transfer cable can be purchased on the Web, from your computer manufacturer, or at an electronics store.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Windows Easy Transfer [is not available in Windows 10](https://support.microsoft.com/help/4026265/windows-windows-easy-transfer-is-not-available-in-windows-10).
|
||||
USMT only transfers the program settings, not the programs themselves. USMT is an application intended for administrators who are performing large-scale automated deployments, but it can also be used in smaller migrations.
|
||||
|
||||
### Migrate with the User State Migration Tool
|
||||
You can use USMT to automate migration during large deployments of the Windows operating system. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they're migrated. You can use USMT for both *side-by-side* migrations, where one piece of hardware is being replaced, or *wipe-and-load* (or *refresh*) migrations, when only the operating system is being upgraded.
|
||||
|
||||
USMT can be used to automate migration during large deployments of the Windows operating system. USMT uses XML files that define migration rules. The migration rules can be configured to control exactly what USMT migrates and how it migrates the items. For example, USMT can migrate:
|
||||
|
||||
- User accounts, including which specific accounts to migrate.
|
||||
- User files, including which specific files to migrate.
|
||||
- Operating system settings, including which specific operating system settings to migrate.
|
||||
- Settings for some applications, including which specific application settings to migrate.
|
||||
|
||||
USMT can be used for the following scenarios:
|
||||
|
||||
- **Side-by-side** - migration where one device is replaced with a different device.
|
||||
- **Wipe-and-load**/**refresh** - migration where Windows is upgraded on a single device.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> USMT only supports devices that are joined to a local Active Directory domain. USMT doesn't support Microsoft Entra joined devices.
|
||||
|
||||
## Upgrade and migration considerations
|
||||
Whether you're upgrading or migrating to a new version of Windows, you must be aware of the following issues and considerations:
|
||||
|
||||
When upgrading or migrating to a new version of Windows, be aware of the following issues and considerations:
|
||||
|
||||
### Application compatibility
|
||||
For more information about application compatibility in Windows, see [Windows compatibility cookbook](/windows/compatibility/).
|
||||
|
||||
For more information about application compatibility in Windows, see [Compatibility for Windows 11](/windows/compatibility/windows-11/).
|
||||
|
||||
### Multilingual Windows image upgrades
|
||||
When performing multilingual Windows upgrades, cross-language upgrades aren't supported by USMT. If you're upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default user interface (UI) language. For example, if English is the default but you have a Spanish language pack installed, you can upgrade or migrate only to English.
|
||||
|
||||
If you're using a single-language Windows image that matches the system default UI language of your multilingual operating system, the migration will work. However, all of the language packs will be removed, and you'll have to reinstall them after the upgrade is completed.
|
||||
USMT doesn't support cross-language upgrades when performing multilingual Windows upgrades. If upgrading or migrating an operating system with multiple language packs installed, only the system default user interface (UI) language can be upgraded or migrated to. For example, if English is the default but a Spanish language pack is installed, only English can be upgraded or migrated to.
|
||||
|
||||
If a single-language Windows image that matches the system default UI language of a multilingual operating system is being used for a *wipe-and-load*/*refresh* migration, the migration works. However, all of the language packs are removed. The language packs will need to be reinstalled after the upgrade is completed.
|
||||
|
||||
### Errorhandler.cmd
|
||||
When upgrading from an earlier version of Windows, if you intend to use Errorhandler.cmd, you must copy Errorhandler.cmd into the %WINDIR%\\Setup\\Scripts directory on the old installation. This makes sure that if there are errors during the down-level phase of Windows Setup, the commands in Errorhandler.cmd will run.
|
||||
|
||||
### Data drive ACL migration
|
||||
During the configuration pass of Windows Setup, the root access control list (ACL) on drives formatted for NTFS that don't appear to have an operating system will be changed to the default Windows XP ACL format. The ACLs on these drives are changed to enable authenticated users to modify access on folders and files.
|
||||
If using **Errorhandler.cmd** when upgrading from an earlier version of Windows, copy **Errorhandler.cmd** into the `%WINDIR%\Setup\Scripts` directory on the original installation of Windows. Copying **Errorhandler.cmd** into the `%WINDIR%\Setup\Scripts` directory on the original installation of Windows makes sure that if there are errors during the down-level phase of Windows Setup, the commands in **Errorhandler.cmd** run. For more information, see [Run a script if Windows Setup encounters a fatal error (ErrorHandler.cmd)](/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup#run-a-script-if-windowssetup-encounters-a-fatal-error-errorhandlercmd).
|
||||
|
||||
Changing the ACLs may affect the performance of Windows Setup if the default Windows XP ACLs are applied to a partition with a large amount of data. Because of these performance concerns, you can change the following registry value to disable this feature:
|
||||
## Related content
|
||||
|
||||
`Key: HKLM\System\Setup`
|
||||
`Type: REG_DWORD`
|
||||
`Value: "DDACLSys_Disabled" = 1`
|
||||
|
||||
This feature is disabled if this registry key value exists and is configured to `1`.
|
||||
|
||||
## Related articles
|
||||
[User State Migration Tool (USMT) Overview Topics](../usmt/usmt-topics.md)<BR>
|
||||
[Windows 10 upgrade paths](windows-10-upgrade-paths.md)<BR>
|
||||
[Windows 10 edition upgrade](windows-10-edition-upgrades.md)
|
||||
- [User State Migration Tool (USMT) overview](../usmt/usmt-overview.md).
|
||||
- [Windows upgrade paths](windows-upgrade-paths.md).
|
||||
- [Windows edition upgrade](windows-edition-upgrades.md).
|
||||
|
||||
@ -8,7 +8,7 @@ ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 01/09/2024
|
||||
ms.date: 08/28/2024
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
@ -65,7 +65,7 @@ This article outlines the general process to follow to migrate files and setting
|
||||
>
|
||||
> USMT fails if it can't migrate a file or setting unless the `/c` option is specified. When the `/c` option is specified, USMT ignores the errors, and logs an error every time that it encounters a file that is being used that USMT didn't migrate. The `<ErrorControl>` section in the `Config.xml` file can be used to specify which errors should be ignored, and which should cause the migration to fail.
|
||||
|
||||
1. Run the `ScanState.exe` command on the source computer to collect files and settings. All of the **.xml** files that the `ScanState.exe` command needs to use should be specified. For example,
|
||||
1. To collect files and settings, run the `ScanState.exe` command on the source computer. All of the **.xml** files that the `ScanState.exe` command needs to use should be specified. For example,
|
||||
|
||||
```cmd
|
||||
ScanState.exe \\server\migration\mystore /config:Config.xml /i:MigDocs.xml /i:MigApp.xml /v:13 /l:ScanState.log
|
||||
@ -75,7 +75,7 @@ This article outlines the general process to follow to migrate files and setting
|
||||
>
|
||||
> The `ScanState.exe` command must be run in **Administrator** mode on the source computer. To run in **Administrator** mode, right-click **Command Prompt**, and then select **Run As Administrator**. For more information about how the `ScanState.exe` command processes and stores the data, see [How USMT Works](usmt-how-it-works.md).
|
||||
|
||||
1. Run the `UsmtUtils.exe` command with the `/Verify` option to ensure that the created store isn't corrupted.
|
||||
1. To ensure that the created store isn't corrupted, run the `UsmtUtils.exe` command with the `/Verify` option.
|
||||
|
||||
## Step 3: Prepare the destination computer and restore files and settings
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 01/09/2024
|
||||
ms.date: 08/28/2024
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
@ -28,13 +28,13 @@ A test computer that contains the operating system of the source computers shoul
|
||||
|
||||
## Step 1: Verify that the application is installed on the source computer, and that it's the same version as the version to be installed on the destination computer
|
||||
|
||||
Before USMT migrates the settings, check whether the application is installed on the source computer, and that it's the correct version. If the application isn't installed on the source computer, USMT still spends time searching for the application's settings. More importantly, if USMT collects settings for an application that isn't installed, it could migrate settings that cause the destination computer to function incorrectly. Also determine whether there's more than one version of the application because the new version could store the settings in a different location. Mismatched application versions could lead to unexpected results on the destination computer.
|
||||
Before USMT migrates the settings, check whether the application is installed on the source computer, and that it's the correct version. If the application isn't installed on the source computer, USMT still spends time searching for the application's settings. More importantly, if USMT collects settings for an application that isn't installed, it could migrate settings that cause the destination computer to function incorrectly. Also determine whether there's more than one version of the application because the new version could store the settings in a different location. Mismatched application versions could lead to unexpected results on the destination computer.
|
||||
|
||||
There are many ways to detect if an application is installed. The best practice is to check for an application uninstall key in the registry, and then search the computer for the executable file that installed the application. It's important to check for both of these items, because sometimes different versions of the same application share the same uninstall key. Even if the key is there, it could correspond to a different version of the application that is wanted.
|
||||
There are many ways to detect if an application is installed. The best practice is to check for an application uninstall key in the registry. The computer can then be searched for the executable file that installed the application. It's important to check for both of these items, because sometimes different versions of the same application share the same uninstall key. Even if the key is there, it could correspond to a different version of the application that is wanted.
|
||||
|
||||
### Check the registry for an application uninstall key
|
||||
|
||||
When many applications are installed (especially those installed using the Microsoft Windows Installer technology), an application uninstall key is created under:
|
||||
When many applications are installed, especially those installed using the Microsoft Windows Installer technology, an application uninstall key is created under:
|
||||
|
||||
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall`
|
||||
|
||||
@ -44,11 +44,17 @@ For example, when Adobe Acrobat Reader 7 is installed, it creates a key named:
|
||||
|
||||
Therefore, if a computer contains this key, then Adobe Acrobat Reader 7 is installed on the computer. The existence of a registry key can be checked using the `DoesObjectExist` helper function.
|
||||
|
||||
Usually, this key can be found by searching under:
|
||||
The **Uninstall** registry key for a particular application can be found under the following registry key:
|
||||
|
||||
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall`
|
||||
|
||||
for the name of the application, the name of the application executable file, or for the name of the company that makes the application. The Registry Editor, `Regedit.exe` located in the `%SystemRoot%`, can be used to search the registry.
|
||||
To find the **Uninstall** key for a specific application, search for one of the following items under the **Uninstall** registry key:
|
||||
|
||||
- Name of the application.
|
||||
- Name of the application executable file.
|
||||
- Name of the company that makes the application.
|
||||
|
||||
To search the registry, use the Registry Editor `Regedit.exe`. `Regedit.exe` is located in the path stored in `%SystemRoot%`, normally `C:\Windows`.
|
||||
|
||||
### Check the file system for the application executable file
|
||||
|
||||
@ -76,7 +82,7 @@ Next, go through the user interface and make a list of all of the available sett
|
||||
>
|
||||
> Most applications store their settings under the user profile. That is, the settings stored in the file system are under the `%UserProfile%` directory, and the settings stored in the registry are under the `HKEY_CURRENT_USER` hive. For these applications, the output of the file and registry monitoring tools can be filtered to show activity only under these locations. This filtering considerably reduces the amount of output that needs to be examined.
|
||||
|
||||
1. Start the monitoring tool(s), change a setting, and look for registry and file system writes that occurred when the setting was changed. Make sure the changes made actually take effect. For example, if changing a setting in Microsoft Word by selecting a check box in the **Options** dialog box, the change typically doesn't take effect until the dialog box is closed by selecting **OK**.
|
||||
1. Start the monitoring tools, change a setting, and look for registry and file system writes that occurred when the setting was changed. Make sure the changes made actually take effect. For example, if changing a setting in Microsoft Word by selecting a check box in the **Options** dialog box, the change typically doesn't take effect until the dialog box is closed by selecting **OK**.
|
||||
|
||||
1. When the setting is changed, note the changes to the file system and registry. There could be more than one file or registry values for each setting. The minimal set of file and registry changes that are required to change this setting should be identified. This set of files and registry keys is what needs to be migrated in order to migrate the setting.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows 10 deployment scenarios and tools
|
||||
description: Learn about the tools you can use to deploy Windows 10 and related applications to your organization. Explore deployment scenarios.
|
||||
title: Windows deployment scenarios and tools
|
||||
description: Learn about the tools that can be used to deploy Windows and related applications to your organization. Explore deployment scenarios.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
author: frankroj
|
||||
@ -10,68 +10,71 @@ ms.date: 11/23/2022
|
||||
ms.subservice: itpro-deploy
|
||||
---
|
||||
|
||||
# Windows 10 deployment scenarios and tools
|
||||
# Windows deployment scenarios and tools
|
||||
|
||||
To successfully deploy the Windows 10 operating system and applications for your organization, understand the available tools to help with the process. In this article, you'll learn about the most commonly used tools for Windows 10 deployment.
|
||||
To successfully deploy the Windows operating system and applications for your organization, it's important to understand the available tools to help with the process. This article covers the most commonly used tools for Windows 10 deployment.
|
||||
|
||||
Microsoft provides many tools, services, and solutions. These tools include Windows Deployment Services (WDS), the Volume Activation Management Tool (VAMT), the User State Migration Tool (USMT), Windows System Image Manager (Windows SIM), Windows Preinstallation Environment (Windows PE), and Windows Recovery Environment (Windows RE). These tools aren't a complete solution on their own. Combine these tools with solutions like [Configuration Manager](deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md) to get a complete deployment solution.
|
||||
|
||||
In this article, you also learn about different types of reference images that you can build, and why reference images are beneficial for most organizations
|
||||
This article also covers the different types of reference images that can be built, and why reference images are beneficial for most organizations.
|
||||
|
||||
## Windows Assessment and Deployment Kit
|
||||
|
||||
Windows ADK contains core assessment and deployment tools and technologies, including Deployment Image Servicing and Management (DISM), Windows Imaging and Configuration Designer (Windows ICD), Windows System Image Manager (Windows SIM), User State Migration Tool (USMT), Volume Activation Management Tool (VAMT), Windows Preinstallation Environment (Windows PE), Windows Assessment Services, Windows Performance Toolkit (WPT), Application Compatibility Toolkit (ACT), and Microsoft SQL Server 2012 Express. For more information, see [Windows ADK for Windows 10](/windows-hardware/get-started/adk-install) or [Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md).
|
||||
Windows ADK contains core assessment and deployment tools and technologies, including:
|
||||
|
||||
|
||||
- [Deployment Image Servicing and Management (DISM)](/windows-hardware/manufacture/desktop/dism---deployment-image-servicing-and-management-technical-reference-for-windows).
|
||||
- [Windows Configuration Designer](/windows/configuration/provisioning-packages/provisioning-packages).
|
||||
- [Windows System Image Manager (Windows SIM)](/windows-hardware/customize/desktop/wsim/windows-system-image-manager-technical-reference).
|
||||
- [User State Migration Tool (USMT)](/windows/deployment/usmt/usmt-overview).
|
||||
- [Volume Activation Management Tool (VAMT)](/windows/deployment/volume-activation/volume-activation-management-tool).
|
||||
- [Windows Preinstallation Environment (Windows PE)](/windows-hardware/manufacture/desktop/winpe-intro).
|
||||
- [Windows Assessment Toolkit](/windows-hardware/test/assessments/).
|
||||
- [Windows Performance Toolkit (WPT)](/windows-hardware/test/wpt/).
|
||||
|
||||
The Windows 10 ADK feature selection page.
|
||||
For more information, see the following articles:
|
||||
|
||||
- [Download and install the Windows ADK](/windows-hardware/get-started/adk-install).
|
||||
- [Windows ADK for Windows scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md).
|
||||
- [Kits and tools overview](/windows-hardware/get-started/kits-and-tools-overview).
|
||||
|
||||
### Deployment Image Servicing and Management (DISM)
|
||||
|
||||
DISM is one of the deployment tools included in the Windows ADK and is used for capturing, servicing, and deploying boot images and operating system images.
|
||||
DISM is one of the deployment tools included in the Windows ADK. It's used for capturing, servicing, and deploying both boot images and operating system images.
|
||||
|
||||
DISM services online and offline images. For example, with DISM you can install the Microsoft .NET Framework 3.5.1 in Windows 10 online, which means that you can start the installation in the running operating system, not that you get the software online. The /LimitAccess switch configures DISM to get the files only from a local source:
|
||||
DISM services online and offline images. For example, with DISM you can install the Microsoft .NET Framework while Windows is online, which means that you can start the installation in the running operating system. The `/LimitAccess` switch configures DISM to get the files only from a local source. For example:
|
||||
|
||||
```cmd
|
||||
Dism.exe /Online /Enable-Feature /FeatureName:NetFX3 /All /Source:D:\Sources\SxS /LimitAccess
|
||||
```
|
||||
|
||||
In Windows 10, you can use Windows PowerShell for many of the functions done by DISM.exe. The equivalent command in Windows 10 using PowerShell is:
|
||||
In Windows you can use Windows PowerShell for many of the functions done by DISM.exe. The equivalent command in Windows using PowerShell is:
|
||||
|
||||
```powershell
|
||||
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -All
|
||||
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -All
|
||||
-Source D:\Sources\SxS -LimitAccess
|
||||
```
|
||||
|
||||
|
||||
|
||||
Using DISM functions in PowerShell.
|
||||
|
||||
For more information on DISM, see [DISM technical reference](/windows-hardware/manufacture/desktop/dism---deployment-image-servicing-and-management-technical-reference-for-windows).
|
||||
|
||||
### User State Migration Tool (USMT)
|
||||
|
||||
USMT is a backup and restore tool that allows you to migrate user state, data, and settings from one installation to another. Microsoft Deployment Toolkit (MDT) and Configuration Manager use USMT as part of the operating system deployment process.
|
||||
USMT is a backup and restore tool that allows you to migrate user state, data, and settings from one installation to another. Microsoft Configuration Manager uses USMT as part of the operating system deployment process.
|
||||
|
||||
USMT includes several command-line tools, the most important of which are ScanState and LoadState:
|
||||
USMT includes several command-line tools, the most important of which are **ScanState** and **LoadState**:
|
||||
|
||||
- **ScanState.exe**: This tool performs the user-state backup.
|
||||
- **LoadState.exe**: This tool performs the user-state restore.
|
||||
- **UsmtUtils.exe**: This tool supplements the functionality in ScanState.exe and LoadState.exe.
|
||||
- **UsmtUtils.exe**: This tool supplements the functionality in **ScanState.exe** and **LoadState.exe**.
|
||||
|
||||
In addition to these tools, there are also XML templates that manage which data is migrated. You can customize the templates, or create new ones, to manage the backup process at a high level of detail. USMT uses the following terms for its templates:
|
||||
|
||||
- **Migration templates**: The default templates in USMT.
|
||||
- **Custom templates**: Custom templates that you create.
|
||||
- **Config template**: An optional template called Config.xml which you can use to exclude or include components in a migration without modifying the other standard XML templates.
|
||||
- **Config template**: An optional template called **Config.xml** which you can use to exclude or include components in a migration without modifying the other standard XML templates.
|
||||
|
||||
|
||||
USMT supports capturing and restoring both data and settings from currently supported versions of Windows. It also supports migrating from a 32-bit operating system to a 64-bit operating system, but not the other way around. For example, you can use USMT to migrate from Windows 10 x86 to Windows 11 x64.
|
||||
|
||||
A sample USMT migration file that will exclude .MP3 files on all local drives and include the folder C:\\Data and all its files, including its subdirectories and their files.
|
||||
|
||||
USMT supports capturing data and settings from Windows Vista and later, and restoring the data and settings to Windows 7 and later (including Windows 10 in both cases). It also supports migrating from a 32-bit operating system to a 64-bit operating system, but not the other way around. For example, you can use USMT to migrate from Windows 7 x86 to Windows 10 x64.
|
||||
|
||||
By default USMT migrates many settings, most of which are related to the user profile but also to Control Panel configurations, file types, and more. The default templates that are used in Windows 10 deployments are MigUser.xml and MigApp.xml. These two default templates migrate the following data and settings:
|
||||
By default USMT migrates many settings, most of which are related to the user profile but also to Control Panel configurations, file types, and more. The default templates that are used in Windows deployments are **MigUser.xml** and **MigApp.xml**. These two default templates migrate the following data and settings:
|
||||
|
||||
- Folders from each profile, including those folders from user profiles, and shared and public profiles. For example, the My Documents, My Video, My Music, My Pictures, desktop files, Start menu, Quick Launch settings, and Favorites folders are migrated.
|
||||
|
||||
@ -83,55 +86,46 @@ By default USMT migrates many settings, most of which are related to the user pr
|
||||
> The asterisk (`*`) stands for zero or more characters.
|
||||
|
||||
> [!NOTE]
|
||||
> The OpenDocument extensions (`*.odt`, `*.odp`, `*.ods`) that Microsoft Office applications can use aren't migrated by default.
|
||||
> The OpenDocument extensions (`*.odt`, `*.odp`, `*.ods`) used by Microsoft Office applications aren't migrated by default.
|
||||
|
||||
- Operating system component settings
|
||||
- Operating system component settings.
|
||||
|
||||
- Application settings
|
||||
- Application settings.
|
||||
|
||||
These settings are migrated by the default MigUser.xml and MigApp.xml templates. For more information, see [What does USMT migrate?](./usmt/usmt-what-does-usmt-migrate.md) For more general information on USMT, see [USMT technical reference](./usmt/usmt-reference.md).
|
||||
These settings are migrated by the default **MigUser.xml** and **MigApp.xml** templates. For more information, see [What does USMT migrate?](./usmt/usmt-what-does-usmt-migrate.md) For more general information on USMT, see [User State Migration Tool (USMT) overview](./usmt/usmt-overview.md).
|
||||
|
||||
### Windows Imaging and Configuration Designer
|
||||
### Windows Configuration Designer
|
||||
|
||||
Windows Imaging and Configuration Designer (Windows ICD) is a tool designed to assist with the creation of provisioning packages that can be used to dynamically configure a Windows device (PCs, tablets, and phones). This tool is useful for setting up new devices, without the need for reimaging the device with a custom image.
|
||||
Windows Configuration Designer is a tool designed to assist with the creation of provisioning packages that can be used to dynamically configure a Windows device. This tool is useful for setting up new devices without the need for reimaging the device with a custom image.
|
||||
|
||||
|
||||
|
||||
Windows Imaging and Configuration Designer.
|
||||
|
||||
For more information, see [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd).
|
||||
For more information, see [Provisioning packages for Windows](/windows/configuration/provisioning-packages/provisioning-packages).
|
||||
|
||||
### Windows System Image Manager (Windows SIM)
|
||||
|
||||
Windows SIM is an authoring tool for Unattend.xml files. When using MDT and/or Configuration Manager, you don't need Windows SIM often because those systems automatically update the Unattend.xml file during the deployment, greatly simplifying the process overall.
|
||||
|
||||
|
||||
|
||||
Windows answer file opened in Windows SIM.
|
||||
|
||||
For more information, see [Windows System Image Manager Technical Reference]( https://go.microsoft.com/fwlink/p/?LinkId=619906).
|
||||
For more information, see [Windows System Image Manager Technical Reference](/windows-hardware/customize/desktop/wsim/windows-system-image-manager-technical-reference).
|
||||
|
||||
### Volume Activation Management Tool (VAMT)
|
||||
|
||||
If you don't use KMS, manage your MAKs centrally with the Volume Activation Management Tool (VAMT). Use this tool to install and manage product keys throughout the organization. VAMT can also activate on behalf of clients without internet access, acting as a MAK proxy.
|
||||
If not using [Key Management Services (KMS)](/windows-server/get-started/kms-client-activation-keys), Multiple Activation Keys (MAKs) can be centrally managed with the Volume Activation Management Tool (VAMT). Use this tool to install and manage product keys throughout the organization. VAMT can also activate on behalf of clients without internet access, acting as a MAK proxy.
|
||||
|
||||
|
||||
|
||||
The updated Volume Activation Management Tool.
|
||||
|
||||
VAMT also can be used to create reports, switch from MAK to KMS, manage Active Directory-based activation, and manage Office 2010 and Office 2013 volume activation. VAMT also supports PowerShell (instead of the old command-line tool). For example, if you want to get information from the VAMT database, you can type:
|
||||
VAMT also can be used to create reports, switch from MAK to KMS, manage Active Directory-based activation, and manage Office volume activation. VAMT also supports PowerShell. For example, to get information from the VAMT database, enter:
|
||||
|
||||
```powershell
|
||||
Get-VamtProduct
|
||||
```
|
||||
|
||||
For more information on the VAMT, see [VAMT technical reference](./volume-activation/volume-activation-management-tool.md).
|
||||
For more information on the VAMT, see the following articles:
|
||||
|
||||
- [Volume Activation Management Tool (VAMT)](/windows/deployment/volume-activation/volume-activation-management-tool).
|
||||
- [VAMT technical reference](./volume-activation/volume-activation-management-tool.md).
|
||||
|
||||
### Windows Preinstallation Environment (Windows PE)
|
||||
|
||||
Windows PE is a "Lite" version of Windows 10 and was created to act as a deployment platform. Windows PE replaces the DOS or Linux boot disks that ruled the deployment solutions of the last decade.
|
||||
Windows PE is a "lite" version of Windows used as a deployment platform.
|
||||
|
||||
The key thing to know about Windows PE is that, like the operating system, it needs drivers for at least network and storage devices in each PC. Luckily Windows PE includes the same drivers as the full Windows 10 operating system, which means much of your hardware will work out of the box.
|
||||
Windows PE is like any other operating system and it needs drivers. However, it doesn't need a full set of drivers. It only needs the drivers to deploy Windows. Normally this is just network and storage drivers. Luckily Windows PE includes the same drivers as the full Windows 10 operating system, which means much of your hardware will work out of the box.
|
||||
|
||||
|
||||
|
||||
@ -179,7 +173,7 @@ MDT is a free deployment solution from Microsoft. It provides end-to-end guidanc
|
||||
|
||||
MDT has two main parts: the first is Lite Touch, which is a stand-alone deployment solution; the second is Zero Touch, which is an extension to Configuration Manager.
|
||||
|
||||
**Note**
|
||||
**Note**
|
||||
Lite Touch and Zero Touch are marketing names for the two solutions that MDT supports, and the naming has nothing to do with automation. You can fully automate the stand-alone MDT solution (Lite Touch), and you can configure the solution integration with Configuration Manager to prompt for information.
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user