mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
fixes
This commit is contained in:
@ -103,7 +103,7 @@
|
||||
##### [Use Orchestrator runbooks with MDT](deploy-windows-mdt/use-orchestrator-runbooks-with-mdt.md)
|
||||
|
||||
#### Deploy Windows 10 with Microsoft Endpoint Configuration Manager
|
||||
##### Get started with Configuration Manager(get-started-with-configuration-manager.md)
|
||||
##### [Get started with Configuration Manager](get-started-with-configuration-manager.md)
|
||||
##### Deploy Windows 10 with Configuration Manager
|
||||
###### [Integrate Configuration Manager with MDT](integrate-configuration-manager-with-mdt.md)
|
||||
###### [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
@ -1,5 +1,5 @@
|
||||
# Deploy Windows 10 with Microsoft Endpoint Configuration Manager
|
||||
## Get started with Configuration Manager(get-started-with-configuration-manager.md)
|
||||
## [Get started with Configuration Manager](get-started-with-configuration-manager.md)
|
||||
|
||||
## Deploy Windows 10 with Configuration Manager
|
||||
### [Integrate Configuration Manager with MDT](integrate-configuration-manager-with-mdt.md)
|
||||
|
@ -25,91 +25,58 @@ ms.topic: article
|
||||
|
||||
In this topic, you will learn how to create a Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard. Creating task sequences in Configuration Manager requires many more steps than creating task sequences for MDT Lite Touch installation. Luckily, the MDT wizard helps you through the process and also guides you through creating the needed packages.
|
||||
|
||||
For the purposes of this topic, we will use two machines: DC01 and CM01. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard, both of which 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).
|
||||
For the purposes of this topic, we will use two machines: DC01 and CM01. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard, both of which are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Prepare for deployment with MDT](../deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
## <a href="" id="sec01"></a>Create a task sequence using the MDT Integration Wizard
|
||||
## Create a task sequence using the MDT Integration Wizard
|
||||
|
||||
|
||||
This section walks you through the process of creating a Configuration Manager task sequence for production use.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, expand **Operating Systems**, right-click **Task Sequences**, and select **Create MDT Task Sequence**.
|
||||
|
||||
2. On the **Choose Template** page, select the **Client Task Sequence** template and click **Next**.
|
||||
|
||||
3. On the **General** page, assign the following settings and then click **Next**:
|
||||
|
||||
* Task sequence name: Windows 10 Enterprise x64 RTM
|
||||
|
||||
* Task sequence comments: Production image with Office 2013
|
||||
|
||||
4. On the **Details** page, assign the following settings and then click **Next**:
|
||||
|
||||
* Join a Domain
|
||||
|
||||
* Domain: contoso.com
|
||||
|
||||
* Account: CONTOSO\\CM\_JD
|
||||
|
||||
* Password: Passw0rd!
|
||||
|
||||
* Windows Settings
|
||||
|
||||
* User name: Contoso
|
||||
|
||||
* Organization name: Contoso
|
||||
|
||||
* Product key: <blank>
|
||||
|
||||
5. On the **Capture Settings** page, accept the default settings, and click **Next**.
|
||||
|
||||
6. On the **Boot Image** page, browse and select the **Zero Touch WinPE x64** boot image package. Then click **Next**.
|
||||
|
||||
7. On the **MDT Package** page, select **Create a new Microsoft Deployment Toolkit Files package**, and in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\MDT\\MDT**. Then click **Next**.
|
||||
|
||||
8. On the **MDT Details** page, assign the name **MDT** and click **Next**.
|
||||
|
||||
9. On the **OS Image** page, browse and select the **Windows 10 Enterprise x64 RTM** package. Then click **Next**.
|
||||
|
||||
10. On the **Deployment Method** page, accept the default settings and click **Next**.
|
||||
|
||||
11. On the **Client Package** page, browse and select the **OSD / Configuration Manager Client** package. Then click **Next**.
|
||||
|
||||
12. On the **USMT Package** page, browse and select **the OSD / Microsoft Corporation User State Migration Tool for Windows 8 10.0.10240.16384** package. Then click **Next**.
|
||||
|
||||
13. On the **Settings Package** page, select the **Create a new settings package** option, and in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\Settings\\Windows 10 x64 Settings**. Then click **Next**.
|
||||
|
||||
14. On the **Settings Details** page, assign the name **Windows 10 x64 Settings** and click **Next**.
|
||||
|
||||
15. On the **Sysprep Package** page, click **Next** twice.
|
||||
|
||||
16. On the **Confirmation** page, click **Finish**.
|
||||
|
||||
## <a href="" id="sec02"></a>Edit the task sequence
|
||||
|
||||
## Edit the task sequence
|
||||
|
||||
After you create the task sequence, we recommend that you configure the task sequence for an optimal deployment experience. The configurations include enabling support for Unified Extensible Firmware Interface (UEFI), dynamic organizational unit (OU) allocation, computer replace scenarios, and more.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, select **Task Sequences**, right-click **Windows 10 Enterprise x64 RTM** task sequence, and select **Edit**.
|
||||
|
||||
2. In the **Install** group, select the **Set Variable for Drive Letter** action and configure the following:
|
||||
|
||||
* OSDPreserveDriveLetter: True
|
||||
|
||||
>[!NOTE]
|
||||
>If you don't change this value, your Windows installation will end up in E:\\Windows.
|
||||
|
||||
3. In the **Post Install** group, select **Apply Network Settings**, and configure the Domain OU value to use the **Contoso / Workstations** OU (browse for values).
|
||||
|
||||
4. In the **Post Install** group, disable the **Auto Apply Drivers** action. (Disabling is done by selecting the action and, in the **Options** tab, selecting the **Disable this step** check box.)
|
||||
|
||||
5. After the disabled **Post Install / Auto Apply Drivers** action, add a new group name: **Drivers**.
|
||||
|
||||
6. After the **Post Install / Drivers** group, add an **Apply Driver Package** action with the following settings:
|
||||
|
||||
* Name: HP EliteBook 8560w
|
||||
|
||||
* Driver Package: Windows 10 x64 - HP EliteBook 8560w
|
||||
|
||||
* Options: Task Sequence Variable: Model equals HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
@ -120,7 +87,6 @@ After you create the task sequence, we recommend that you configure the task seq
|
||||
*Figure 24. The driver package options*
|
||||
|
||||
7. In the **State Restore / Install Applications** group, select the **Install Application** action.
|
||||
|
||||
8. Select the **Install the following applications** option, and add the OSD / Adobe Reader XI - OSD Install application to the list.
|
||||
|
||||

|
||||
@ -128,27 +94,17 @@ After you create the task sequence, we recommend that you configure the task seq
|
||||
*Figure 25. Add an application to the Configuration Manager task sequence*
|
||||
|
||||
9. In the **State Restore** group, after the **Set Status 5** action, add a **Request State Store** action with the following settings:
|
||||
|
||||
* Restore state from another computer
|
||||
|
||||
* If computer account fails to connect to state store, use the Network Access account
|
||||
|
||||
* Options: Continue on error
|
||||
|
||||
* Options / Condition:
|
||||
|
||||
* Task Sequence Variable
|
||||
|
||||
* USMTLOCAL not equals True
|
||||
|
||||
10. In the **State Restore** group, after the **Restore User State** action, add a **Release State Store** action with the following settings:
|
||||
|
||||
* Options: Continue on error
|
||||
|
||||
* Options / Condition:
|
||||
|
||||
* Task Sequence Variable
|
||||
|
||||
* USMTLOCAL not equals True
|
||||
|
||||
11. Click **OK**.
|
||||
@ -156,36 +112,23 @@ After you create the task sequence, we recommend that you configure the task seq
|
||||
>[!NOTE]
|
||||
>The Request State Store and Release State Store actions need to be added for common computer replace scenarios.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="sec03"></a>Move the packages
|
||||
|
||||
## Move the packages
|
||||
|
||||
While creating the task sequence with the MDT wizard, a few operating system deployment packages were created. To move these packages to the OSD folder, take the following steps.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, expand **Application Management**, and then select **Packages**.
|
||||
|
||||
2. Select the **MDT** and **Windows 10 x64 Settings** packages, right-click and select **Move**.
|
||||
|
||||
3. In the **Move Selected Items** dialog box, select the **OSD** folder, and click **OK**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](../deploy-windows-sccm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](../deploy-windows-sccm/add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](../deploy-windows-sccm/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](../deploy-windows-sccm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](../deploy-windows-sccm/deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
[Integrate Configuration Manager with MDT](integrate-configuration-manager-with-mdt.md)<br>
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)<br>
|
||||
[Create a custom Windows PE boot image with Configuration Manager](../deploy-windows-sccm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)<br>
|
||||
[Add a Windows 10 operating system image using Configuration Manager](../deploy-windows-sccm/add-a-windows-10-operating-system-image-using-configuration-manager.md)<br>
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](../deploy-windows-sccm/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)<br>
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](../deploy-windows-sccm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)<br>
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](../deploy-windows-sccm/deploy-windows-10-using-pxe-and-configuration-manager.md)<br>
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)<br>
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)<br>
|
||||
|
@ -22,7 +22,7 @@ ms.topic: article
|
||||
- Windows 10
|
||||
|
||||
This topic will help you understand the benefits of integrating the Microsoft Deployment Toolkit with Microsoft System Center 2012 R2 Configuration Manager SP1 when you deploy a new or updated version of the Windows operating system.
|
||||
MDT is a free, supported download from Microsoft that adds approximately 280 enhancements to Windows operating system deployment with System Center 2012 R2 Configuration Manager SP1. It is, therefore, recommended that you utilize MDT when deploying the Windows operating system with Configuration Manager SP1. In addition to integrating MDT with Configuration Manager, we also recommend using MDT Lite Touch to create the Windows 10 reference images used in Configuration Manager. For more information on how to create a reference image, see [Create a Windows 10 reference image](create-a-windows-10-reference-image.md).
|
||||
MDT is a free, supported download from Microsoft that adds approximately 280 enhancements to Windows operating system deployment with System Center 2012 R2 Configuration Manager SP1. It is, therefore, recommended that you utilize MDT when deploying the Windows operating system with Configuration Manager SP1. In addition to integrating MDT with Configuration Manager, we also recommend using MDT Lite Touch to create the Windows 10 reference images used in Configuration Manager. For more information on how to create a reference image, see [Create a Windows 10 reference image](../deploy-windows-mdt/create-a-windows-10-reference-image.md).
|
||||
|
||||
## Why integrate MDT with Configuration Manager
|
||||
|
||||
@ -64,7 +64,7 @@ The task sequence uses instructions that allow you to reduce the number of task
|
||||
|
||||

