Microsoft Deployment Toolkit

Microsoft Deployment Toolkit (MDT; formerly Business Desktop Deployment[2]) is a computer program that permits network deployment of Microsoft Windows and Microsoft Office.[1]

Microsoft Deployment Toolkit
Developer(s)Microsoft
Stable release
Build 8456 (6.3.8456.1000) / 25 January 2019 (2019-01-25)[1]
Operating system
[1]
Platformx86 and x64[1]
Size20 MB[1]
Available inEnglish[1]
TypeSystem software
LicenseFreeware[1]
Websitetechnet.microsoft.com/en-gb/windows/dn475741.aspx

Overview

MDT can help build an automated installation source for deploying Windows operating systems from Windows 7 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).[3]Device drivers, Windows updates and software can be included with the build.[1][3]

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.[4] The Operating System and drivers to be included with this package are selected, and the administrator password, owner information, and product key are specified.[3][4][5] 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.[4][5] 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.[3]

Operation

The Microsoft Deployment Toolkit (MDT) supports three types of deployments:[3] 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.[5] UDI deployments require full manual intervention to respond to every installation prompt, such as machine name, password or language setting.[6] ZTI and UDI deployments both require a Microsoft System Center infrastructure.[3] ZTI deployments require a persistent network connection to the distribution point.[5] 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.[4]

gollark: How much of a market *is* there for private Minecraft servers with large amounts of RAM and whatnot? Technically competent people can just rent a VPS.
gollark: Sounds generic.
gollark: (not mine, it's a popular CC server)
gollark: SwitchCraft uses something like 16GB.
gollark: Minecraft uses *all* RAM.

See also

References
  1. "Microsoft Deployment Toolkit Download Page".
  2. "Business Desktop Deployment (BDD) and Microsoft Deployment Toolkit (MDT) Archive".
  3. "Microsoft (August 2012). Using the Microsoft Deployment Toolkit". Archived from the original on 2019-09-14. Retrieved 2013-02-17.
  4. "Microsoft (August 2012). Quick Start Guide for Lite Touch Installation". Archived from the original on 2019-09-14. Retrieved 2013-02-17.
  5. "Microsoft (August 2012). Quick Start Guide for Configuration Manager 2012". Archived from the original on 2019-09-14. Retrieved 2013-02-17.
  6. "Microsoft (August 2012). Quick Start Guide for User Driven Installation". Archived from the original on 2019-09-14. Retrieved 2013-02-17.

How to Install ADK and MDT on Windows Server 2016?

Microsoft deployment resources
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.