MDT (Microsoft Deployment Toolkit)
Developer(s)Microsoft
Initial releaseAugust 2003 (2003-08)
Stable release
Build 8456 (6.3.8456.1000) / 25 January 2019 (2019-01-25)[1]
Operating system
Platformx86 and x64[1]
Size20 MB[1]
Available inEnglish[1]
TypeSystem software
LicenseFreeware[1]
Websitewww.microsoft.com/deployment Edit this on Wikidata

Microsoft Deployment Toolkit (MDT; originally released as Business Desktop Deployment in August 2003[2][3]) is a free software package from Microsoft for automating the deployment of Windows 10, Server 2019 and older Windows Server and desktop operating systems.[4]

Overview

MDT can help build an automated installation source for deploying Windows operating systems from Windows 7, Windows 10 and Windows Server 2008 onwards, from either a single machine or a central server distribution tool, such as Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM).[5] Device drivers, Windows updates and software can be included with the build.[6][5]

All the software intended for installation (Operating System, drivers, updates and applications) are added to a pool of available software and packaged into deployment packages.[7] The Operating System and drivers to be included with this package are selected, and the administrator password, owner information, and product key are specified.[5][7][8] Microsoft Deployment Toolkit generates a custom Windows PE (Preinstallation Environment) image that allows client machines to install the assembled deployment packages over the network from the MDT server.[7][8] This Windows PE disk image can be burned to and booted from a CD, or booted with Windows Deployment Services. When selecting the package to deploy, software that has been included in the pool may also be selected for installation.[5]

Operation

The Microsoft Deployment Toolkit (MDT) supports three types of deployments:[5] Zero Touch Installation (ZTI), Lite Touch Installation (LTI), and User Driven Installation (UDI). ZTI is a fully automated deployment scheme in which installation requires no user interaction whatsoever.[8] UDI deployments require full manual intervention to respond to every installation prompt, such as machine name, password or language setting.[9] ZTI and UDI deployments both require a Microsoft System Center infrastructure.[5] ZTI deployments require a persistent network connection to the distribution point.[8] LTI deployments require limited user interaction. An LTI deployment needs very little infrastructure, so it can be installed from a network share, or media using either a USB flash drive or an optical disc.[7]

See also

References

  1. 1 2 3 4 5 "Microsoft Deployment Toolkit Download Page". Microsoft.
  2. Niehaus, Michael (22 Jan 2008). "A concise history of BDD". Retrieved 27 Mar 2021.
  3. "Deploying fully patched Windows 10 computers: A guide for IT pros". TechGenix. 2020-12-30. Retrieved 2021-03-27.
  4. Vigo, Jesus (July 5, 2016). "How to set up Microsoft Deployment Toolkit: Step by step". TechRepublic. Retrieved 2021-03-27.
  5. 1 2 3 4 5 6 "Microsoft (August 2012). Using the Microsoft Deployment Toolkit". Archived from the original on 2019-09-14. Retrieved 2013-02-17.
  6. Sharwood, Simon. "Microsoft automates Office 365 installs". www.theregister.com. Retrieved 2021-03-27.
  7. 1 2 3 4 "Microsoft (August 2012). Quick Start Guide for Lite Touch Installation". Archived from the original on 2019-09-14. Retrieved 2013-02-17.
  8. 1 2 3 4 "Microsoft (August 2012). Quick Start Guide for Configuration Manager 2012". Archived from the original on 2019-09-14. Retrieved 2013-02-17.
  9. "Microsoft (August 2012). Quick Start Guide for User Driven Installation". Archived from the original on 2019-09-14. Retrieved 2013-02-17.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.