|
||||
|
||||
Figure 2. The Gather action in the task sequence is reading the rules.
|
||||
The Gather action in the task sequence is reading the rules.
|
||||
|
||||
### MDT adds an operating system deployment simulation environment
|
||||
|
||||
@ -72,7 +72,7 @@ When testing a deployment, it is important to be able to quickly test any change
|
||||
|
||||

|
||||
|
||||
Figure 3. The folder that contains the rules, a few scripts from MDT, and a custom script (Gather.ps1).
|
||||
The folder that contains the rules, a few scripts from MDT, and a custom script (Gather.ps1).
|
||||
|
||||
### MDT adds real-time monitoring
|
||||
|
||||
@ -80,7 +80,7 @@ With MDT integration, you can follow your deployments in real time, and if you h
|
||||
|
||||

|
||||
|
||||
Figure 4. View the real-time monitoring data with PowerShell.
|
||||
View the real-time monitoring data with PowerShell.
|
||||
|
||||
### MDT adds an optional deployment wizard
|
||||
|
||||
@ -88,11 +88,11 @@ For some deployment scenarios, you may need to prompt the user for information d
|
||||
|
||||

|
||||
|
||||
Figure 5. The optional UDI wizard open in the UDI Wizard Designer.
|
||||
The optional UDI wizard open in the UDI Wizard Designer.
|
||||
|
||||
MDT Zero Touch simply extends Configuration Manager with many useful built-in operating system deployment components. By providing well-established, supported solutions, MDT reduces the complexity of deployment in Configuration Manager.
|
||||
|
||||
## <a href="" id="sec02"></a>Why use MDT Lite Touch to create reference images
|
||||
## Why use MDT Lite Touch to create reference images
|
||||
|
||||
You can create reference images for Configuration Manager in Configuration Manager, but in general we recommend creating them in MDT Lite Touch for the following reasons:
|
||||
- In a deployment project, it is typically much faster to create a reference image using MDT Lite Touch than Configuration Manager.
|
||||
@ -104,21 +104,12 @@ You can create reference images for Configuration Manager in Configuration Manag
|
||||
|
||||
## Related topics
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](../deploy-windows-sccm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](../deploy-windows-sccm/add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](../deploy-windows-sccm/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](../deploy-windows-sccm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](../deploy-windows-sccm/deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)<br>
|
||||
[Create a custom Windows PE boot image with Configuration Manager](../deploy-windows-sccm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)<br>
|
||||
[Add a Windows 10 operating system image using Configuration Manager](../deploy-windows-sccm/add-a-windows-10-operating-system-image-using-configuration-manager.md)<br>
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](../deploy-windows-sccm/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)<br>
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](../deploy-windows-sccm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)<br>
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)<br>
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](../deploy-windows-sccm/deploy-windows-10-using-pxe-and-configuration-manager.md)<br>
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)<br>
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
Reference in New Issue
Block a user