mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 05:47:23 +00:00
draft
This commit is contained in:
Greg Lindsay
parent
552689efe6
commit
6d301a30f5
@ -23,13 +23,13 @@ ms.topic: article
|
||||
|
||||
In this topic, you will learn how to replicate your Windows 10 deployment shares to facilitate the deployment of Windows 10 in remote or branch locations. If you work in a distributed environment, replicating the deployment shares is an important part of the deployment solution. With images reaching 5 GB in size or more, you can't deploy machines in a remote office over the wire. You need to replicate the content, so that the clients can do local deployments.
|
||||
|
||||
We will use four machines for this topic: DC01, MDT01, MDT02, and PC0006. DC01 is a domain controller, MDT01 is a Windows Server 2012 R2 standard server, and PC0006 is a blank machine to which you will deploy Windows 10. You will configure a second deployment server (MDT02) for a remote site (Stockholm) by replicating the deployment share in the original site (New York). MDT01, MDT02, and PC0006 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md#proof).
|
||||
We will use four machines for this topic: DC01, MDT01, MDT02, and PC0006. DC01 is a domain controller, MDT01 is a Windows Server 2012 R2 standard server, and PC0006 is a blank machine to which you will deploy Windows 10. You will configure a second deployment server (MDT02) for a remote site (Stockholm) by replicating the deployment share in the original site (New York). MDT01, MDT02, and PC0006 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
|
||||
|
||||
Figure 1. The machines used in this topic.
|
||||
Computers used in this topic.
|
||||
|
||||
## <a href="" id="sec01"></a>Replicate deployment shares
|
||||
## Replicate deployment shares
|
||||
|
||||
Replicating the content between MDT01 (New York) and MDT02 (Stockholm) can be done in a number of different ways. The most common content replication solutions with Microsoft Deployment Toolkit (MDT) use either the Linked Deployment Shares (LDS) feature or Distributed File System Replication (DFS-R). Some organizations have used a simple robocopy script for replication of the content.
|
||||
|
||||
@ -44,7 +44,7 @@ LDS is a built-in feature in MDT for replicating content. However, LDS works bes
|
||||
|
||||
DFS-R is not only very fast and reliable, but it also offers central monitoring, bandwidth control, and a great delta replication engine. DFS-R will work equally well whether you have 2 sites or 90. When using DFS-R for MDT, we recommend running your deployment servers on Windows Server 2008 R2 or higher. From that version on, you can configure the replication target(s) as read-only, which is exactly what you want for MDT. This way, you can have your master deployment share centralized and replicate out changes as they happen. DFS-R will quickly pick up changes at the central deployment share in MDT01 and replicate the delta changes to MDT02.
|
||||
|
||||
## <a href="" id="sec02"></a>Set up Distributed File System Replication (DFS-R) for replication
|
||||
## Set up Distributed File System Replication (DFS-R) for replication
|
||||
|
||||
Setting up DFS-R for replication is a quick and straightforward process. You prepare the deployment servers and then create a replication group. To complete the setup, you configure some replication settings.
|
||||
|
||||
@ -57,7 +57,7 @@ Setting up DFS-R for replication is a quick and straightforward process. You pre
|
||||
|
||||
|
||||
|
||||
Figure 2. Adding the DFS Replication role to MDT01.
|
||||
Adding the DFS Replication role to MDT01.
|
||||
|
||||
6. On the **Select features** page, accept the default settings, and click **Next**.
|
||||
7. On the **Confirm installation selections** page, click **Install**.
|
||||
@ -81,7 +81,7 @@ Setting up DFS-R for replication is a quick and straightforward process. You pre
|
||||
|
||||
|
||||
|
||||
Figure 3. Sharing the **E:\\MDTProduction folder** on MDT02.
|
||||
Sharing the **E:\\MDTProduction folder** on MDT02.
|
||||
|
||||
### Configure the deployment share
|
||||
|
||||
@ -103,22 +103,21 @@ When you have multiple deployment servers sharing the same content, you need to
|
||||
UserID=MDT_BA
|
||||
SkipBDDWelcome=YES
|
||||
```
|
||||
**Note**
|
||||
The DeployRoot value needs to go into the Bootstrap.ini file, but you can use the same logic in the CustomSettings.ini file. For example, you can redirect the logs to the local deployment server (SLSHARE), or have the User State Migration Tool (USMT) migration store (UDDIR) local. To learn more about USMT, see [Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md) and [Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md).
|
||||
**Note**: The DeployRoot value needs to go into the Bootstrap.ini file, but you can use the same logic in the CustomSettings.ini file. For example, you can redirect the logs to the local deployment server (SLSHARE), or have the User State Migration Tool (USMT) migration store (UDDIR) local. To learn more about USMT, see [Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md) and [Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md).
|
||||
|
||||
2. Save the Bootstrap.ini file.
|
||||
3. Using the Deployment Workbench, right-click the **MDT Production** deployment share and select **Update Deployment Share**.
|
||||
|
||||
|
||||
|
||||
Figure 4. Updating the MDT Production deployment share.
|
||||
Updating the MDT Production deployment share.
|
||||
|
||||
4. Use the default settings for the Update Deployment Share Wizard.
|
||||
5. After the update is complete, use the Windows Deployment Services console. In the **Boot Images** node, right-click the **MDT Production x64** boot image and select **Replace Image**.
|
||||
|
||||
|
||||
|
||||
Figure 5. Replacing the updated boot image in WDS.
|
||||
Replacing the updated boot image in WDS.
|
||||
|
||||
6. Browse and select the **E:\\MDTProduction\\Boot\\LiteTouchPE\_x64.wim** boot image, and then complete Replace Boot Image Wizard using the default settings.
|
||||
## <a href="" id="sec03"></a>Replicate the content
|
||||
@ -131,7 +130,7 @@ When you have multiple deployment servers sharing the same content, you need to
|
||||
|
||||
|
||||
|
||||
Figure 6. Adding the Replication Group Members.
|
||||
Adding the Replication Group Members.
|
||||
|
||||
11. On the **Topology Selection** page, select the **Full mesh** option and click **Next**.
|
||||
12. On the **Replication Group Schedule and Bandwidth** page, accept the default settings and click **Next**.
|
||||
@ -142,7 +141,7 @@ When you have multiple deployment servers sharing the same content, you need to
|
||||
|
||||
|
||||
|
||||
Figure 7. Configure the MDT02 member.
|
||||
Configure the MDT02 member.
|
||||
|
||||
17. On the **Review Settings and Create Replication Group** page, click **Create**.
|
||||
18. On the **Confirmation** page, click **Close**.
|
||||
@ -160,7 +159,7 @@ When you have multiple deployment servers sharing the same content, you need to
|
||||
|
||||
|
||||
|
||||
Figure 8. Configure the Staging settings.
|
||||
Configure the Staging settings.
|
||||
|
||||
22. In the middle pane, right-click the **MDT02** member and select **Properties**.
|
||||
23. On the **MDT02 (MDTProduction) Properties** page, configure the following and then click **OK**:
|
||||
@ -182,15 +181,15 @@ It will take some time for the replication configuration to be picked up by the
|
||||
|
||||
|
||||
|
||||
Figure 9. The DFS Replication Health Report.
|
||||
The DFS Replication Health Report.
|
||||
|
||||
## <a href="" id="sec04"></a>Configure Windows Deployment Services (WDS) in a remote site
|
||||
## Configure Windows Deployment Services (WDS) in a remote site
|
||||
|
||||
Like you did in the previous topic for MDT01, you need to add the MDT Production Lite Touch x64 Boot image to Windows Deployment Services on MDT02. For the following steps, we assume that WDS has already been installed on MDT02.
|
||||
1. On MDT02, using the WDS console, right-click **Boot Images** and select **Add Boot Image**.
|
||||
2. Browse to the E:\\MDTProduction\\Boot\\LiteTouchPE\_x64.wim file and add the image with the default settings.
|
||||
|
||||
## <a href="" id="sec05"></a>Deploy the Windows 10 client to the remote site
|
||||
## Deploy the Windows 10 client to the remote site
|
||||
|
||||
Now you should have a solution ready for deploying the Windows 10 client to the remote site, Stockholm, connecting to the MDT Production deployment share replica on MDT02.
|
||||
|
||||
@ -214,16 +213,9 @@ Now you should have a solution ready for deploying the Windows 10 client to the
|
||||
|
||||
## Related topics
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.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)
|
||||
|
||||
[Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)
|
||||
|
||||
[Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md)
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)<br>
|
||||
[Create a Windows 10 reference image](create-a-windows-10-reference-image.md)<br>
|
||||
[Deploy a Windows 10 image using MDT](deploy-a-windows-10-image-using-mdt.md)<br>
|
||||
[Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)<br>
|
||||
[Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md)<br>
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
|
||||
|
||||
|
||||
@ -11,18 +11,19 @@ ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Configure MDT settings
|
||||
|
||||
One of the most powerful features in Microsoft Deployment Toolkit (MDT) is its extension capabilities; there is virtually no limitation to what you can do in terms of customization. In this topic, you learn about configuring customizations for your environment.
|
||||
For the purposes of this topic, we will use four machines: DC01, MDT01, HV01, and PC0001. DC01 is a domain controller, MDT01 is a Windows Server 2012 R2 Standard server, and PC0001 is a Windows 10 Enterprise x64 client used for the MDT simulation environment. OR01 has Microsoft System Center 2012 R2 Orchestrator installed. MDT01, OR01, and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md#proof).
|
||||
For the purposes of this topic, we will use four machines: DC01, MDT01, HV01, and PC0001. DC01 is a domain controller, MDT01 is a Windows Server 2012 R2 Standard server, and PC0001 is a Windows 10 Enterprise x64 client used for the MDT simulation environment. OR01 has Microsoft System Center 2012 R2 Orchestrator installed. MDT01, OR01, and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
|
||||
|
||||
Figure 1. The machines used in this topic.
|
||||
The computers used in this topic.
|
||||
|
||||
## In this section
|
||||
|
||||
@ -37,14 +38,9 @@ Figure 1. The machines used in this topic.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.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)
|
||||
|
||||
[Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)
|
||||
|
||||
[Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)<br>
|
||||
[Create a Windows 10 reference image](create-a-windows-10-reference-image.md)<br>
|
||||
[Deploy a Windows 10 image using MDT](deploy-a-windows-10-image-using-mdt.md)<br>
|
||||
[Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)<br>
|
||||
[Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)<br>
|
||||
[Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md)
|
||||
|
||||
@ -11,7 +11,8 @@ ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -22,25 +23,21 @@ 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 computer refresh process. The refresh scenario, or computer refresh, is a reinstallation of an operating system on the same machine. You can refresh the machine to the same operating system as it is currently running, or to a later version.
|
||||
|
||||
For the purposes of this topic, we will use three machines: DC01, MDT01, and PC0001. DC01 is a domain controller and MDT01 is a Windows Server 2012 R2 Standard server. PC0001 is a machine with Windows 7 Service Pack 1 (SP1) that is going to be refreshed into a Windows 10 machine, with data and settings restored. MDT01 and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md#proof).
|
||||
For the purposes of this topic, we will use three machines: DC01, MDT01, and PC0001. DC01 is a domain controller and MDT01 is a Windows Server 2012 R2 Standard server. PC0001 is a machine with Windows 7 Service Pack 1 (SP1) that is going to be refreshed into a Windows 10 machine, with data and settings restored. MDT01 and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
|
||||
|
||||
Figure 1. The machines used in this topic.
|
||||
The computers used in this topic.
|
||||
|
||||
## <a href="" id="sec01"></a>The computer refresh process
|
||||
## The computer refresh process
|
||||
|
||||
Even though a computer will appear, to the end user, to be upgraded, a computer refresh is not, technically, an in-place upgrade. A computer refresh also involves taking care of user data and settings from the old installation and making sure to restore those at the end of the installation.
|
||||
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.
|
||||
|
||||
3. Apply the new operating system image.
|
||||
|
||||
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.
|
||||
@ -62,12 +59,11 @@ As an example, the following line configures USMT to migrate only domain user pr
|
||||
|
||||
In addition to the command-line switches that control which profiles to migrate, the XML templates control exactly what data is being migrated. You can control data within and outside the user profiles
|
||||
|
||||
## <a href="" id="sec02"></a>Create a custom User State Migration Tool (USMT) template
|
||||
## Create a custom User State Migration Tool (USMT) template
|
||||
|
||||
In this section, you learn to migrate additional data using a custom template. You configure the environment to use a custom USMT XML template that will:
|
||||
|
||||
1. Back up the **C:\\Data** folder (including all files and folders).
|
||||
|
||||
2. Scan the local disk for PDF documents (\*.pdf files) and restore them into the **C:\\Data\\PDF Documents** folder on the destination machine.
|
||||
The custom USMT template is named MigContosoData.xml, and you can find it in the sample files for this documentation, which include:
|
||||
|
||||
@ -86,7 +82,7 @@ In order to use the custom MigContosoData.xml USMT template, you need to copy it
|
||||
```
|
||||
3. Save the CustomSettings.ini file.
|
||||
|
||||
## <a href="" id="sec03"></a>Refresh a Windows 7 SP1 client
|
||||
## Refresh a Windows 7 SP1 client
|
||||
|
||||
After adding the additional USMT template and configuring the CustomSettings.ini file to use it, you are now ready to refresh a Windows 7 SP1 client to Windows 10. In these steps, we assume you have a Windows 7 SP1 client named PC0001 in your environment that is ready for a refresh to Windows 10.
|
||||
|
||||
@ -119,14 +115,9 @@ Figure 2. Starting the computer refresh from the running Windows 7 SP1 client.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.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)
|
||||
|
||||
[Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)
|
||||
|
||||
[Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md)
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)<br>
|
||||
[Create a Windows 10 reference image](create-a-windows-10-reference-image.md)<br>
|
||||
[Deploy a Windows 10 image using MDT](deploy-a-windows-10-image-using-mdt.md)<br>
|
||||
[Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)<br>
|
||||
[Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md)<br>
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
|
||||
@ -26,22 +26,20 @@ For the purposes of this topic, we will use four machines: DC01, MDT01, PC0002,
|
||||
|
||||
|
||||
|
||||
Figure 1. The machines used in this topic.
|
||||
The computers used in this topic.
|
||||
|
||||
## <a href="" id="sec01"></a>Prepare for the computer replace
|
||||
## Prepare for the computer replace
|
||||
|
||||
When preparing for the computer replace, you need to create a folder in which to store the backup, and a backup only task sequence that you run on the old computer.
|
||||
|
||||
### Configure the rules on the Microsoft Deployment Toolkit (MDT) Production share
|
||||
|
||||
1. On MDT01, using the Deployment Workbench, update the MDT Production deployment share rules.
|
||||
|
||||
2. Change the **SkipUserData=YES** option to **NO**, and click **OK**.
|
||||
|
||||
### Create and share the MigData folder
|
||||
|
||||
1. On MDT01, log on as **CONTOSO\\Administrator**.
|
||||
|
||||
2. Create and share the **E:\\MigData** folder by running the following three commands in an elevated Windows PowerShell prompt:
|
||||
``` powershell
|
||||
New-Item -Path E:\MigData -ItemType directory
|
||||
@ -64,24 +62,20 @@ When preparing for the computer replace, you need to create a folder in which to
|
||||
|
||||
|
||||
|
||||
Figure 2. The Backup Only Task Sequence action list.
|
||||
The Backup Only Task Sequence action list.
|
||||
|
||||
## <a href="" id="sec02"></a>Perform the computer replace
|
||||
|
||||
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 Window Imaging (WIM) backup.
|
||||
|
||||
2. On the new machine, you perform a standard bare-metal deployment. At the end of the bare-metal deployment, the USMT backup from the old computer is restored.
|
||||
|
||||
### Execute the replace task sequence
|
||||
|
||||
1. On PC0002, log on as **CONTOSO\\Administrator**.
|
||||
|
||||
2. Verify that you have write access to the **\\\\MDT01\\MigData$** share.
|
||||
|
||||
3. Execute **\\\\MDT01\\MDTProduction$\\Scripts\\LiteTouch.vbs**.
|
||||
|
||||
4. Complete the Windows Deployment Wizard using the following settings:
|
||||
|
||||
1. Select a task sequence to execute on this computer: Backup Only Task Sequence
|
||||
@ -98,13 +92,13 @@ During a computer replace, these are the high-level steps that occur:
|
||||
|
||||
|
||||
|
||||
Figure 3. The new task sequence running the Capture User State action on PC0002.
|
||||
The new task sequence running the Capture User State action on PC0002.
|
||||
|
||||
5. On MDT01, verify that you have an USMT.MIG compressed backup file in the **E:\\MigData\\PC0002\\USMT** folder.
|
||||
|
||||
|
||||
|
||||
Figure 4. The USMT backup of PC0002.
|
||||
The USMT backup of PC0002.
|
||||
|
||||
### Deploy the PC0007 virtual machine
|
||||
|
||||
@ -120,7 +114,7 @@ During a computer replace, these are the high-level steps that occur:
|
||||
|
||||
|
||||
|
||||
Figure 5. The initial PXE boot process of PC0005.
|
||||
The initial PXE boot process of PC0005.
|
||||
|
||||
3. After Windows Preinstallation Environment (Windows PE) has booted, complete the Windows Deployment Wizard using the following settings:
|
||||
|
||||
@ -139,14 +133,9 @@ During a computer replace, these are the high-level steps that occur:
|
||||
|
||||
## Related topics
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.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)
|
||||
|
||||
[Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)
|
||||
|
||||
[Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)
|
||||
|
||||
[Get started with the Microsoft Deployment Toolkit (MDT)](get-started-with-the-microsoft-deployment-toolkit.md)<br>
|
||||
[Create a Windows 10 reference image](create-a-windows-10-reference-image.md)<br>
|
||||
[Deploy a Windows 10 image using MDT](deploy-a-windows-10-image-using-mdt.md)<br>
|
||||
[Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md)<br>
|
||||
[Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md)<br>
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
|
||||
@ -10,8 +10,10 @@ ms.localizationpriority: medium
|
||||
ms.date: 10/11/2017
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.audience: itpro
author: greg-lindsay
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.audience: itpro
|
||||
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -444,7 +446,7 @@ If you have already completed steps in [Deploy Windows 10 in a test lab using Mi
|
||||
- Summary: click **Next**
|
||||
- Confirmation: click **Finish**
|
||||
|
||||
9. For purposes of this test lab, we will not add applications, such as Microsoft Office, to the deployment share. For information about adding applications, see the [Add applications](deploy-windows-mdt/create-a-windows-10-reference-image.md#sec03) section of the [Create a Windows 10 reference image](deploy-windows-mdt/create-a-windows-10-reference-image.md) topic in the TechNet library.
|
||||
9. For purposes of this test lab, we will not add applications, such as Microsoft Office, to the deployment share. For information about adding applications, see the [Add applications](deploy-windows-mdt/create-a-windows-10-reference-image.md#add-applications) section of the [Create a Windows 10 reference image](deploy-windows-mdt/create-a-windows-10-reference-image.md) topic in the TechNet library.
|
||||
|
||||
10. The next step is to create a task sequence to reference the operating system that was imported. To create a task sequence, right-click the **Task Sequences** node under **MDT Build Lab** and then click **New Task Sequence**. Use the following settings for the New Task Sequence Wizard:
|
||||
- Task sequence ID: **REFW10X64-001**<br>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user