mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Updated-6038482
Articles updated to resolve Warning and address Acrolinx errors.
This commit is contained in:
Jitin Mathew
parent
31f83a8b38
commit
de1733184a
@ -17,12 +17,12 @@ ms.topic: article
|
||||
|
||||
This topic will show you how to use MDT Lite Touch Installation (LTI) to upgrade a Windows 7 computer to a Windows 10 computer using the online computer refresh process. The computer refresh scenario is a reinstallation of an updated operating system on the same computer. You can also use this procedure to reinstall the same OS version. In this article, the computer refresh will be done while the computer is online. MDT also supports an offline computer refresh. For more info on that scenario, see the USMTOfflineMigration property on the [MDT resource page](/mem/configmgr/mdt/).
|
||||
|
||||
For the purposes of this topic, we will use three computers: DC01, MDT01, and PC0001.
|
||||
For the purposes of this topic, we'll use three computers: DC01, MDT01, and PC0001.
|
||||
- DC01 is a domain controller for the contoso.com domain.
|
||||
- MDT01 is domain member server that hosts your deployment share.
|
||||
- PC0001 is a domain member computer running a previous version of Windows that is going to be refreshed to a new version of Windows 10, with data and settings restored. The example used here is a computer running Windows 7 SP1.
|
||||
|
||||
Both DC01 and MDT01 are running Windows Server 2019; however any supported version of Windows Server can be used. For more details on the setup for this topic, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
Both DC01 and MDT01 are running Windows Server 2019; however any supported version of Windows Server can be used. For more details on the setup for this topic, see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
|
||||
|
||||
@ -30,9 +30,9 @@ The computers used in this topic.
|
||||
|
||||
## The computer refresh process
|
||||
|
||||
A computer refresh is not the same as an in-place upgrade because a computer refresh involves exporting user data and settings then wiping the device before installing a fresh OS and restoring the user's data and settings.
|
||||
A computer refresh isn't the same as an in-place upgrade because a computer refresh involves exporting user data and settings then wiping the device before installing a fresh OS and restoring the user's data and settings.
|
||||
|
||||
For a computer refresh with MDT, you use the User State Migration Tool (USMT), which is part of the Windows Assessment and Deployment Kit (ADK) for Windows 10, to migrate user data and settings. To complete a computer refresh you will:
|
||||
For a computer refresh with MDT, you use the User State Migration Tool (USMT), which is part of the Windows Assessment and Deployment Kit (ADK) for Windows 10, to migrate user data and settings. To complete a computer refresh, you will:
|
||||
|
||||
1. Back up data and settings locally, in a backup folder.
|
||||
2. Wipe the partition, except for the backup folder.
|
||||
@ -40,7 +40,7 @@ For a computer refresh with MDT, you use the User State Migration Tool (USMT), w
|
||||
4. Install other applications.
|
||||
5. Restore data and settings.
|
||||
|
||||
During the computer refresh, USMT uses a feature called Hard-Link Migration Store. When you use this feature, the files are simply linked in the file system, which allows for fast migration, even when there is a lot of data.
|
||||
During the computer refresh, USMT uses a feature called Hard-Link Migration Store. When you use this feature, the files are linked in the file system, which allows for fast migration, even when there's a lot of data.
|
||||
|
||||
>[!NOTE]
|
||||
>In addition to the USMT backup, you can enable an optional full Windows Imaging (WIM) backup of the machine by configuring the MDT rules. If you do this, a .wim file is created in addition to the USMT backup. The .wim file contains the entire volume from the computer and helpdesk personnel can extract content from it if needed. Please note that this is a data WIM backup only. Using this backup to restore the entire computer is not a supported scenario.
|
||||
@ -60,17 +60,17 @@ In addition to the command-line switches that control which profiles to migrate,
|
||||
|
||||
### Multicast
|
||||
|
||||
Multicast is a technology designed to optimize simultaneous deployment to multiple devices. If you have a limited number of simultaneous deployments, you should disable multicast which was [configured in a previous procedure](deploy-a-windows-10-image-using-mdt.md#set-up-mdt-for-multicast) in this guide. Disabling multicast will speed up deployment for a small number of computers. You will need to update the deployment share after changing this setting.
|
||||
Multicast is a technology designed to optimize simultaneous deployment to multiple devices. If you have a limited number of simultaneous deployments, you should disable multicast which was [configured in a previous procedure](deploy-a-windows-10-image-using-mdt.md#set-up-mdt-for-multicast) in this guide. Disabling multicast will speed up deployment for a small number of computers. You'll need to update the deployment share after changing this setting.
|
||||
|
||||
## Refresh a Windows 7 SP1 client
|
||||
|
||||
In these section, we assume that you have already performed the prerequisite procedures in the following topics, so that you have a deployment share named **MDTProduction$** on MDT01:
|
||||
In this section, we assume that you've already performed the prerequisite procedures in the following topics, so that you have a deployment share named **MDTProduction$** on MDT01:
|
||||
|
||||
- [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md)
|
||||
- [Create a Windows 10 reference image](create-a-windows-10-reference-image.md)
|
||||
- [Deploy a Windows 10 image using MDT](deploy-a-windows-10-image-using-mdt.md)
|
||||
|
||||
It is also assumed that you have a domain member client computer named PC0001 in your environment running Windows 7, 8.1 or 10 that is ready for a refresh to the latest version of Windows 10. For demonstration purposes, we will refreshing a Windows 7 SP1 PC to Windows 10, version 1909.
|
||||
It is also assumed that you have a domain member client computer named PC0001 in your environment running Windows 7, 8.1 or 10 that is ready for a refresh to the latest version of Windows 10. For demonstration purposes, we'll be refreshing a Windows 7 SP1 PC to Windows 10, version 1909.
|
||||
|
||||
### Upgrade (refresh) a Windows 7 SP1 client
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Replace a Windows 7 computer with a Windows 10 computer (Windows 10)
|
||||
description: In this article, you will learn how to replace a Windows 7 device with a Windows 10 device.
|
||||
description: In this article, you'll learn how to replace a Windows 7 device with a Windows 10 device.
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
@ -16,15 +16,15 @@ ms.topic: article
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
A computer replace scenario for Windows 10 is quite similar to a computer refresh for Windows 10. However, because you are replacing a device, you cannot store the backup on the old computer. Instead you need to store the backup to a location where the new computer can read it. The User State Migration Tool (USMT) will be used to back up and restore data and settings.
|
||||
A computer replace scenario for Windows 10 is similar to a computer refresh for Windows 10. However, because you're replacing a device, you can't store the backup on the old computer. Instead you need to store the backup to a location where the new computer can read it. The User State Migration Tool (USMT) will be used to back up and restore data and settings.
|
||||
|
||||
For the purposes of this topic, we will use four computers: DC01, MDT01, PC0002, and PC0007.
|
||||
For the purposes of this topic, we'll use four computers: DC01, MDT01, PC0002, and PC0007.
|
||||
- DC01 is a domain controller for the contoso.com domain.
|
||||
- MDT01 is domain member server that hosts your deployment share.
|
||||
- PC0002 is an old computer running Windows 7 SP1 that will be replaced by PC0007.
|
||||
- PC0007 is a new computer will have the Windows 10 OS installed prior to data from PC0002 being migrated. Both PC0002 and PC0007 are members of the contoso.com domain.
|
||||
|
||||
For more details on the setup for this topic, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
For more details on the setup for this topic, see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
|
||||
|
||||
@ -40,9 +40,9 @@ The computers used in this topic.
|
||||
|
||||
On **MDT01**:
|
||||
|
||||
1. Open the Deployment Workbench, under **Deployment Shares** right-click **MDT Production**, click **Properties**, and then click the **Rules** tab.
|
||||
2. Change the **SkipUserData=YES** option to **NO**, and click **OK**.
|
||||
3. Right-click **MDT Production** and click **Update Deployment Share**. Click **Next**, **Next**, and **Finish** to complete the Update Deployment Share Wizard with the default settings.
|
||||
1. Open the Deployment Workbench, under **Deployment Shares** right-click **MDT Production**, select **Properties**, and then select the **Rules** tab.
|
||||
2. Change the **SkipUserData=YES** option to **NO**, and select **OK**.
|
||||
3. Right-click on **MDT Production** and select **Update Deployment Share**. Then select **Next**, **Next**, and **Finish** to complete the Update Deployment Share Wizard with the default settings.
|
||||
|
||||
### Create and share the MigData folder
|
||||
|
||||
@ -75,7 +75,7 @@ On **MDT01**:
|
||||
|
||||
During a computer replace, these are the high-level steps that occur:
|
||||
|
||||
1. On the computer you are replacing, a special replace task sequence runs the USMT backup and, if you configured it, runs the optional full Windows Imaging (WIM) backup.
|
||||
1. On the computer you're replacing, a special replace task sequence runs the USMT backup and, if you configured it, runs the optional full Windows Imaging (WIM) backup.
|
||||
2. On the new computer, you perform a standard bare-metal deployment. At the end of the bare-metal deployment, the USMT backup from the old computer is restored.
|
||||
|
||||
### Run the replace task sequence
|
||||
|
||||
@ -3,6 +3,7 @@ title: Optimize Windows update delivery
|
||||
description: Two methods of peer-to-peer content distribution are available, Delivery Optimization and BranchCache.
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
author: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user