This commit is contained in:
Greg Lindsay 2020-01-22 16:36:25 -08:00
parent eaa8ca4f53
commit 5932a9eecf
3 changed files with 17 additions and 17 deletions

View File

@ -31,7 +31,7 @@ For the purposes of this topic, we will use three computers: DC01, MDT01, and PC
![figure 1](../images/mdt-08-fig01.png) ![figure 1](../images/mdt-08-fig01.png)
>[!NOTE] >[!NOTE]
>See [Deploying Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md) for detailed information about the setup for this guide. >See [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md) for more information about the server, client, and network infrastructure used in this guide.
## The reference image ## The reference image

View File

@ -21,18 +21,16 @@ ms.topic: article
**Applies to** **Applies to**
- Windows 10 - Windows 10
This topic provides an overview of the features, components, and capabilities of the Microsoft Deployment Toolkit (MDT). When you are ready to install and start using MDT, see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md). This topic provides an overview of the features, components, and capabilities of the Microsoft Deployment Toolkit (MDT). To download the latest version of MDT, visit the [MDT resource page](https://go.microsoft.com/fwlink/p/?LinkId=618117). When you are ready to start using MDT, see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
## Introduction ## About MDT
The Microsoft Deployment Toolkit (MDT) is a unified collection of tools, processes, and guidance for automating desktop and server deployment. You can use it to create reference images or as a complete deployment solution. MDT is one of the most important tools available to IT professionals today. MDT is a unified collection of tools, processes, and guidance for automating desktop and server deployment. You can use it to create reference images or as a complete deployment solution. MDT is one of the most important tools available to IT professionals today.
In addition to reducing deployment time and standardizing desktop and server images, MDT enables you to more easily manage security and ongoing configurations. MDT builds on top of the core deployment tools in the Windows Assessment and Deployment Kit (Windows ADK) with additional guidance and features designed to reduce the complexity and time required for deployment in an enterprise environment. In addition to reducing deployment time and standardizing desktop and server images, MDT enables you to more easily manage security and ongoing configurations. MDT builds on top of the core deployment tools in the Windows Assessment and Deployment Kit (Windows ADK) with additional guidance and features designed to reduce the complexity and time required for deployment in an enterprise environment.
MDT supports the deployment of Windows 10, as well as Windows 7, Windows 8.1, and Windows Server. It also includes support for zero-touch installation (ZTI) with [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/). MDT supports the deployment of Windows 10, as well as Windows 7, Windows 8.1, and Windows Server. It also includes support for zero-touch installation (ZTI) with [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/).
To download the latest version of MDT, visit the [MDT resource page](https://go.microsoft.com/fwlink/p/?LinkId=618117).
## Key features in MDT ## Key features in MDT
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 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.

View File

@ -25,17 +25,18 @@ This topic will walk you through the steps necessary to create the server struct
## Requirements ## Requirements
The procedures in this guide use the following fictitious names and infrastructure.
### Network and server infrastructure ### Network and server infrastructure
For the purposes of this topic, we will use three computers: **DC01**, **MDT01**, and **HV01**. For the purposes of this topic, we will use three server computers: **DC01**, **MDT01**, and **HV01**.
- All servers are running Windows Server 2019. - All servers are running Windows Server 2019.
- You can use an earlier version of Windows Server with minor modifications to some procedures. - You can use an earlier version of Windows Server with minor modifications to some procedures.
- Although MDT supports Windows Server 2008 R2, At least Windows Server 2012 R2 or later is requried to perform the procedures in this guide. - Note: Although MDT supports Windows Server 2008 R2, at least Windows Server 2012 R2 or later is requried to perform the procedures in this guide.
- DC01 is a domain controller, DHCP server, and DNS server for contoso.com, representing the fictitious Contoso Corporation. - DC01 is a domain controller, DHCP server, and DNS server for <b>contoso.com</b>, representing the fictitious Contoso Corporation.
- MDT01 is a domain member server in contoso.com and has a D: drive that will be used for data. - MDT01 is a domain member server in contoso.com with a data (D:) drive that can store at least 200GB.
- The data drive requires at least 100GB of disk space.
- HV01 is a Hyper-V host computer that is used to build a Windows 10 reference image. - HV01 is a Hyper-V host computer that is used to build a Windows 10 reference image.
- See [Hyper-V requirements](#hyper-v-requirements) below for more information. - See [Hyper-V requirements](#hyper-v-requirements) below for more information about HV01.
### Client computers ### Client computers
@ -51,7 +52,7 @@ Several client computers are referenced in this guide using hostnames PC0001 to
### Storage requirements ### Storage requirements
MDT01 and HV01 should have a data drive (D:) that can support up to 200 GB of data. The system drives on all computers (C:) can be 50 GB in size, but 100 GB is recommended. MDT01 and HV01 should have a data drive (D:) that can support up to 200 GB of data. The system drives on all computers (C:) can be 50 GB in size, but 100 GB is recommended. You can also use a computer with a single, system drive as long as it has at least 200 GB of available storage space. You will need to adjust come procedures in this guide to specify the C: drive instead of the D: drive.
### Hyper-V requirements ### Hyper-V requirements
@ -199,7 +200,6 @@ See the following example:
## Use CMTrace to read log files (optional) ## Use CMTrace to read log files (optional)
The log files in MDT Lite Touch are formatted to be read by Configuration Manager Trace ([CMTrace](https://docs.microsoft.com/sccm/core/support/cmtrace)), which is available as part of the [Microsoft System 2012 R2 Center Configuration Manager Toolkit](https://go.microsoft.com/fwlink/p/?LinkId=734717). You should also download this tool. The log files in MDT Lite Touch are formatted to be read by Configuration Manager Trace ([CMTrace](https://docs.microsoft.com/sccm/core/support/cmtrace)), which is available as part of the [Microsoft System 2012 R2 Center Configuration Manager Toolkit](https://go.microsoft.com/fwlink/p/?LinkId=734717). You should also download this tool.
You can use Notepad (example below): You can use Notepad (example below):
![figure 8](../images/mdt-05-fig09.png) ![figure 8](../images/mdt-05-fig09.png)
@ -208,6 +208,8 @@ Alternatively, CMTrace formatting makes the logs much easier to read. See the sa
![figure 9](../images/mdt-05-fig10.png) ![figure 9](../images/mdt-05-fig10.png)
After installing the ConfigMgrTools.msi file, search for **cmtrace** and pin the tool to your taskbar for easy access.
## Next steps ## Next steps
When you have completed all the steps in this section to prepare for deployment, see [Create a Windows 10 reference image](create-a-windows-10-reference-image.md). When you have completed all the steps in this section to prepare for deployment, see [Create a Windows 10 reference image](create-a-windows-10-reference-image.md).
@ -216,7 +218,7 @@ When you have completed all the steps in this section to prepare for deployment,
**Sample files** **Sample files**
The following sample files are also available to help automate some MDT deployment tasks: The following sample files are also available to help automate some MDT deployment tasks. This guide does not use these files.
- [Gather.ps1](https://go.microsoft.com/fwlink/p/?LinkId=619361). This sample Windows PowerShell script performs the MDT Gather process in a simulated MDT environment. This allows you to test the MDT gather process and check to see if it is working correctly without performing a full Windows deployment. - [Gather.ps1](https://go.microsoft.com/fwlink/p/?LinkId=619361). This sample Windows PowerShell script performs the MDT Gather process in a simulated MDT environment. This allows you to test the MDT gather process and check to see if it is working correctly without performing a full Windows deployment.
- [Set-OUPermissions.ps1](https://go.microsoft.com/fwlink/p/?LinkId=619362). This sample Windows PowerShell script creates a domain account and then configures OU permissions to allow the account to join machines to the domain in the specified OU. - [Set-OUPermissions.ps1](https://go.microsoft.com/fwlink/p/?LinkId=619362). This sample Windows PowerShell script creates a domain account and then configures OU permissions to allow the account to join machines to the domain in the specified OU.
- [MDTSample.zip](https://go.microsoft.com/fwlink/p/?LinkId=619363). This sample web service shows you how to configure a computer name dynamically using MDT. - [MDTSample.zip](https://go.microsoft.com/fwlink/p/?LinkId=619363). This sample web service shows you how to configure a computer name dynamically using MDT.