mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
fix file
This commit is contained in:
Greg Lindsay
parent
9a50e36b7f
commit
960e8574b6
@ -19,7 +19,7 @@ ms.topic: article
|
||||
# Get started with the Microsoft Deployment Toolkit (MDT)
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 10
|
||||
|
||||
This topic will help you gain a better understanding of how to use the Microsoft Deployment Toolkit (MDT) to deploy Windows 10. When you are ready to try using MDT to deploy Windows 10 in various says, see [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
@ -34,39 +34,39 @@ In addition to familiarizing you with the features and options available in MDT,
|
||||
The Microsoft Deployment Toolkit (MDT) has been in existence since 2003, when it was first introduced as Business Desktop Deployment (BDD) 1.0. The toolkit has evolved, both in functionality and popularity, and today it is considered fundamental to Windows operating system and enterprise application deployment.
|
||||
|
||||
MDT has many useful features, the most important of which are:
|
||||
- **Windows Client support.** Supports Windows 7, Windows 8, Windows 8.1, and Windows 10.
|
||||
- **Windows Server support.** Supports Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.
|
||||
- **Additional operating systems support.** Supports Windows Thin PC and Windows Embedded POSReady 7, as well as Windows 8.1 Embedded Industry.
|
||||
- **UEFI support.** Supports deployment to machines using Unified Extensible Firmware Interface (UEFI) version 2.3.1.
|
||||
- **GPT support.** Supports deployment to machines that require the new GUID (globally unique identifier) partition table (GPT) format. This is related to UEFI.
|
||||
- **Enhanced Windows PowerShell support.** Provides support for running PowerShell scripts.
|
||||
- **Windows Client support.** Supports Windows 7, Windows 8, Windows 8.1, and Windows 10.
|
||||
- **Windows Server support.** Supports Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019.
|
||||
- **Additional operating systems support.** Supports Windows Thin PC and Windows Embedded POSReady 7, as well as Windows 8.1 Embedded Industry.
|
||||
- **UEFI support.** Supports deployment to machines using Unified Extensible Firmware Interface (UEFI) version 2.3.1.
|
||||
- **GPT support.** Supports deployment to machines that require the new GUID (globally unique identifier) partition table (GPT) format. This is related to UEFI.
|
||||
- **Enhanced Windows PowerShell support.** Provides support for running PowerShell scripts.
|
||||
|
||||
|
||||
|
||||
Figure 2. The deployment share mounted as a standard PSDrive allows for administration using PowerShell.
|
||||
|
||||
- **Add local administrator accounts.** Allows you to add multiple user accounts to the local Administrators group on the target computers, either via settings or the deployment wizard.
|
||||
- **Automated participation in CEIP and WER.** Provides configuration for participation in Windows Customer Experience Improvement Program (CEIP) and Windows Error Reporting (WER).
|
||||
- **Deploy Windows RE.** Enables deployment of a customized Windows Recovery Environment (Windows RE) as part of the task sequence.
|
||||
- **Deploy to VHD.** Provides ready-made task sequence templates for deploying Windows into a virtual hard disk (VHD) file.
|
||||
- **Improved deployment wizard.** Provides additional progress information and a cleaner UI for the Lite Touch Deployment Wizard.
|
||||
- **Monitoring.** Allows you to see the status of currently running deployments.
|
||||
- **Apply GPO Pack.** Allows you to deploy local group policy objects created by Microsoft Security Compliance Manager (SCM).
|
||||
- **Partitioning routines.** Provides improved partitioning routines to ensure that deployments work regardless of the current hard drive structure.
|
||||
- **Offline BitLocker.** Provides the capability to have BitLocker enabled during the Windows Preinstallation Environment (Windows PE) phase, thus saving hours of encryption time.
|
||||
- **USMT offline user-state migration.** Provides support for running the User State Migration Tool (USMT) capture offline, during the Windows PE phase of the deployment.
|
||||
- **Add local administrator accounts.** Allows you to add multiple user accounts to the local Administrators group on the target computers, either via settings or the deployment wizard.
|
||||
- **Automated participation in CEIP and WER.** Provides configuration for participation in Windows Customer Experience Improvement Program (CEIP) and Windows Error Reporting (WER).
|
||||
- **Deploy Windows RE.** Enables deployment of a customized Windows Recovery Environment (Windows RE) as part of the task sequence.
|
||||
- **Deploy to VHD.** Provides ready-made task sequence templates for deploying Windows into a virtual hard disk (VHD) file.
|
||||
- **Improved deployment wizard.** Provides additional progress information and a cleaner UI for the Lite Touch Deployment Wizard.
|
||||
- **Monitoring.** Allows you to see the status of currently running deployments.
|
||||
- **Apply GPO Pack.** Allows you to deploy local group policy objects created by Microsoft Security Compliance Manager (SCM).
|
||||
- **Partitioning routines.** Provides improved partitioning routines to ensure that deployments work regardless of the current hard drive structure.
|
||||
- **Offline BitLocker.** Provides the capability to have BitLocker enabled during the Windows Preinstallation Environment (Windows PE) phase, thus saving hours of encryption time.
|
||||
- **USMT offline user-state migration.** Provides support for running the User State Migration Tool (USMT) capture offline, during the Windows PE phase of the deployment.
|
||||
|
||||
|
||||
|
||||
Figure 3. The offline USMT backup in action.
|
||||
|
||||
- **Install or uninstall Windows roles or features.** Enables you to select roles and features as part of the deployment wizard. MDT also supports uninstall of roles and features.
|
||||
- **Microsoft System Center 2012 Orchestrator integration.** Provides the capability to use Orchestrator runbooks as part of the task sequence.
|
||||
- **Support for DaRT.** Supports optional integration of the DaRT components into the boot image.
|
||||
- **Support for Office 2013.** Provides added support for deploying Microsoft Office Professional Plus 2013.
|
||||
- **Support for Modern UI app package provisioning.** Provisions applications based on the new Windows app package standard, which is used in Windows 8 and later.
|
||||
- **Extensibility.** Provides the capability to extend MDT far beyond the built-in features by adding custom scripts, web services, System Center Orchestrator runbooks, PowerShell scripts, and VBScripts.
|
||||
- **Upgrade task sequence.** Provides a new upgrade task sequence template that you can use to upgrade existing Windows 7, Windows 8, and Windows 8.1 systems directly to Windows 10, automatically preserving all data, settings, applications, and drivers. For more information about using this new upgrade task sequence, refer to the [Microsoft Deployment Toolkit resource page](https://go.microsoft.com/fwlink/p/?LinkId=618117).
|
||||
- **Install or uninstall Windows roles or features.** Enables you to select roles and features as part of the deployment wizard. MDT also supports uninstall of roles and features.
|
||||
- **Microsoft System Center 2012 Orchestrator integration.** Provides the capability to use Orchestrator runbooks as part of the task sequence.
|
||||
- **Support for DaRT.** Supports optional integration of the DaRT components into the boot image.
|
||||
- **Support for Office 2013.** Provides added support for deploying Microsoft Office Professional Plus 2013.
|
||||
- **Support for Modern UI app package provisioning.** Provisions applications based on the new Windows app package standard, which is used in Windows 8 and later.
|
||||
- **Extensibility.** Provides the capability to extend MDT far beyond the built-in features by adding custom scripts, web services, System Center Orchestrator runbooks, PowerShell scripts, and VBScripts.
|
||||
- **Upgrade task sequence.** Provides a new upgrade task sequence template that you can use to upgrade existing Windows 7, Windows 8, and Windows 8.1 systems directly to Windows 10, automatically preserving all data, settings, applications, and drivers. For more information about using this new upgrade task sequence, refer to the [Microsoft Deployment Toolkit resource page](https://go.microsoft.com/fwlink/p/?LinkId=618117).
|
||||
|
||||
## MDT Lite Touch components
|
||||
|
||||
@ -84,10 +84,10 @@ A deployment share is essentially a folder on the server that is shared and cont
|
||||
## Rules
|
||||
|
||||
The rules (CustomSettings.ini and Bootstrap.ini) make up the brain of MDT. The rules control the Windows Deployment Wizard on the client and, for example, can provide the following settings to the machine being deployed:
|
||||
- Computer name
|
||||
- Domain to join, and organizational unit (OU) in Active Directory to hold the computer object
|
||||
- Whether to enable BitLocker
|
||||
- Regional settings
|
||||
- Computer name
|
||||
- Domain to join, and organizational unit (OU) in Active Directory to hold the computer object
|
||||
- Whether to enable BitLocker
|
||||
- Regional settings
|
||||
You can manage hundreds of settings in the rules. For more information, see the [Microsoft Deployment Toolkit resource center](https://go.microsoft.com/fwlink/p/?LinkId=618117).
|
||||
|
||||
|
||||
@ -120,38 +120,38 @@ With the Deployment Workbench, you can add any Microsoft packages that you want
|
||||
Task sequences are the heart and soul of the deployment solution. When creating a task sequence, you need to select a template. The templates are located in the Templates folder in the MDT installation directory, and they determine which default actions are present in the sequence.
|
||||
|
||||
You can think of a task sequence as a list of actions that need to be executed in a certain order. Each action can also have conditions. Some examples of actions are as follows:
|
||||
- **Gather.** Reads configuration settings from the deployment server.
|
||||
- **Format and Partition.** Creates the partition(s) and formats them.
|
||||
- **Inject Drivers.** Finds out which drivers the machine needs and downloads them from the central driver repository.
|
||||
- **Apply Operating System.** Uses ImageX to apply the image.
|
||||
- **Windows Update.** Connects to a WSUS server and updates the machine.
|
||||
- **Gather.** Reads configuration settings from the deployment server.
|
||||
- **Format and Partition.** Creates the partition(s) and formats them.
|
||||
- **Inject Drivers.** Finds out which drivers the machine needs and downloads them from the central driver repository.
|
||||
- **Apply Operating System.** Uses ImageX to apply the image.
|
||||
- **Windows Update.** Connects to a WSUS server and updates the machine.
|
||||
|
||||
## Task sequence templates
|
||||
|
||||
MDT comes with nine default task sequence templates. You can also create your own templates. As long as you store them in the Templates folder, they will be available when you create a new task sequence.
|
||||
- **Sysprep and Capture task sequence.** Used to run the System Preparation (Sysprep) tool and capture an image of a reference computer.
|
||||
- **Sysprep and Capture task sequence.** Used to run the System Preparation (Sysprep) tool and capture an image of a reference computer.
|
||||
|
||||
**Note**
|
||||
It is preferable to use a complete build and capture instead of the Sysprep and Capture task sequence. A complete build and capture can be automated, whereas Sysprep and Capture cannot.
|
||||
|
||||
- **Standard Client task sequence.** The most frequently used task sequence. Used for creating reference images and for deploying clients in production.
|
||||
- **Standard Client Replace task sequence.** Used to run User State Migration Tool (USMT) backup and the optional full Windows Imaging (WIM) backup action. Can also be used to do a secure wipe of a machine that is going to be decommissioned.
|
||||
- **Custom task sequence.** As the name implies, a custom task sequence with only one default action (one Install Application action).
|
||||
- **Standard Server task sequence.** The default task sequence for deploying operating system images to servers. The main difference between this template and the Standard Client task sequence template is that it does not contain any USMT actions because USMT is not supported on servers.
|
||||
- **Lite Touch OEM task sequence.** Used to preload operating systems images on the computer hard drive. Typically used by computer original equipment manufacturers (OEMs) but some enterprise organizations also use this feature.
|
||||
- **Post OS Installation task sequence.** A task sequence prepared to run actions after the operating system has been deployed. Very useful for server deployments but not often used for client deployments.
|
||||
- **Deploy to VHD Client task sequence.** Similar to the Standard Client task sequence template but also creates a virtual hard disk (VHD) file on the target computer and deploys the image to the VHD file.
|
||||
- **Deploy to VHD Server task sequence.** Same as the Deploy to VHD Client task sequence but for servers.
|
||||
- **Standard Client Upgrade task sequence.** A simple task sequence template used to perform an in-place upgrade from Windows 7, Windows 8, or Windows 8.1 directly to Windows 10, automatically preserving existing data, settings, applications, and drivers.
|
||||
- **Standard Client task sequence.** The most frequently used task sequence. Used for creating reference images and for deploying clients in production.
|
||||
- **Standard Client Replace task sequence.** Used to run User State Migration Tool (USMT) backup and the optional full Windows Imaging (WIM) backup action. Can also be used to do a secure wipe of a machine that is going to be decommissioned.
|
||||
- **Custom task sequence.** As the name implies, a custom task sequence with only one default action (one Install Application action).
|
||||
- **Standard Server task sequence.** The default task sequence for deploying operating system images to servers. The main difference between this template and the Standard Client task sequence template is that it does not contain any USMT actions because USMT is not supported on servers.
|
||||
- **Lite Touch OEM task sequence.** Used to preload operating systems images on the computer hard drive. Typically used by computer original equipment manufacturers (OEMs) but some enterprise organizations also use this feature.
|
||||
- **Post OS Installation task sequence.** A task sequence prepared to run actions after the operating system has been deployed. Very useful for server deployments but not often used for client deployments.
|
||||
- **Deploy to VHD Client task sequence.** Similar to the Standard Client task sequence template but also creates a virtual hard disk (VHD) file on the target computer and deploys the image to the VHD file.
|
||||
- **Deploy to VHD Server task sequence.** Same as the Deploy to VHD Client task sequence but for servers.
|
||||
- **Standard Client Upgrade task sequence.** A simple task sequence template used to perform an in-place upgrade from Windows 7, Windows 8, or Windows 8.1 directly to Windows 10, automatically preserving existing data, settings, applications, and drivers.
|
||||
|
||||
## Selection profiles
|
||||
|
||||
Selection profiles, which are available in the Advanced Configuration node, provide a way to filter content in the Deployment Workbench. Selection profiles are used for several purposes in the Deployment Workbench and in Lite Touch deployments. For example, they can be used to:
|
||||
- Control which drivers and packages are injected into the Lite Touch (and generic) boot images.
|
||||
- Control which drivers are injected during the task sequence.
|
||||
- Control what is included in any media that you create.
|
||||
- Control what is replicated to other deployment shares.
|
||||
- Filter which task sequences and applications are displayed in the Deployment Wizard.
|
||||
- Control which drivers and packages are injected into the Lite Touch (and generic) boot images.
|
||||
- Control which drivers are injected during the task sequence.
|
||||
- Control what is included in any media that you create.
|
||||
- Control what is replicated to other deployment shares.
|
||||
- Filter which task sequences and applications are displayed in the Deployment Wizard.
|
||||
|
||||
## Logging
|
||||
|
||||
@ -172,57 +172,4 @@ On the deployment share, you also can enable monitoring. After you enable monito
|
||||
[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)<br>
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
=======
|
||||
=======
|
||||
>>>>>>> bc07494f1704b1e23c818d59e7f42c56fefb83d1
|
||||
---
|
||||
title: Get started with the Microsoft Deployment Toolkit (MDT) (Windows 10)
|
||||
description: This topic will help you gain a better understanding of how to use the Microsoft Deployment Toolkit (MDT), as part of a Windows operating system deployment.
|
||||
ms.assetid: a256442c-be47-4bb9-a105-c831f58ce3ee
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: deploy, image, feature, install, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Get started with the Microsoft Deployment Toolkit (MDT)
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
This topic will help you gain a better understanding of how to use the Microsoft Deployment Toolkit (MDT), as part of a Windows operating system deployment. MDT is one of the most important tools available to IT professionals today. You can use it to create reference images or as a complete deployment solution. MDT also can be used to extend the operating system deployment features available in Microsoft System Center 2012 R2 Configuration Manager.
|
||||
|
||||
In addition to familiarizing you with the features and options available in MDT, this topic will walk you through the process of preparing for deploying Windows 10 using MDT by configuring Active Directory, creating an organizational unit (OU) structure, creating service accounts, configuring log files and folders, and installing the tools needed to view the logs and continue with the deployment process.
|
||||
|
||||
For the purposes of this topic, we will use two machines: DC01 and MDT01. DC01 is a domain controller and MDT01 is a Windows Server 2012 R2 standard server. MDT01 is a member 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).
|
||||
|
||||
|
||||
|
||||
Figure 1. The machines used in this topic.
|
||||
|
||||
## In this section
|
||||
|
||||
- [Key features in MDT](key-features-in-mdt.md)
|
||||
- [MDT Lite Touch components](mdt-lite-touch-components.md)
|
||||
- [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md)
|
||||
|
||||
## Related topics
|
||||
|
||||
[Microsoft Deployment Toolkit downloads and documentation](https://go.microsoft.com/fwlink/p/?LinkId=618117)<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)<br>
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
|
||||
[Configure MDT settings](configure-mdt-settings.md)
|
||||
Loading…
x
Reference in New Issue
Block a user